Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

velux.fi

VELUX-kattoikkunat, -tasakaton ikkunat, -valotunnelit ja -verhot

Page Load Speed

2.3 sec in total

First Response

265 ms

Resources Loaded

1.7 sec

Page Rendered

296 ms

velux.fi screenshot

About Website

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

VELUX on maailman johtava kattoikkunoiden, tasakaton ikkunoiden, valotunnelien ja kattoikkunaverhojen valmistaja – katso koko tuotevalikoimamme täältä.

Visit velux.fi

Key Findings

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

Performance Metrics

velux.fi performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value6,700 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value31.5 s

0/100

10%

Network Requests Diagram

velux.fi

265 ms

www.velux.fi

294 ms

export

610 ms

tailwind.min.css

46 ms

marketing.min.css

108 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Velux.fi, 61% (25 requests) were made to Cdn-marketing.velux.com and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (610 ms) relates to the external source Velux.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.7 kB (21%)

Content Size

1.1 MB

After Optimization

871.9 kB

In fact, the total size of Velux.fi main page is 1.1 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. 80% 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 466.9 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 130.7 kB

  • Original 148.4 kB
  • After minification 90.6 kB
  • After compression 17.7 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 57.8 kB, which is 39% 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 88% of the original size.

Image Optimization

-3%

Potential reduce by 14.8 kB

  • Original 466.9 kB
  • After minification 452.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. VELUX images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 88.0 kB

  • Original 207.5 kB
  • After minification 207.5 kB
  • After compression 119.5 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 88.0 kB or 42% of the original size.

CSS Optimization

-0%

Potential reduce by 100 B

  • Original 282.7 kB
  • After minification 282.7 kB
  • After compression 282.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. Velux.fi has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (44%)

Requests Now

34

After Optimization

19

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

Accessibility Review

velux.fi accessibility score

77

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

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

Missing source maps for large first-party JavaScript

SEO Factors

velux.fi SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Velux.fi can be misinterpreted by Google and other search engines. Our service has detected that Finnish is used on the page, and it does not match the claimed English language. Our system also found out that Velux.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 VELUX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: