Quality and Performance report

http://pachnacakraina.com/oczyszczanie,olej-nagietkowy---demakijaz-skory-z-problemami-50-ml,326
Report generated on Mar 15, 2019 2:12:42 PM

SIMULATED VISITOR: Chrome Paris 8.0/1.5Mbps (Latency: 50 ms) Edit

Requests

67

Weight

2.17MB

HTML CSS Scripts Images Others
Timeline / Waterfall

First Byte

0.32sec

Start Render

0.90sec

Fully loaded

3.13sec


Browser warnings 0OK
HTTP/2 Ready: 45%
Speed Index: 1990

Technologies :

Google Analytics

Google Font API

PHP

jQuery


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 

0/100

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 : 59,38% of total weight
  • JavaScript : 29,09% of total weight
  • Texts : 10,17% of total weight
  • CSS : 1,31% of total weight
  • Others : 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:


 
Read more
Security 

0/100

Use HTTPS to collect sensitive data

This page specifies some input to collect passwords or credit card information. Please, provide a secure connection.

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.

Moreover, this page collects sensitive information (through password or credit card input fields). In this case, Google Chrome warns its users that the website is "Not Secure" :

HTTPS marqué non sécurisé sur Google Chrome

Setting up HTTPS on a website sometimes causes some reservations (cost, impacts on performance...). 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
Number of requests 

0/100

2 resources are unreachable

You should avoid requesting unreachable resources.

Warning notifications that some requests related to your page are encountering errors can be due to:

  • errors in your HTML, CSS, or JavaScript resources;
  • an unhandled error on the server side;
  • or a problem on a service used by your page.

The following HTTP codes were returned:

These errors can affect content on and behaviors of your website and cause unnecessary network traffic, which affects the loading time of your page.


 
Read more
Cache policy 

0/100

25 of your requests don't define a cache policy

The 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:

myresource.min.20140101.js

See the Yahoo! guidelines on this subject.

This page contains 25 resources without expiry date:


 
Read more
Browser rendering 

0/100

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 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.

The following resources represent a SPOF for this page:


 
Read more
Browser rendering 

0/100

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?

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 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).

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


 
Read more

Did you know?

Quality 

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
jQuery 

More informations about jQuery performance

jQuery is the most used JavaScript library. Upgrade your website performance respecting the jQuery best practices. We recommend that you learn the basics of the jQuery performance, reading the following link: http://learn.jquery.com/performance/.


 
Read more
Data amount 

1 domain sends 2kB 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 2kB of cookies:

Domain name: pachnacakraina
  • PHPSESSID: 992 bytes distributed on 31 request(s)
  • _gid: 216 bytes distributed on 8 request(s)
  • _ga: 208 bytes distributed on 8 request(s)
  • _fbp: 87 bytes distributed on 3 request(s)
  • _gat_gtag_UA_112022692_1: 8 bytes distributed on 8 request(s)
  • _gat: 8 bytes distributed on 8 request(s)


 
Read more

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

  • 95 internal links (98,96%)
  • 1 "follow" external link (1,04%)
  • No "nofollow" external link (0,00%)


 
Read more
Security 

23 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.


 
Read more
Quality 

The !important declaration is used 5 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:

http://pachnacakraina.com/script/magicthumb/magicthumb.css

  • .MagicThumb, .MagicThumb:hover {outline: 0 !important} (line 15, col 1)
  • .MagicThumb span {display: none !important} (line 25, col 1)
  • .MagicThumb-caption {border: 0 !important} (line 50, col 1)
  • .MagicThumb-caption {outline: 0 !important} (line 51, col 1)
  • .MagicThumb-buttons a {margin: 0px 1px !important} (line 64, col 1)


 
Read more

Well done, these best practices are respected

Browser rendering 

100/100

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.


 
Read more
Accessibility 

100/100

No empty element detected

<p>, <li>, <button>, <legend>, <caption>, <figcaption> and <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.

<p aria-hidden="true"></p>


 
Read more
Cache policy 

100/100

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">
    (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']...,'/analytics.js','ga');
    ga('create', 'UA-11111111-1', 'mywebsite.com');
</script>

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
Accessibility 

100/100

<noscript> tag detected

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


 
Read less
Quality 

100/100

No nested tables detected

table tag should only be used to render ordered data. Handle the elements layout with CSS instructions.

You can use colspan and rowspan properties to represent complex data.

No nested table found in this page.


 
Read more
Compliance 

100/100

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.


 
Read more