5.5 sec in total
344 ms
4.4 sec
766 ms
Click here to check amazing Xella content. Otherwise, check out these important facts you probably never knew about xella.se
Välkommen till Ytong Silka byggmaterial i lättbetong och kalksandsten
Visit xella.seWe analyzed Xella.se page load time and found that the first response time was 344 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
xella.se performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value8.6 s
1/100
25%
Value9.2 s
13/100
10%
Value450 ms
63/100
30%
Value0.245
51/100
15%
Value9.0 s
34/100
10%
344 ms
371 ms
488 ms
211 ms
565 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 84% of them (21 requests) were addressed to the original Xella.se, 8% (2 requests) were made to Upcoming.backoffice.xella.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Xella.se.
Page size can be reduced by 508.4 kB (11%)
4.7 MB
4.2 MB
In fact, the total size of Xella.se main page is 4.7 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. 25% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 40.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. This page needs HTML code to be minified as it can gain 13.8 kB, which is 30% 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 40.9 kB or 88% of the original size.
Potential reduce by 35.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. Xella images are well optimized though.
Potential reduce by 223.9 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 223.9 kB or 65% of the original size.
Potential reduce by 207.8 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. Xella.se needs all CSS files to be minified and compressed as it can save up to 207.8 kB or 73% of the original size.
We found no issues to fix!
20
20
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xella. According to our analytics all requests are already optimized.
xella.se
344 ms
www.xella.se
371 ms
main.css
488 ms
head.js
211 ms
script.js
565 ms
2580x1260_S_fair_nordbygg.jpg
1285 ms
eco_topslider_2560x1280.jpg
1048 ms
multipor_slider2560x1280.jpg
1515 ms
energyplus_slider_2560x1280.jpg
1545 ms
cover_newsteaser_S_fb.png
604 ms
enfamiljshus-sv.jpg
840 ms
Bargeteheide1.jpg
1722 ms
GMW_Seniorenpflegeheim_1.jpg
1882 ms
Forum1.jpg
2175 ms
Bahnhof_Schwetzingen_Aussen1.jpg
2264 ms
Teaser_1_-_Arbeta_pa_Xella.png
2489 ms
Teaser_2_-_Kontakt.png
2466 ms
Teaser_3_-_Produkter.png
2650 ms
DINWebPro-Medium.woff
2889 ms
DINWebPro.woff
3010 ms
DINWebPro-Bold.woff
3068 ms
specification_text_json.php
830 ms
specification_text_json.php
832 ms
ga.js
28 ms
__utm.gif
16 ms
xella.se accessibility score
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
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
xella.se 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
xella.se 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
N/A
SV
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xella.se can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Swedish. Our system also found out that Xella.se 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.
xella.se
Open Graph description is not detected on the main page of Xella. 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: