Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

postimees.ru

postimees.ru

Page Load Speed

11.3 sec in total

First Response

1.4 sec

Resources Loaded

8.3 sec

Page Rendered

1.6 sec

postimees.ru screenshot

About Website

Click here to check amazing Postimees content for Estonia. Otherwise, check out these important facts you probably never knew about postimees.ru

Новости в Эстонии и за рубежом: самый авторитетный русскоязычный новостной портал в Эстонии. Ознакомься поближе

Visit postimees.ru

Key Findings

We analyzed Postimees.ru page load time and found that the first response time was 1.4 sec and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

postimees.ru performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.167

71/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

rus.postimees.ee

1354 ms

css

24 ms

print.css

789 ms

gpt.js

7 ms

pubads_impl_82.js

7 ms

Our browser made a total of 269 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Postimees.ru, 7% (20 requests) were made to Static.xx.fbcdn.net and 7% (19 requests) were made to I.pmo.ee. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Rus.postimees.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (40%)

Content Size

2.6 MB

After Optimization

1.6 MB

In fact, the total size of Postimees.ru main page is 2.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 251.7 kB

  • Original 302.4 kB
  • After minification 302.0 kB
  • After compression 50.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 251.7 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 69.2 kB

  • Original 1.1 MB
  • After minification 1.1 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. Postimees images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 484.9 kB

  • Original 788.9 kB
  • After minification 784.6 kB
  • After compression 304.0 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 484.9 kB or 61% of the original size.

CSS Optimization

-65%

Potential reduce by 244.3 kB

  • Original 377.7 kB
  • After minification 373.0 kB
  • After compression 133.4 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. Postimees.ru needs all CSS files to be minified and compressed as it can save up to 244.3 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 139 (55%)

Requests Now

252

After Optimization

113

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

Accessibility Review

postimees.ru accessibility score

50

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.

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

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

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

postimees.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

postimees.ru SEO score

83

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

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postimees.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Postimees.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 Postimees. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: