2.2 sec in total
401 ms
1.7 sec
107 ms
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.eeWe analyzed Peatus.ee page load time and found that the first response time was 401 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
peatus.ee performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value8.8 s
1/100
25%
Value7.3 s
28/100
10%
Value620 ms
48/100
30%
Value0.216
57/100
15%
Value8.3 s
40/100
10%
401 ms
254 ms
379 ms
253 ms
395 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 95% of them (40 requests) were addressed to the original Peatus.ee, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (635 ms) belongs to the original domain Peatus.ee.
Page size can be reduced by 709.2 kB (82%)
865.9 kB
156.7 kB
In fact, the total size of Peatus.ee main page is 865.9 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. 40% of websites need less resources to load. Javascripts take 748.9 kB which makes up the majority of the site volume.
Potential reduce by 17.3 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 17.3 kB or 68% of the original size.
Potential reduce by 6.2 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.
Potential reduce by 616.1 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.
Potential reduce by 69.5 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.
Number of requests can be reduced by 32 (78%)
41
9
The browser has sent 41 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 16 to 1 for JavaScripts and as a result speed up the page load time.
peatus.ee
401 ms
tabs.css
254 ms
jquery-1.3.2.min.js
379 ms
flexcroll.js
253 ms
StopsInfo213.js
395 ms
PageTemplates.js
517 ms
PageController.js
397 ms
utils.js
397 ms
balloontip.js
393 ms
AutoSearch213.js
509 ms
StopsInfo.js
506 ms
dijkstra.js
510 ms
OptimalRoute.js
511 ms
calendar_eu.js
507 ms
custom_form_elements.js
631 ms
System.js
635 ms
MainParent.js
633 ms
ga.js
29 ms
print.png
133 ms
footer_bg.gif
130 ms
helesinine_nupp_vasak.gif
131 ms
helesinine_nupp_parem.gif
131 ms
logo_ee.png
127 ms
tabs_2_ee2.gif
128 ms
kysim2rk.gif
252 ms
maximize.gif
253 ms
restore.gif
255 ms
MarkerStartSmall.gif
254 ms
MarkerEndSmall.gif
252 ms
zoom.png
254 ms
MarkerStart.gif
378 ms
MarkerEnd.gif
376 ms
info.gif
378 ms
expand.gif
378 ms
collapse.gif
379 ms
MarkerYellow.gif
378 ms
MarkerGray.gif
500 ms
MarkerRed.gif
500 ms
cluster.gif
504 ms
stop.gif
505 ms
__utm.gif
11 ms
print.css
128 ms
peatus.ee accessibility score
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
button, link, and menuitem elements do not have accessible names.
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
peatus.ee best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
peatus.ee SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
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) and no language is claimed in <html> or <meta> tags either. 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.
peatus.ee
Open Graph description is not detected on the main page of Peatus. 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: