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 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 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.
This resource represents a SPOF for this page:
How can I fix this?
- 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 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
It is critical to restrict the origin of the contents of your webpage to protect your website from cross-site scripting attacks (XSS).
XSS attacks explained
An XSS attack aims to inject content into a page.
You can protect your pages against these attacks by implementing a content security policy that tells the web browser which servers are allowed to deliver resources on each page. If the browser makes a request to an unauthorized server, it must inform the user.
How can I prevent an XSS attack?
Set up a "Content-Security-Policy" (CSP) HTTP header. To specify a security policy on the source of your resources, 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, the page loads correctly provided that all the scripts come from the current host or https://apis.google.com.
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.
Set a lang for your page
Your page should define a
lang attribute on the
html root node: this will allow screen readers to correctly understand your website.
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?
The Slowest Resources
The page load time is 2.5 seconds. Listed below, are your site's slowest loading requests:
- sites.google.com/site/pesnyaladasedan/_[...]1_00013_1_t218.jpg (324ms)
- gg.google.com/csi?v=3&s=jotspot&action=[...]render.617,ol.1271 (298ms)
- sites.google.com/site/pesnyaladasedan/_[...]emedefaultstandard (232ms)
- https://sites.google.com/site/pesnyaladasedan/ (226ms)
- https://www.google.com/images/icons/product/sites-16.ico (219ms)
- sites.google.com/site/pesnyaladasedan/_[...]allthemes-view.css (199ms)
- sites.google.com/site/pesnyaladasedan/_[...]fined&afjstz=lg0rD (175ms)
- translate.google.com/translate_a/elemen[...]lateCallback&hl=fr (75ms)
- https://www.google.com/images/cleardot.gif (74ms)
- ssl.gstatic.com/sites/p/ab32ab/system/a[...]ntchip-ltr-ltr.css (361ms)
- https://ssl.google-analytics.com/ga.js (336ms)
- https://www.google-analytics.com/analytics.js (329ms)
- translate.googleapis.com/translate_stat[...]anslateelement.css (280ms)
- ssl.gstatic.com/sites/p/ab32ab/system/j[...]ot_min_view__ru.js (259ms)
- stats.g.doubleclick.net/r/collect?v=1&a[...]_v=j52&z=250286087 (237ms)
- translate.googleapis.com/element/TE_201[...]nt/element_main.js (185ms)
- ssl.gstatic.com/sites/p/ab32ab/system/a[...]hip/bg_sprites.gif (105ms)
- translate.googleapis.com/translate_a/l?[...]backs____0j26f6xju (73ms)
- www.gstatic.com/images/branding/product[...]translate_24dp.png (70ms)
Excessively slow response times can be due to any number of reasons, usually because of a heavy resource that's loading or a temporary network issue.
For more information on page load time, you can consult the timeline.
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
This page does not load too much data (0,35 MB)
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 : 24,68% of total weight
- CSS : 10,41% of total weight
- Texts : 2,47% of total weight
Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:
- ssl.gstatic.com/sites/p/ab32ab/syste[...]_min_view__ru.js (104 kB)
- translate.googleapis.com/element/TE_[...]/element_main.js (83 kB)
- sites.google.com/site/pesnyaladaseda[...]00013_1_t218.jpg (78 kB)
- ssl.gstatic.com/sites/p/ab32ab/syste[...]chip-ltr-ltr.css (28 kB)
- https://ssl.google-analytics.com/ga.js (16 kB)
- https://www.google-analytics.com/analytics.js (12 kB)
- https://sites.google.com/site/pesnyaladasedan/ (7 kB)
- translate.googleapis.com/translate_s[...]slateelement.css (4 kB)
- translate.googleapis.com/translate_s[...]slateelement.css (4 kB)
- translate.googleapis.com/translate_s[...]img/te_ctrl3.gif (3 kB)
You serve scaled images
Images must not be delivered larger than they are actually displayed to avoid loading unnecessary data.
Resizing images explained
height attributes in
img tags is not recommended to reduce the rendering of an image.
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
Good job! No image resize have been detected. This is ideal for reducing page weight and loading time.
On this page, 1 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:
- www.gstatic.com/images/bran[...]e_24dp.png (displayed size: 20x20)
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:
- 8 internal links (88,89%)
- No "follow" external link (0,00%)
- 1 "nofollow" external link (11,11%)
Well done, these best practices are respected
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.
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)
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 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 specifies a <title> tag
The page should define a unique title (using a <title> tag).
Use of titles by search engines
Once properly configured, the page title can be displayed in the search engine results page:
Using a suitable title is a major criterion for SEO. It allows you to control at best what is displayed in search results pages, and determine the keywords you want your site pops out.
How to define the title of a web page?
The title of the page is specified into the
<title> tag, which must be placed into the
<head> tag, at the beginning of the code.
This page defines a title the
Here is the page's title:
Тимати Лада Седан
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.