Quality and Performance report

Report generated on Mar 20, 2018 10:23:55 PM
Download report
SIMULATED VISITOR: Chrome Paris 8.0/1.5Mbps (Latency: 50 ms) Edit





HTML CSS Scripts Images Others
Timeline / Waterfall

First Byte


Start Render


Fully loaded


Browser warnings 0OK
HTTP/2 Ready: 9%
Speed Index: 1695

Technologies :


Google Analytics

Google Tag Manager


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

Data amount 


Reduce the page weight (2.1MB)

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 : 88,80% of total weight
  • JavaScript : 9,73% of total weight
  • CSS : 0,76% of total weight
  • Texts : 0,60% of total weight
  • JSON : 0,03% of total weight

Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:

Read more
Data amount 


4 images are 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:

Don't resize the following images:

On this page, 16 images are resized by less than 35%. This can be consistent in a Responsive Web Design website, so this best practice does not penalize the following resources, but please make sure that they do not affect the page performance:

Read more
Browser rendering 


2 critical dependencies 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 our 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.

The following resources represent a SPOF for this page:

Read more
Browser rendering 


Defer parsing of JavaScript

JavaScript can significantly slow down a page display, especially if it is necessary to download an external script.

Defer the use of JavaScript as much as possible to provide a faster start for the page display.

How can I fix this?

Use one of the methods below to defer parsing for external JavaScript files:

  • use the async attribute;
  • use the defer attribute;
  • append the script to the DOM in JavaScript during the onload event;
  • make sure your scripts are placed at the bottom of the page (ideally at the end of the body).

294.2KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.

Read more


Consider using jQuery 1.12

You webpage uses jQuery 1.11.0. 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.

Read more


You should use a secured 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.

Read more

Did you know?


The !important declaration is used 6 times

If you abuse of this declaration, you should consider a review of your CSS code. We tolerate 10 occurrences of the !important declaration before penalizing your score.

Here are the !important detected:


  • .gallery-thumbs .swiper-slide {width: 20%!important} (line 254, col 2)
  • .veha_recall .button, .bl07 button.btn, .bl06 button.btn {bo... (line 510, col 2)
  • .open {background: rgba(0,0,0,.8)!important} (line 563, col 2)
  • .open {padding: 15% 0!important} (line 564, col 2)
  • .bl00 > ol > li {padding: 15px 30px 5px 30px!important} (line 724, col 19)
  • .lfoot img {margin: 10px 0!important} (line 760, col 14)

Read more
Data amount 

2 domains send 7kB 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, 2 domains send 7kB of cookies:

Domain name: argowindowrepair
  • 29a407e69f24e5641ae42a177924d020: 3kB distributed on 100 request(s)
  • _ga: 1kB distributed on 47 request(s)
  • _gid: 1kB distributed on 46 request(s)
  • _ym_uid: 779 bytes distributed on 41 request(s)
  • _gat_UA-100782098-1: 46 bytes distributed on 46 request(s)
  • _ym_isad: 37 bytes distributed on 37 request(s)
  • _ym_visorc_44931685: 34 bytes distributed on 34 request(s)
Domain name: yandex
  • i: 92 bytes distributed on 1 request(s)
  • yp: 26 bytes distributed on 1 request(s)
  • yandexuid: 19 bytes distributed on 1 request(s)
  • yabs-sid: 18 bytes distributed on 1 request(s)

Read more

3 CSS properties are overridden

Generally, it is unnecessary to define 2 times the same property within the same rule: the second one overrides the first.
This may affect the readability of CSS code. Eliminate unnecessarily overridden properties also reduce the file size.

How to improve it?

Remove one occurrence of the duplicated property. For example, the following properties:

.myClass {
margin: 20px;
margin: 10px;

Should be replaced by:

.myClass {
margin: 10px;

The following files define the same property several times in a single rule.
Note that CSS fallbacks can justify a duplicated property.

Make sure that the following properties are duplicated on purpose:


  • .veha_recall .button, .b[...]7,199,47) 0%, rgb(191,112,20) 100%)} (line 513, col 2)
  • .veha_recall .button, .b[...]7,199,47) 0%, rgb(191,112,20) 100%)} (line 514, col 2)
  • .veha_recall .button, .b[...]37,199,47) 0%,rgb(191,112,20) 100%)} (line 516, col 2)

Read more

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.

Read more

This page contains 51 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 51 links present in the page:

  • 44 internal links (86,27%)
  • 7 "follow" external links (13,73%)
  • No "nofollow" external link (0,00%)

Read more

6 CSS selectors are duplicated

Using several times the same selector for several declarative blocks within a single CSS file can affect the readability and maintainability of the code. It is also an optimization opportunity: by grouping these elements within a single rule, you will reduce the file size and optimize the rendering times.

The CSS Object Model (CSSOM)

The CSS rules allow to select elements from the HTML code in order to apply styling properties.

In order to do that, the browser constructs its own model of the CSS markup it has fetched: the CSS Object Model. This transformation takes several steps: reading the file, converting the strings of text into browser tokens, transforming this tokens into objects with properties and rules and organizing the elements in a tree-like model. These operations will take place more quickly if the CSS code is written in a simple and non-redundant way.

How to improve the CSS rules?

For maintenance as well as performance, you have to reduce the number of rules contained into your CSS files and group rules whenever it’s possible. For instance, the following rules:

.myClass {
margin: 0;
border: 1px solid black;

Should be merged into a single one:

.myClass {
margin: 0;
border: 1px solid black;

If the duplication is the result of a legacy process or is justified for maintenance reasons, you can consider using a CSS minification tool able to do automatically this improvement.

You can save 588 characters. The following files define the same selector in different rules:


  • @media all and (max-widt[...]x-width: 1024px) #cssmenu ul ul li a (2 times)


  • .bl03 (2 times)
  • .bl06 (2 times)
  • .bl08 (2 times)
  • .footer (2 times)
  • @media (max-width:768px)[...]ecall textarea, .veha_recall .button (2 times)

Read more

Well done, these best practices are respected

Data amount 


Redirects are lightweight

A HTTP redirect's content is not used by web browsers. So, it provides an unnecessary weight that should be as small as possible.

Redirects on the web

Redirects can be temporary (302 HTTP code) or permanent (301).

This mechanism is for example used for secondary domains (.net to .com), the language detection mechanisms, etc.

How to fix the issue?

First ensure that the redirect is unavoidable. In this case, it is necessary to reduce or completely remove the contents of the server responses for redirects.

A redirect should be < 1kB.

There isn't too heavy redirect.

Read more
Cache policy 


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:

<script type="text/javascript">
    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.

Read more


<noscript> tag detected

This page uses noscript tag. It allows to display a message when JavaScript is disabled by the user.

Read less


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.

There are two values to check if you want to hide your server version: the ServerSignature and the ServerTokens (/etc/apache2/conf.d/security file on a Linux server).

# Hide the version from the 'Server' HTTP Header.
# (e.g.): display only "Server: Apache"
ServerTokens Prod
# Don't add a trailing footer line under server-generated document,
# containing the server name and its version.
ServerSignature Off

However, keep in mind that the best way to protect your system from attacks is to regularly update your Apache server.

Read more


You have defined a <meta> 'description'

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?

Use <meta name="description" content="page description"> and place it in the <head> tag.

This page defines one <meta> description:

Wooden windows restoration. One stop windows & glass repair service provider. Save up to 70% of the budget for restoration in just 1 day. Call for free estimate

Read more


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.

Read more