Quality and Performance reporthttps://cienkusz.com.pl/drzwi-szklane
Report generated on Mar 13, 2019 2:15:24 PM
are almost there...
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
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 83.2KiB (67% reduction).
- Compressing cienkusz.com.pl/js[...]n.js could save 55.2KiB (65% reduction).
- Compressing cienkusz.com.pl/st[...].css could save 10.5KiB (83% reduction).
- Compressing cienkusz.com.pl/js[...]x.js could save 9.0KiB (76% reduction).
- Compressing cienkusz.com.pl/dr[...]lane could save 5.8KiB (59% reduction).
- Compressing cienkusz.com.pl/js[...].css could save 2.8KiB (72% reduction).
This page is delivered by an Apache server. Check if it uses the mod_deflate module.
16 of your requests don't define a cache policy with Apache
Expires header is essential for an efficient caching policy. It will significantly impact on the loading time for returning visitor.
The Expires header explained
You can set an expiration date for each resource: as long as the date is not exceeded, the browser stores and uses the resource in cache.
The expiry date of resources is set using the
Expires HTTP header:
Expires: Thu, 25 Dec 2014 20:00:00 GMT
You can set a far expiry date for static resources (1 year maximum), and a closer date for resources that change more frequently (at least 48 hours).
When you deploy a new version of your website, remember to rename static resources that have been modified. If you do not change their names, your users will keep resources corresponding to the old versions stored in their caches, and they may find themselves on an unstable version of your page. For example:
See the Yahoo! guidelines on this subject.
What should I do?
This page is delivered by an Apache server. Check if it uses the mod_expires module. Here's an example of configuration, to adapt to your needs (in your .htaccess file, for example):
ExpiresDefault "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 year"
ExpiresByType image/gif "access plus 1 month"
ExpiresByType image/png "access plus 1 month"
ExpiresByType image/jpeg "access plus 1 month"
ExpiresByType text/css "access plus 1 year"
This page contains 16 resources without expiry date:
- and 9 others
1 critical dependency detected
The failure of a third-party content provider could bring an overall breakdown of your website.
Single Point Of Failure
A Frontend Single Point Of Failure (SPOF) is a critical dependency on a third-party content, that may block the entire display of your page in case of failure of the content provider.
As an example, if your web page uses a blocking script hosted by Google’s servers, then your page is reliant on any failure from this script. Please read this blog post dedicated to SPOF for more information.
How to avoid SPOF?
As far as possible, exclude any of these dependencies, even from renowned providers. If you have to use a third-party content, ensure that you choosed an asynchronous integration and that you have a fallback in case of problem.
We are checking if the tested web page depends (in a critical way) on some of most widespread external resources (googleapis, typekit,...). That are known as Frontend SPOF (Single Point Of Failure) cases.
This resource represents a SPOF for this page:
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.
Optimize your images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 33.2KiB (12% reduction).
- Losslessly compressing cienkusz.com.pl/im[...].jpg could save 15.5KiB (16% reduction).
- Losslessly compressing cienkusz.com.pl/im[...].jpg could save 9.7KiB (68% reduction).
- Losslessly compressing cienkusz.com.pl/us[...].jpg could save 3.2KiB (5% reduction).
- Losslessly compressing cienkusz.com.pl/us[...].jpg could save 2.3KiB (5% reduction).
- Losslessly compressing cienkusz.com.pl/us[...].jpg could save 1.2KiB (5% reduction).
- Losslessly compressing cienkusz.com.pl/us[...].jpg could save 1.2KiB (6% reduction).
Specify a 'Vary: Accept-Encoding' header
The following publicly cacheable, compressible resources should have a "Vary: Accept-Encoding" header:
Vary: Accept-Encoding header allows to cache two versions of the resource on proxies: one compressed, and one uncompressed. So, the clients who cannot properly decompress the files are able to access your page via a proxy, using the uncompressed version. The other users will get the compressed version.
Did you know?
Your SSL certificate will expire on 05/09/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
1 domain sends 442 bytes of cookies
HTTP cookies are used to track a user to costumize the page according to their profile. They are sent as a HTTP header from the web server to the browser. Then, each time the browser accesses to the server, it sends a request containing the cookie received at the first response. See more information.
Here, 1 domain sends 442 bytes of cookies:
Domain name: cienkusz
PHPSESSID: 442 bytes distributed on 17 request(s)
This page does not load too much data (542kB)
A too high page weight slows down the 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 : 61,30% of total weight
- Font : 15,05% of total weight
- CSS : 3,35% of total weight
- Texts : 2,00% of total weight
Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:
- https://cienkusz.com.pl/images/tlo2.jpg (103 kB)
- https://cienkusz.com.pl/js/jquery-1.7.2.min.js (87 kB)
- cienkusz.com.pl/userfiles/image/drzw[...]e-warszawa-5.jpg (72 kB)
- cienkusz.com.pl/userfiles/image/drzw[...]e-warszawa-1.jpg (55 kB)
- fonts.gstatic.com/s/ubuntu/v13/4iCs6[...]goKcQ72j00.woff2 (47 kB)
- fonts.gstatic.com/s/ubuntu/v13/4iCs6[...]BYlgoKfw72.woff2 (35 kB)
- cienkusz.com.pl/userfiles/image/drzw[...]e-warszawa-2.jpg (32 kB)
- cienkusz.com.pl/userfiles/image/drzw[...]e-warszawa-3.jpg (22 kB)
- cienkusz.com.pl/userfiles/image/drzw[...]e-warszawa-4.jpg (22 kB)
- https://cienkusz.com.pl/images/belka.jpg (15 kB)
This page contains 9 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 9 links present in the page:
- 7 internal links (77,78%)
- 2 "follow" external links (22,22%)
- No "nofollow" external link (0,00%)
Well done, these best practices are respected
No empty element detected
<quote> elements must not be empty because if they are, some screen readers will have difficulties interpreting their presence.
Remove these empty elements from you code or decorate them with the
aria-hidden attribute so that the screen readers ignore them.
Your <img> tags use an alt attribute
alt attribute is also an important criterion for SEO. Indeed, search engines crawlers cannot parse graphic contents. That is why they use the alternative text to return consistent results, like in Google images.
<img src="product.jpg" alt="My product description"/>
alt attribute is used in several cases unrelated to SEO:
- When a screen reader is in use for accessibility purposes;
- While image is loading, particularly for slow connections;
- When the image file is not found.
You have 5
img tags and they all have the
If nothing seems appropriate for describing an image, you might set an empty text. We advise you to make sure the majority of your images define a relevant text. Read the W3C recommendations here.
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.
Your Apache server version is not exposed
You are using Apache, but we are not able to detect the version. It is more difficult for a hacker to attack your website, because he does not know the version you use. This is a good practice.
# Hide the version from the 'Server' HTTP Header.
# (e.g.): display only "Server: Apache"
# Don't add a trailing footer line under server-generated document,
# containing the server name and its version.
However, keep in mind that the best way to protect your system from attacks is to regularly update your Apache server.
This page defines <h1> and <h2> tags
We recommend putting page keywords in at least the h1 and h2 tags. Search engines use the h1, h2, and h3 tags for SEO purposes.
This page contains:
- 1 <h1> element(s)
- 1 <h2> element(s)
- 1 <h3> element(s)
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.