5.1 sec in total
679 ms
3.7 sec
707 ms
Visit oxid.cz now to see the best up-to-date Oxid content and also check out these interesting facts you probably never knew about oxid.cz
Bez sekání. Bez starostí. Na zelenou. Poskytujeme pevný internet nebo třeba vychytanou IPTV. Objevte všechny naše telekomunikační služby.
Visit oxid.czWe analyzed Oxid.cz page load time and found that the first response time was 679 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
oxid.cz performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value9.1 s
1/100
25%
Value5.9 s
48/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value5.0 s
76/100
10%
679 ms
822 ms
431 ms
33 ms
976 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Oxid.cz, 3% (1 request) were made to Google.com and 3% (1 request) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Nordictelecom.cz.
Page size can be reduced by 311.5 kB (16%)
1.9 MB
1.6 MB
In fact, the total size of Oxid.cz main page is 1.9 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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 276.4 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 276.4 kB or 91% of the original size.
Potential reduce by 34.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. Oxid images are well optimized though.
Potential reduce by 1.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 0 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. Oxid.cz has all CSS files already compressed.
Number of requests can be reduced by 4 (13%)
31
27
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oxid. 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.
www.nordictelecom.cz
679 ms
nordictelecom.cz
822 ms
main-d271a824c9821fc96c15.css
431 ms
api.js
33 ms
main-d271a824c9821fc96c15.bundle.js
976 ms
recaptcha__cs.js
290 ms
gtm.js
158 ms
logo-nordic.svg
168 ms
logo-nordic-short.svg
291 ms
basket.svg
406 ms
search.svg
401 ms
phone.svg
402 ms
vracime_do_telekomunikaci_svobodu_-_nordic_telecom.jpg
615 ms
zeleny_internet_-_nordic_telecom.jpg
405 ms
nordic_tv-iptv-2.jpg
731 ms
zakaznicka_pece_nordic_telecom_1.jpg
724 ms
internet-za-295-kc.jpg
519 ms
ajtak_na_prijmu.jpg
730 ms
prima-comedy-2.png
590 ms
viasat_history_218Y14q.png
627 ms
sport2-1.png
700 ms
sporty_tv.png
724 ms
love_nature.png
737 ms
iptv-na-3-msice-zdarma.jpg
811 ms
opticke_vlakno.jpg
1046 ms
prima_fresh_festival_polreich.jpg
940 ms
internet-100-mb.jpg
948 ms
internet-speed-test.jpg
1052 ms
prima-fresh-festival-soutez-listky-2024.jpg
848 ms
zavolame_vam_-_nordic_telecom.jpg
923 ms
ajtaka_na_prijmi_-_nordic_telecom.jpg
960 ms
success.png
1031 ms
a65cb41cdc472c0555a24743376eaa88.ttf
1104 ms
cc90ab08cef32b25dff8a2e9cac9152c.ttf
1116 ms
70d44b11be934b7f5157fecabbcd4d63.otf
1018 ms
b655dc3e.js
419 ms
oxid.cz 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
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
oxid.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
oxid.cz 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
Tap targets are not sized appropriately
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oxid.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Oxid.cz 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.
oxid.cz
Open Graph data is detected on the main page of Oxid. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: