Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

vaalikone.fi

Helsingin Sanomat vaalikone – Presidentinvaalit 2024 | Tervetuloa vaalikoneeseen

Page Load Speed

6.5 sec in total

First Response

346 ms

Resources Loaded

5.9 sec

Page Rendered

304 ms

vaalikone.fi screenshot

About Website

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

Kokeile HS:n vaalikoneella, ketä ehdokasta kannattaa äänestää. Uudistunut vaalikone kertoo, kuka ehdokkaista kannattaa samoja asioita ja kuka on arvomaailmaltaan sinua lähimpänä

Visit vaalikone.fi

Key Findings

We analyzed Vaalikone.fi page load time and found that the first response time was 346 ms and then it took 6.2 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

vaalikone.fi performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value1.319

1/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

vaalikone.fi

346 ms

422 ms

hs-plugins-update4.js

390 ms

sanoma_bt.js

137 ms

desktop-all.css

340 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 30% of them (23 requests) were addressed to the original Vaalikone.fi, 13% (10 requests) were made to Hs.fi and 6% (5 requests) were made to Files.snstatic.fi. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Hs.spring-tns.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.9 kB (50%)

Content Size

844.0 kB

After Optimization

419.1 kB

In fact, the total size of Vaalikone.fi main page is 844.0 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. 50% of websites need less resources to load. Javascripts take 411.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 130.7 kB

  • Original 154.7 kB
  • After minification 115.1 kB
  • After compression 24.0 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 39.6 kB, which is 26% 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 130.7 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 29.6 kB

  • Original 277.8 kB
  • After minification 248.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. Obviously, Vaalikone needs image optimization as it can save up to 29.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 264.6 kB

  • Original 411.6 kB
  • After minification 399.0 kB
  • After compression 147.0 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 264.6 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (63%)

Requests Now

68

After Optimization

25

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

Accessibility Review

vaalikone.fi accessibility score

86

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

Links do not have a discernible name

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

vaalikone.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

SEO Factors

vaalikone.fi SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 Vaalikone.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 Vaalikone.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 data is detected on the main page of Vaalikone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: