Quality and Performance reporthttp://ubezpieczeniaturystyczne.online/
Report generated on Sep 26, 2018 6:40:59 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
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:
- ubezpieczeniaturystyczne.on[...]/header.jpg (displayed size: 1366x164)
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:
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).
You should use a secure connection (HTTPS)
HTTPS guarantees the confidentiality and security of communications over the internet: data is encrypted, so protected against attacks and data corruption.
Google is multiplying its actions to push more and more websites towards HTTPS. Google first added HTTPS in its SEO criteria (see the announcement). Since then, Chrome has been evolving and now highlights the absence of a secure environment in various cases where information is collected from users. Other browsers are also following this trend.
Setting up HTTPS on a website sometimes causes some reservations (cost, impacts on performance, compatibility with technical partners…). But the market has changed in recent years and you should not worry about migrating to HTTPS. You should consider switching your site to HTTPS.
How to set up the HTTPS protocol
You have to set up a certificate you got from a reliable certification authority. Learn more by contacting your website host who can help you getting this certificate. Besides, the following page help you in your migration procedure to the HTTPS protocol.
A free certificate? Try Let's Encrypt!
Let's Encrypt is a free, automated, and open certificate authority. Many hosting providers offer to enable the generation and automatic renewal of free certificates directly from the administration interface of your domain. Contact your website host for more information.
You should define a 'description' meta tag
The page should define a unique description.
Description in search engines
The description of the page may be directly displayed in search engine results pages (SERP):
It allows you to control at best the entry preview in search engines, and to improve the click rate to your page. Learn more.
How to define a page's description?
<meta name="description" content="page description"> and place it in the
description has been found on this page. Please provide a <meta>
The Content Security Policy is missing
Protect you website from cross-site scripting (XSS) attacks by setting up a restrictive Content-Security-Policy.
XSS attacks explained
XSS attacks are a type of attack in which malicious data is maliciously added to websites. The number of vulnerabilities allowing these attacks is quite large, which is why it is as useful to prevent them as to limit their harmful effects.
You can protect your pages against these attacks and their effects by restricting execution to code portions either legitimized by the domain to which they belong or by a unique integrity token. The code that does not corresponding to this security policy will not be executed and the user will be informed.
You can learn more about XSS attacks on the Open Web Application Security Project (OWASP) Website.
Configure a "Content-Security-Policy" (CSP) HTTP header
Set up a "Content-Security-Policy" (CSP) HTTP header to prevent or limit damage caused by an XSS attack. To specify a security policy configure your server so the response of the first resource contains the "Content-Security-Policy" HTTP header.
Here's an example:
Content-Security-Policy: script-src 'self' https://apis.google.com
In this case, only scripts coming from the current host or https://apis.google.com will be executed.
Please, be careful, if the header is misconfigured, some of your content, scripts, or styles may be blocked. That could cause unwanted side effects. Moreover, the restrictions apply to all pages of the website. We recommend you test the different pages of your website before deploying this header in your production environment.
No Content Security Policy on this page: it is more easily exposed to XSS attacks.
Did you know?
No HTML code is commented
Comments allow you to detail a portion of code and help you navigate more efficiently in the DOM. However, make sure no sensitive information is exposed in your comments.
Well done, none of your comments contains HTML code.
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 does not load too much data (327kB)
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 : 35,28% of total weight
- Font : 32,82% of total weight
- Texts : 7,52% of total weight
- CSS : 6,60% of total weight
Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:
- ubezpieczeniaturystyczne.online/wp-c[...]images/header.jpg (115 kB)
- ubezpieczeniaturystyczne.online/wp-i[...]ery.js?ver=1.12.4 (40 kB)
- http://ubezpieczeniaturystyczne.online/ (25 kB)
- fonts.gstatic.com/s/librefranklin/v2[...]i24_SI0q1s.woff2 (21 kB)
- ubezpieczeniaturystyczne.online/wp-c[...]yle.css?ver=4.9.8 (21 kB)
- fonts.gstatic.com/s/librefranklin/v2[...]4XkRiUf2zc.woff2 (20 kB)
- fonts.gstatic.com/s/librefranklin/v2[...]i20-SI0q1s.woff2 (20 kB)
- fonts.gstatic.com/s/librefranklin/v2[...]_SI6q1vxiQ.woff2 (16 kB)
- fonts.gstatic.com/s/librefranklin/v2[...]RiUR2zcLig.woff2 (15 kB)
- fonts.gstatic.com/s/librefranklin/v2[...]-SI6q1vxiQ.woff2 (15 kB)
This page contains 23 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 23 links present in the page:
- 21 internal links (91,30%)
- 2 "follow" external links (8,70%)
- No "nofollow" external link (0,00%)
7 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.
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 1
img tag that defined 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.
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)
- 8 <h2> 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.
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.