Quality and Performance reporthttps://www.vita-derm.pl/depilacja-laserowa
Report generated on Mar 14, 2019 9:27:40 AM
work to be done
Share this report by email
Feel free to share this report with your collaborators, by copying the URL from the address bar,
or by clicking below:
Share the report
Tips and best practices:
Things to improve
Reduce the page weight (2.2MB)
The page weight is too high, slowing down its display, especially on low speed connections. This can lead to frustration for users paying for data (see whatdoesmysitecost.com).
Evaluate the Weight of my Web Page
In February 2016, the average weight of 100 most visited websites in the world was 1,38MB.
How to reduce the weight of my page?
You can report to our "Data amount" category to discover the possible optimizations in your case. Images are often involved.
Moreover, make sure to build your web pages in order to load data that is essential to the user experience (rendering optimization of the critical path).
For other contents (social networking plugins, advertising, content at the bottom of the page ...), it is better to delay the loading (asynchronous, lazy-loading ...), so they don't override priority contents.
We strongly recommend that you define performance budgets before you carry out your web projects. These budgets can be settled through the Dareboost monitoring feature.
We have established the weight distribution of the page by resource type:
- Images : 67,58% of total weight
- CSS : 2,57% of total weight
- Font : 1,40% of total weight
- Texts : 1,39% of total weight
- JSON : 0,05% of total weight
Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:
- www.vita-derm.pl/userfiles/image/Bea[...]Sheer_Desire.jpg (614 kB)
- www.youtube.com/yts/jsbin/player-vfl[...]Av/fr_FR/base.js (472 kB)
- https://www.vita-derm.pl/images/animacja/5.jpg (120 kB)
- https://www.vita-derm.pl/images/animacja/2.jpg (109 kB)
- https://www.vita-derm.pl/images/animacja/6.jpg (106 kB)
- https://www.vita-derm.pl/images/animacja/17.jpg (97 kB)
- https://www.vita-derm.pl/images/animacja/3.jpg (95 kB)
- https://www.vita-derm.pl/images/animacja/1.jpg (83 kB)
- https://www.vita-derm.pl/images/animacja/4.jpg (79 kB)
- https://www.vita-derm.pl/images/animacja/7.jpg (77 kB)
Optimize your images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 487.2KiB (46% reduction).
- Losslessly compressing www.vita-derm.pl/u[...].jpg could save 378.0KiB (63% reduction).
- Losslessly compressing www.vita-derm.pl/i[...].jpg could save 17.6KiB (17% reduction).
- Losslessly compressing www.vita-derm.pl/i[...].jpg could save 16.7KiB (15% reduction).
- Losslessly compressing www.vita-derm.pl/i[...].jpg could save 16.3KiB (16% reduction).
- Losslessly compressing www.vita-derm.pl/i[...].jpg could save 16.0KiB (18% reduction).
- Losslessly compressing www.vita-derm.pl/i[...].jpg could save 14.4KiB (75% reduction).
- Losslessly compressing www.vita-derm.pl/i[...].jpg could save 14.4KiB (74% reduction).
- Losslessly compressing www.vita-derm.pl/i[...].jpg could save 13.8KiB (76% reduction).
1 image is resized on browser side
Images must not be delivered larger than they are actually displayed to avoid loading unnecessary data.
Resizing images explained
Resizing images on browser side to reduce their rendering size is not recommended.
For instance, if your image is set to render at 300px by 300px on a particular page, don't upload the original 1000px by 1000px version of that image to your page. Instead, resize/crop the image to fit the display size and then upload it to your site to decrease the page weight and loading time.
Using images with responsive designs or retina screens?
Responsive website designs and retina screens do not justify an image resizing. Even in such cases, some methods exist to deliver your pictures to the right size. We recommend reading the following resources:
- Introduction to responsive images
- Picturefill, to start using the <picture> element
- RICG, group of developers working on responsive images
Don't resize the following image:
- www.vita-derm.pl/userfiles/[...]Desire.jpg (displayed size: 400x264)
On this page, 1 image is resized by less than 35%. This can be consistent in a Responsive Web Design website, so this best practice does not penalize the following resource, but please make sure that it does not affect the page performance:
- https://www.vita-derm.pl/images/cookie_no.png (displayed size: 20x20)
How can I fix this?
First of all, distinguish what portions of your JS is critical and must be loaded as soon as possible, and put them in a specific external file. Keep this file as streamlined as possible, and defer the parsing or execution of all other JS files (learn more).
- use the async attribute;
- use the defer attribute;
- make sure your scripts are placed at the bottom of the page (ideally at the end of the body).
- www.youtube.com/yt[...]e.js (1.1MiB)
- www.youtube.com/yt[...]r.js (86.5KiB)
- www.vita-derm.pl/j[...]n.js (86.0KiB)
- www.vita-derm.pl/j[...]y.js (50.7KiB)
- www.vita-derm.pl/j[...]n.js (13.3KiB)
- www.vita-derm.pl/s[...]r.js (12.6KiB)
- www.vita-derm.pl/j[...]x.js (6.7KiB)
Consider using jQuery 1.12
You webpage uses jQuery 1.7.2. You should migrate to the latest version of the 1.x branch: jQuery 1.12, that contains several bug and security fixes.
Should I migrate to the last version of jQuery ?
Migrating from a 1. x version of jQuery to the latest version (3.x) can have many unintended impacts and means losing compatibility with older browsers. You should only consider abandoning jQuery 1.x as a part of a complete overhaul of your Front-End infrastructure. As you reflect on it, you will surely discover that you might not need jQuery.
13 images (683kB) are loaded too early
Load images above the foldline first, that means all the images that are visible without any scroll of the page by the visitor.
Webpage and images
Images use to represent more than 60% of the total weight of webpages. By loading initially the only images that are visible without page scrolling, you’ll reduce bandwith consumption as for your server and your visitors. If an image has to display after any visitor’s action (as scrolling) , then you’d better load it on demand, when necessary (lazyloading).
How to set up lazyloading?
As an example, with jQuery you could use a plugin dedicated to images lazyloading.
13 images (683kB) loading can be delayed on this page, representing 45% of the total weight of all your images.
Did you know?
Your SSL certificate will expire on 10/26/2019. Update your certificate before that date.
What happens if my certificate expires?
Letting a certificate expire can have consequences for end users who will then see many error or alert messages while browsing the site, warning them of possible frauds, identity thefts or traffic interceptions. These alerts can have a very negative impact on the user's perception of the visited domain.
No <noscript> tag is detected
When a web page uses scripts, it is advised to set at least one
More informations about jQuery performance
This page contains 79 links
Two kind of links exist:
- Internal links that refer to pages with the same domain name;
- External links that point to other websites (must be relevant and point towards quality content).
If you reference many links, you can ask the SEO crawlers to consider only some of them, by adding the
rel=nofollow attribute to the irrelevant ones (e.g., advertisements).
Here is the distribution of 79 links present in the page:
- 75 internal links (94,94%)
- 4 "follow" external links (5,06%)
- No "nofollow" external link (0,00%)
Your server should be able to communicate with HTTP while it uses a HTTPS connection
Take precautionary measures against attacks like "man in the middle" by making sure to only communicate in HTTPS with the server.
The HTTP Strict Transport Security (HSTS) Header
When you communicate with a server through a secure connection, every sent request towards this server should use the HTTPS protocol. The HTTP HSTS header allows to indicate to the browser that all the requests sent to the domain concerned must be done via HTTPS. If the URL is presented under "http://...", the web browser is automatically going to replace it by "https://...".
However, we advise you to not set this header unless your entire website serves its resources in HTTPS.
HSTS can be configured with your Apache server. Make sure that the mod_headers module is enabled. Then, you can specify your HSTS (in your .htaccess file, for example). Here is an example :
Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains"
For further information, you can read this article.
No HSTS header has been detected on this page.
4 resources on this page are for public use
By default, the browser accepts to perform AJAX requests, or to retrieve web fonts, only on the same domain name of the page. So a font provided by toto.com can only be used by the pages of toto.com. This prevents misuse of your resources by any site.
Some resources are public, and explicitly want to be available to everyone (eg Google Fonts). In this case, the HTTP header
Access-Control-Allow-Origin can be used with the value "*". You should, however, use this property if your resource has aimed to be used by the greatest number. Otherwise, we recommend that you keep the default, or set a specific domain name in the "Access-Control-Allow-Origin" HTTP header.
You should be aware of the following resources, that use a
Access-Control-Allow-Origin: * HTTP header. Make sure they are actually intended to be used by pages from all domain names:
It appears these files are hosted by a third-party, so they may not be within your control. However, you should consider any alternative to these resources to improve your page performance.
Well done, these best practices are respected
Your HTML response is not too heavy
Why reduce the code amount of a page?
Before a web page can be displayed, the browser must, among other things, download it, parse it and model it into a document that can be understood by the rendering engine. If the amount of code contained in the page is too large, these steps are slowed down and the rendering is delayed.
How to reduce the amount of code?
Your HTML response should contain only the information that is immediately necessary to display the visible area of the page. Move inline information to external files (JS for scripts, CSS for styles, asynchronous queries for additional content) and simplify the HTML structure of your page.
You do not use too long inline scripts
Any script with a significant size should let the browser cached them in order to reduce loading time/improve performance of your returning visitor.
Inline scripts / cache policy
"inline" scripts allow to integrate easily small portions of scripts directly in the HTML code. Example:
ga('create', 'UA-11111111-1', 'mywebsite.com');
By doing so, you avoid making a request to the server to retrieve the resource. So inline scripts represent a performance gain if you want to integrate small scripts.
However, once a script has a fairly substantial size, we advise you to outsource it and perform a request to retrieve it. So you will benefit from the cache mechanism.
What should I do?
Outsource your scripts with more than 1500 characters in one or more separate files.
No nested tables detected
table tag should only be used to render ordered data. Handle the elements layout with CSS instructions.
You can use
rowspan properties to represent complex data.
table found in this page.
No frameset, frame and noframes tags detected
These tags are obsolete, due to several issues related to the navigation consistency, SEO or browsers' bookmark features for example.
None of these tags is detected on this page.
The use of the iframe tag is prefered.
This page uses only standard image formats
The images that use a non-standard format may not be indexed by search engines.
Only these image formats are considered standard on the web: jpeg, jpg, png, gif, svg, ico, webp. You should consider an alternative to any other format.
Moreover, remember to treat the text around your images: some search engines analyze approximately the 10 words preceding and following the image in order to add a context to the image.
No Java applets detected
Java applets are considered obsolete in 2015. HTML5 is powerful and more widely supported. Using Java applets can lead to compatibility issues and may send negative signals to your users (eg the browser indicating that content was blocked because it could be dangerous).
Congratulations, this page doesn't contain Java applets.