Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

vltava.fi

Vltava | Raflaamo.fi

Page Load Speed

19.9 sec in total

First Response

469 ms

Resources Loaded

18.8 sec

Page Rendered

621 ms

vltava.fi screenshot

About Website

Welcome to vltava.fi homepage info - get ready to check Vltava best content right away, or after learning these important things about vltava.fi

Vltava on suurenmoinen tšekkiläinen ravintola Elielinaukiolla Helsingin sydämessä.

Visit vltava.fi

Key Findings

We analyzed Vltava.fi page load time and found that the first response time was 469 ms and then it took 19.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

vltava.fi performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.12

84/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

vltava.fi

469 ms

vltava

332 ms

vltava

1218 ms

main.css

135 ms

raflaamo.css

422 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vltava.fi, 18% (25 requests) were made to Static.xx.fbcdn.net and 17% (23 requests) were made to Raflaamo.fi. The less responsive or slowest element that took the longest time to load (12.1 sec) relates to the external source Laari.sok.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (26%)

Content Size

8.7 MB

After Optimization

6.4 MB

In fact, the total size of Vltava.fi main page is 8.7 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 5.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 285.2 kB

  • Original 343.3 kB
  • After minification 264.2 kB
  • After compression 58.1 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. This page needs HTML code to be minified as it can gain 79.1 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 285.2 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 223.8 kB

  • Original 5.9 MB
  • After minification 5.7 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. Vltava images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 1.6 MB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 634.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 1.6 MB or 72% of the original size.

CSS Optimization

-86%

Potential reduce by 177.1 kB

  • Original 204.7 kB
  • After minification 176.6 kB
  • After compression 27.6 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. Vltava.fi needs all CSS files to be minified and compressed as it can save up to 177.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (45%)

Requests Now

128

After Optimization

71

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

Accessibility Review

vltava.fi accessibility score

85

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

High

Links do not have a discernible 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

High

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

High

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

Best Practices

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

Page has valid source maps

SEO Factors

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

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

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