2.3 sec in total
265 ms
1.7 sec
296 ms
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.fiWe 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.
velux.fi performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value6.3 s
10/100
25%
Value9.5 s
12/100
10%
Value6,700 ms
0/100
30%
Value0.163
72/100
15%
Value31.5 s
0/100
10%
265 ms
294 ms
610 ms
46 ms
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 size can be reduced by 233.7 kB (21%)
1.1 MB
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.
Potential reduce by 130.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.
Potential reduce by 14.8 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.
Potential reduce by 88.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 88.0 kB or 42% of the original size.
Potential reduce by 100 B
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.
Number of requests can be reduced by 15 (44%)
34
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.
velux.fi
265 ms
www.velux.fi
294 ms
export
610 ms
tailwind.min.css
46 ms
marketing.min.css
108 ms
jquery-3.3.0.min.js
18 ms
jquery-migrate-3.3.2.js
20 ms
common.min.js
158 ms
components.min.js
160 ms
uc.js
22 ms
api.js
164 ms
sitecore-forms.min.js
121 ms
sitecore-forms.min.css
121 ms
686777ed6d.js
261 ms
gtm.js
192 ms
gtm.js
349 ms
gtm.js
308 ms
player.html
167 ms
flag_usa.png
20 ms
velux%20logo.svg
18 ms
header-bottom-bg.png
18 ms
icon-chevron-small-right.png
21 ms
facebook.png
21 ms
twitter.png
22 ms
youtube.png
45 ms
pinterest.png
44 ms
linkedin.png
43 ms
instagram.png
44 ms
veluxgothic-light.woff
33 ms
veluxgothic-bold.woff
92 ms
veluxgothic-regitalic.woff
93 ms
veluxgothic-regular.woff
91 ms
icon-chevron-small-right.png
121 ms
player.css
116 ms
player.js
142 ms
3dae5e9e6d77.js
111 ms
velux-international-id10145335.jpg
63 ms
product-catalogue.jpg
60 ms
case-study-photo-product-inspiration.jpg
63 ms
digital-tools.jpg
61 ms
WindowTypes
192 ms
velux.fi accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
velux.fi best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
velux.fi SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
FI
EN
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.
velux.fi
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: