Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

guardian-spb.ru

Входные стальные двери, компания "Двери Гардиан" в СПб

Page Load Speed

19.8 sec in total

First Response

1.8 sec

Resources Loaded

17 sec

Page Rendered

970 ms

guardian-spb.ru screenshot

About Website

Visit guardian-spb.ru now to see the best up-to-date Guardian Spb content for Russia and also check out these interesting facts you probably never knew about guardian-spb.ru

Входные стальные двери компании "Двери Гардиан", металлические двери в Санкт-Петербурге 11 фирменных салонов. Доставка и установка. Замер бесплатно!

Visit guardian-spb.ru

Key Findings

We analyzed Guardian-spb.ru page load time and found that the first response time was 1.8 sec and then it took 18 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

guardian-spb.ru performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value10,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.3 s

0/100

10%

Network Requests Diagram

guardian-spb.ru

1811 ms

css__T-3bOE8tubTPeXNQz4jZOi0WU5320QjSCupcNx9c-VM__ZPHjLuF5-JVCbMNZ98AQzlKApDwqvPAPtO19OAZ4-gI__WWDBxG7oFqnCBU9puASFFTf3GYktPh4v2r9ypE5FZKg.css

324 ms

js__2nu-f_-MK33dRIQaWIdLP84wUiGzIZwBgGaMto4f2kY__2pkqXjBO9pMF06nUvX11DkMECNCM7M-5Qm_bWm0bC9k__WWDBxG7oFqnCBU9puASFFTf3GYktPh4v2r9ypE5FZKg.js

510 ms

js__H5AFmq1RrXKsrazzPq_xPQPy4K0wUKqecPjczzRiTgQ__p930YZ_ODW6ZjDLOJmxJnRL7juGStYuszD6uNS8_FFo__WWDBxG7oFqnCBU9puASFFTf3GYktPh4v2r9ypE5FZKg.js

207 ms

js__jY3-3CF_aW2-zV7M-ZJG0aboHTCHOpI0LqsoubNNRFI__hep11hr0bMli1FOW7LIhjy_eKKMS7eT1XluaHVikkHk__WWDBxG7oFqnCBU9puASFFTf3GYktPh4v2r9ypE5FZKg.js

208 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 95% of them (89 requests) were addressed to the original Guardian-spb.ru, 1% (1 request) were made to W.sharethis.com and 1% (1 request) were made to Wd-edge.sharethis.com. The less responsive or slowest element that took the longest time to load (14.3 sec) relates to the external source Wd-edge.sharethis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 687.8 kB (32%)

Content Size

2.1 MB

After Optimization

1.4 MB

In fact, the total size of Guardian-spb.ru main page is 2.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 92.0 kB

  • Original 114.7 kB
  • After minification 110.2 kB
  • After compression 22.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 92.0 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 80.6 kB

  • Original 1.3 MB
  • After minification 1.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Guardian Spb images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 370.1 kB

  • Original 511.2 kB
  • After minification 501.2 kB
  • After compression 141.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 370.1 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 145.1 kB

  • Original 176.1 kB
  • After minification 175.9 kB
  • After compression 30.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Guardian-spb.ru needs all CSS files to be minified and compressed as it can save up to 145.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (28%)

Requests Now

92

After Optimization

66

The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guardian Spb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

guardian-spb.ru accessibility score

75

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

guardian-spb.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

guardian-spb.ru SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guardian-spb.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Guardian-spb.ru main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Guardian Spb. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: