Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

finnair.fi

Lennot ja lentolippuja yli 80 kohteeseen maailmalla | Finnair Suomi

Page Load Speed

3.8 sec in total

First Response

287 ms

Resources Loaded

2.4 sec

Page Rendered

1.1 sec

finnair.fi screenshot

About Website

Click here to check amazing Finnair content for Finland. Otherwise, check out these important facts you probably never knew about finnair.fi

Finnair lentää Eurooppaan, Pohjois-Amerikkaan ja Aasiaan. Moderni laivasto – enemmän mukavuutta ja pienemmät päästöt. Varaa lentosi jo tänään.

Visit finnair.fi

Key Findings

We analyzed Finnair.fi page load time and found that the first response time was 287 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

finnair.fi performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value3,990 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

finnair.fi

287 ms

2026 ms

index.05281.css

131 ms

runtime.72ed0476c4dce0d4.js

164 ms

polyfills.d08231e117e41570.js

162 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Finnair.fi, 38% (10 requests) were made to Cdn.finnair.com and 38% (10 requests) were made to Cms.finnair.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Finnair.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.1 MB (76%)

Content Size

5.4 MB

After Optimization

1.3 MB

In fact, the total size of Finnair.fi main page is 5.4 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. 55% of websites need less resources to load. Javascripts take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 1.5 MB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 303.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. 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 1.5 MB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 74.0 kB
  • After minification 74.0 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. Finnair images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 2.6 MB

  • Original 3.5 MB
  • After minification 3.5 MB
  • After compression 932.2 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 2.6 MB or 73% of the original size.

CSS Optimization

-51%

Potential reduce by 12.3 kB

  • Original 24.2 kB
  • After minification 24.0 kB
  • After compression 11.9 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. Finnair.fi needs all CSS files to be minified and compressed as it can save up to 12.3 kB or 51% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (25%)

Requests Now

20

After Optimization

15

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

Accessibility Review

finnair.fi accessibility score

79

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

finnair.fi best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

finnair.fi SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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