Access velux.no. VELUX takvinduer – forvandler rom med dagslys

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value7,460 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

velux.no

148 ms

velux.no

283 ms

www.velux.no

661 ms

index-3a164889.css

200 ms

icon-sprite-678a43e0.svg

342 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that all of those requests were addressed to Velux.no and no external sources were called. The less responsive or slowest element that took the longest time to load (661 ms) belongs to the original domain Velux.no.

Content Size

220.3 kB

After Optimization

26.9 kB

In fact, the total size of Velux.no main page is 220.3 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. 35% of websites need less resources to load. HTML takes 129.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 106.4 kB

Original 129.3 kB
After minification 125.3 kB
After compression 22.9 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 106.4 kB or 82% of the original size.

CSS Optimization

-96%

Potential reduce by 87.0 kB

Original 91.0 kB
After minification 4.0 kB
After compression 3.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. Velux.no needs all CSS files to be minified and compressed as it can save up to 87.0 kB or 96% of the original size.

Requests Now

After Optimization

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VELUX. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

NN
Language Claimed

NN
Encoding

UTF-8

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