Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

metro.fi

Pääkaupunkiseutu | HS.fi

Page Load Speed

693 ms in total

First Response

35 ms

Resources Loaded

606 ms

Page Rendered

52 ms

metro.fi screenshot

About Website

Welcome to metro.fi homepage info - get ready to check Metro best content for Finland right away, or after learning these important things about metro.fi

Mitä tapahtuu pääkaupunkiseudulla? Helsingin Sanomat raportoi kaupunginosien elämästä ja uutisoi kaupunkisuunnittelun vaikutuksesta arjen sujumiseen, asuntomarkkinoihin, liikenteeseen ja talouteen.

Visit metro.fi

Key Findings

We analyzed Metro.fi page load time and found that the first response time was 35 ms and then it took 658 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

metro.fi performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value3,670 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.186

66/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

metro.fi

35 ms

metro.fi

305 ms

kaupunki

231 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 67% of them (2 requests) were addressed to the original Metro.fi, 33% (1 request) were made to Hs.fi. The less responsive or slowest element that took the longest time to load (305 ms) belongs to the original domain Metro.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 548.7 kB (58%)

Content Size

938.5 kB

After Optimization

389.8 kB

In fact, the total size of Metro.fi main page is 938.5 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Javascripts take 531.2 kB which makes up the majority of the site volume.

HTML Optimization

-14%

Potential reduce by 16 B

  • Original 114 B
  • After minification 114 B
  • After compression 98 B

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 16 B or 14% of the original size.

Image Optimization

-1%

Potential reduce by 1.4 kB

  • Original 188.5 kB
  • After minification 187.1 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. Metro images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 352.7 kB

  • Original 531.2 kB
  • After minification 516.9 kB
  • After compression 178.6 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 352.7 kB or 66% of the original size.

CSS Optimization

-89%

Potential reduce by 194.6 kB

  • Original 218.6 kB
  • After minification 218.6 kB
  • After compression 24.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. Metro.fi needs all CSS files to be minified and compressed as it can save up to 194.6 kB or 89% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

metro.fi accessibility score

100

Accessibility Issues

Best Practices

metro.fi 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

metro.fi SEO score

93

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    FI

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metro.fi can be misinterpreted by Google and other search engines. Our service has detected that Finnish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Metro.fi main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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