3.4 sec in total
311 ms
2.6 sec
441 ms
Visit xella.rs now to see the best up-to-date Xella content and also check out these interesting facts you probably never knew about xella.rs
Visit xella.rsWe analyzed Xella.rs page load time and found that the first response time was 311 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
xella.rs performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value13.0 s
0/100
25%
Value13.5 s
2/100
10%
Value3,070 ms
2/100
30%
Value0.112
86/100
15%
Value14.0 s
10/100
10%
311 ms
326 ms
435 ms
202 ms
8 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 Xella.rs, 69% (18 requests) were made to Ytong.rs and 15% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Ytong.rs.
Page size can be reduced by 526.4 kB (14%)
3.7 MB
3.2 MB
In fact, the total size of Xella.rs main page is 3.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. 30% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 36.8 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 14.6 kB, which is 35% 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 36.8 kB or 87% of the original size.
Potential reduce by 24.9 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 256.8 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 256.8 kB or 66% 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.rs needs all CSS files to be minified and compressed as it can save up to 207.8 kB or 73% of the original size.
Number of requests can be reduced by 4 (19%)
21
17
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xella. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
xella.rs
311 ms
www.ytong.rs
326 ms
main.css
435 ms
head.js
202 ms
jquery-1.8.2.js
8 ms
script.js
508 ms
urchin.js
8 ms
homepage-slider1-A3.jpg
804 ms
homepage-slider2.jpg
942 ms
ytong-slider-03.jpg
1069 ms
homepage_slider_4_v2.jpg
995 ms
renoviranje_slider.jpg
888 ms
homepage-box-ytong-kuce.jpg
438 ms
homepage-box-zadovoljni-vlasnici.jpg
726 ms
homepage-box-besplatni-servis.jpg
1018 ms
homepage-teser-video-2.jpg
1074 ms
homepage-teser-upustvo.jpg
1249 ms
homepage-teser-stovarista.jpg
1319 ms
analytics.js
45 ms
specification_text_json.php
419 ms
specification_text_json.php
422 ms
__utm.gif
24 ms
collect
14 ms
DINWebPro-Medium.woff
1093 ms
DINWebPro.woff
1144 ms
DINWebPro-Bold.woff
1287 ms
xella.rs 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
[lang] attributes do not have a valid value
xella.rs 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
xella.rs SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
N/A
SR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xella.rs 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 Serbian. Our system also found out that Xella.rs 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.rs
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: