4.5 sec in total
389 ms
3.8 sec
308 ms
Welcome to next.cz homepage info - get ready to check NEXT best content for Czech Republic right away, or after learning these important things about next.cz
NEXT, prověřené vchodové bezpečnostní dveře do bytu i domu, zabezpečovací systémy, folie na okna, mříže, alarm, bezpečnostní kamery.
Visit next.czWe analyzed Next.cz page load time and found that the first response time was 389 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
next.cz performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value12.2 s
0/100
25%
Value8.4 s
18/100
10%
Value860 ms
33/100
30%
Value0.251
49/100
15%
Value10.9 s
21/100
10%
389 ms
942 ms
193 ms
288 ms
574 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 72% of them (54 requests) were addressed to the original Next.cz, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to C.imedia.cz. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Next.cz.
Page size can be reduced by 646.4 kB (25%)
2.6 MB
2.0 MB
In fact, the total size of Next.cz main page is 2.6 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 58.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 18.9 kB, which is 27% 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 58.8 kB or 83% of the original size.
Potential reduce by 3.2 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. NEXT images are well optimized though.
Potential reduce by 277.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 277.8 kB or 74% of the original size.
Potential reduce by 306.7 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. Next.cz needs all CSS files to be minified and compressed as it can save up to 306.7 kB or 86% of the original size.
Number of requests can be reduced by 47 (69%)
68
21
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NEXT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
next.cz
389 ms
www.next.cz
942 ms
wysiwyg.css
193 ms
jquery-ui-1.8.17.custom.css
288 ms
bootstrap.css
574 ms
slider.css
195 ms
theme-default.css
426 ms
select2.css
381 ms
theme-custom.css
484 ms
jquery-1.7.2.min.js
525 ms
jquery-ui.js
8 ms
jquery.coda-slider-2.0.js
384 ms
bootstrap.min.js
772 ms
response.min.js
487 ms
bootstrap-slider.js
530 ms
jquery.slides.min.js
590 ms
jquery.number.min.js
585 ms
jquery.iframetracker.js
635 ms
jquery-cookie.js
634 ms
jquery.fancybox-1.3.4.css
662 ms
validationEngine.jquery.css
681 ms
jquery.fancybox-1.3.4.js
694 ms
fancy-load.js
793 ms
jquery.pngFix.pack.js
791 ms
jquery.jgrowl.css
756 ms
jquery.jgrowl.min.js
790 ms
default.js
907 ms
jquery.validationEngine-cz.js
1106 ms
jquery.validationEngine.js
1269 ms
retargeting.js
333 ms
conversion.js
35 ms
css
24 ms
analytics.js
27 ms
fbevents.js
138 ms
logo.png
359 ms
zamereni_zdarma.png
337 ms
cz_vlajka.jpg
441 ms
sk_vlajka.jpg
373 ms
en_vlajka.jpg
446 ms
de_vlajka.jpg
457 ms
at_vlajka.jpg
461 ms
ro_vlajka.jpg
479 ms
vt_vlajka.jpg
567 ms
o-hpbanner1.jpg
1247 ms
o-h_banner_3.jpg
1746 ms
dvere_641x393(1).jpg
859 ms
art_img2.jpg
687 ms
next_video_313x213_01.jpg
1036 ms
101_311x430.jpg
858 ms
dvere_do_prvniho_bytu_643x430.jpg
1121 ms
o-centralgroup_cz_logo.jpg
972 ms
o-finep_cz_logo.jpg
960 ms
o-evva_cz_logo.jpg
1082 ms
iko-fb.png
1108 ms
iko-yt.png
1140 ms
detail-prev.png
1176 ms
detail-next.png
1193 ms
divider.png
1207 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
43 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
43 ms
collect
26 ms
collect
62 ms
18 ms
sdk.js
205 ms
retargeting
113 ms
48 ms
log.js
31 ms
index.php
750 ms
index.php
807 ms
www.next.cz.js
201 ms
31 ms
39 ms
xd_arbiter.php
216 ms
xd_arbiter.php
421 ms
next.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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
next.cz 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
Page has valid source maps
next.cz 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
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Next.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 Next.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.
next.cz
Open Graph data is detected on the main page of NEXT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: