Tools & Wizards About Us
peatus.ee screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

peatus.ee

peatus.ee

Page Load Speed

12.6 sec in total

First Response

2 sec

Resources Loaded

10.5 sec

Page Rendered

56 ms

peatus.ee screenshot

About Website

Welcome to peatus.ee homepage info - get ready to check Peatus best content for Estonia right away, or after learning these important things about peatus.ee

Digitransit journey planning UI

Visit peatus.ee

Key Findings

We analyzed Peatus.ee page load time and found that the first response time was 2 sec and then it took 10.6 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

peatus.ee performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.271

45/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

web.peatus.ee

2037 ms

gtm.js

78 ms

estonia_theme.e47a938100da82cfb528.css

4630 ms

css

43 ms

js

56 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Peatus.ee, 22% (2 requests) were made to Googletagmanager.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (8.1 sec) relates to the external source Web.peatus.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (80%)

Content Size

2.0 MB

After Optimization

405.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peatus.ee main page is 2.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 10% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 920.0 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 256.6 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 920.0 kB or 78% of the original size.

Image Optimization

-57%

Potential reduce by 6.2 kB

  • Original 11.0 kB
  • After minification 4.8 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, Peatus needs image optimization as it can save up to 6.2 kB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-82%

Potential reduce by 616.1 kB

  • Original 748.9 kB
  • After minification 462.3 kB
  • After compression 132.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 616.1 kB or 82% of the original size.

CSS Optimization

-86%

Potential reduce by 69.5 kB

  • Original 80.5 kB
  • After minification 56.8 kB
  • After compression 11.0 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. Peatus.ee needs all CSS files to be minified and compressed as it can save up to 69.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

web.peatus.ee

web.peatus.ee

2037 ms

gtm.js

gtm.js

78 ms

estonia_theme.e47a938100da82cfb528.css

estonia_theme.e47a938100da82cfb528.css

4630 ms

css

css

43 ms

js

js

56 ms

b8946c77e1902ab699b4.js

b8946c77e1902ab699b4.js

8128 ms

f1d693ccb9195320d813.js

f1d693ccb9195320d813.js

687 ms

5a48d6267691f2e41c20.js

5a48d6267691f2e41c20.js

879 ms

4290cb1b7a07aee17d77f0e92699c1fe.svg

4290cb1b7a07aee17d77f0e92699c1fe.svg

310 ms

Accessibility Review

peatus.ee accessibility score

89

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 input fields do not have accessible names

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

peatus.ee SEO score

100

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    ET

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peatus.ee 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 Estonian. Our system also found out that Peatus.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

peatus.ee

Open Graph data is detected on the main page of Peatus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: