Tools & Wizards About Us
w3c.org.ru screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

w3c.org.ru

W3C for Russia

Page Load Speed

3.5 sec in total

First Response

852 ms

Resources Loaded

2.5 sec

Page Rendered

98 ms

w3c.org.ru screenshot

About Website

Welcome to w3c.org.ru homepage info - get ready to check W3C best content for Russia right away, or after learning these important things about w3c.org.ru

W3C for Russia — информационная страница W3C для России (на русском языке) ...

Visit w3c.org.ru

Key Findings

We analyzed W3c.org.ru page load time and found that the first response time was 852 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

w3c.org.ru performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value4.5 s

71/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

w3c.org.ru

852 ms

w3c.org.ru

559 ms

style.css

136 ms

main.js

401 ms

js

60 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 65% of them (13 requests) were addressed to the original W3c.org.ru, 5% (1 request) were made to Googletagmanager.com and 5% (1 request) were made to W3.org. The less responsive or slowest element that took the longest time to load (852 ms) belongs to the original domain W3c.org.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.9 kB (43%)

Content Size

50.5 kB

After Optimization

28.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of W3c.org.ru main page is 50.5 kB. 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 10% of websites need less resources to load. Images take 33.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 13.6 kB

  • Original 16.7 kB
  • After minification 10.2 kB
  • After compression 3.2 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. This page needs HTML code to be minified as it can gain 6.5 kB, which is 39% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.6 kB or 81% of the original size.

Image Optimization

-25%

Potential reduce by 8.3 kB

  • Original 33.0 kB
  • After minification 24.7 kB

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. Obviously, W3C needs image optimization as it can save up to 8.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-7%

Potential reduce by 54 B

  • Original 781 B
  • After minification 781 B
  • After compression 727 B

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. W3c.org.ru has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

17

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of W3C. According to our analytics all requests are already optimized.

Network Requests Diagram

w3c.org.ru

w3c.org.ru

852 ms

w3c.org.ru

w3c.org.ru

559 ms

style.css

style.css

136 ms

main.js

main.js

401 ms

js

js

60 ms

valid-html401

valid-html401

126 ms

vcss

vcss

63 ms

cycounter

cycounter

571 ms

3_1_D9D9D9FF_D9D9D9FF_0_pageviews

3_1_D9D9D9FF_D9D9D9FF_0_pageviews

674 ms

w3c_home.png

w3c_home.png

140 ms

rss.png

rss.png

146 ms

atom.png

atom.png

331 ms

twt-link.png

twt-link.png

279 ms

tg-link.png

tg-link.png

345 ms

twt.png

twt.png

346 ms

fb.png

fb.png

383 ms

vk.png

vk.png

397 ms

tg.png

tg.png

406 ms

tag.js

tag.js

45 ms

advert.gif

advert.gif

566 ms

Accessibility Review

w3c.org.ru accessibility score

77

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

w3c.org.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

w3c.org.ru SEO score

99

Search Engine Optimization Advices

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

w3c.org.ru

Open Graph description is not detected on the main page of W3C. 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: