Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

guardian-spb.ru

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

Page Load Speed

8.7 sec in total

First Response

483 ms

Resources Loaded

7.5 sec

Page Rendered

684 ms

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 483 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

guardian-spb.ru performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value16,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value37.2 s

0/100

10%

Network Requests Diagram

guardian-spb.ru

483 ms

guardian-spb.ru

669 ms

tilda-fallback-1.0.min.js

36 ms

tilda-grid-3.0.min.css

34 ms

tilda-blocks-page25453314.min.css

269 ms

Our browser made a total of 194 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Guardian-spb.ru, 55% (106 requests) were made to Static.tildacdn.com and 15% (29 requests) were made to Thb.tildacdn.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Static.tildacdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (11%)

Content Size

23.0 MB

After Optimization

20.5 MB

In fact, the total size of Guardian-spb.ru main page is 23.0 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. Only a small number of websites need less resources to load. Images take 19.2 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 2.2 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 283.8 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 2.2 MB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 303.8 kB

  • Original 19.2 MB
  • After minification 18.9 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

-0%

Potential reduce by 2.5 kB

  • Original 850.0 kB
  • After minification 850.0 kB
  • After compression 847.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 21.3 kB

  • Original 482.0 kB
  • After minification 482.0 kB
  • After compression 460.7 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 94 (52%)

Requests Now

182

After Optimization

88

The browser has sent 182 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 51 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

guardian-spb.ru accessibility score

80

Accessibility Issues

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

<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

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

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

89

Search Engine Optimization Advices

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

    N/A

  • 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 neither this language nor any other was claimed in <html> or <meta> tags. 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 data is detected on the main page of Guardian Spb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: