Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

postimees.ee

Postimees: Värsked uudised Eestist ja välismaalt

Page Load Speed

8.7 sec in total

First Response

1.3 sec

Resources Loaded

5.6 sec

Page Rendered

1.8 sec

postimees.ee screenshot

About Website

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

Postimees: Värsked uudised Eestist ja välismaalt. Loe lähemalt

Visit postimees.ee

Key Findings

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

Performance Metrics

postimees.ee performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value7,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.077

95/100

15%

TTI (Time to Interactive)

Value27.8 s

0/100

10%

Network Requests Diagram

www.postimees.ee

1349 ms

css

24 ms

print.css

1013 ms

gpt.js

5 ms

pubads_impl_81.js

7 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Postimees.ee, 35% (48 requests) were made to F.pmo.ee and 14% (20 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 F.pmo.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (28%)

Content Size

8.6 MB

After Optimization

6.1 MB

In fact, the total size of Postimees.ee main page is 8.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. 55% of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 273.2 kB

  • Original 323.1 kB
  • After minification 322.4 kB
  • After compression 49.9 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 273.2 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 136.1 kB

  • Original 5.5 MB
  • After minification 5.3 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

-75%

Potential reduce by 1.3 MB

  • Original 1.7 MB
  • After minification 1.4 MB
  • After compression 429.8 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 1.3 MB or 75% of the original size.

CSS Optimization

-68%

Potential reduce by 699.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 333.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. Postimees.ee needs all CSS files to be minified and compressed as it can save up to 699.3 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (29%)

Requests Now

135

After Optimization

96

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

Accessibility Review

postimees.ee accessibility score

62

Accessibility Issues

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-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements 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

Best Practices

postimees.ee 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

postimees.ee SEO score

92

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

    ET

  • Language Claimed

    ET

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postimees.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it matches the claimed language. Our system also found out that Postimees.ee 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: