3.8 sec in total
385 ms
3 sec
421 ms
Visit nefertitis.cz now to see the best up-to-date NEFERTITIS content for Czech Republic and also check out these interesting facts you probably never knew about nefertitis.cz
Internetový obchod se šperky, polodrahokamy, drahými kameny, bytovými doplňky a vůněmi
Visit nefertitis.czWe analyzed Nefertitis.cz page load time and found that the first response time was 385 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
nefertitis.cz performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value9.4 s
1/100
25%
Value7.4 s
27/100
10%
Value1,180 ms
21/100
30%
Value0
100/100
15%
Value10.8 s
22/100
10%
385 ms
406 ms
926 ms
215 ms
642 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 70% of them (33 requests) were addressed to the original Nefertitis.cz, 6% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Nefertitis.cz.
Page size can be reduced by 141.8 kB (10%)
1.5 MB
1.3 MB
In fact, the total size of Nefertitis.cz main page is 1.5 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.2 MB which makes up the majority of the site volume.
Potential reduce by 66.2 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 66.2 kB or 77% of the original size.
Potential reduce by 74.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. NEFERTITIS images are well optimized though.
Potential reduce by 821 B
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.
Number of requests can be reduced by 11 (26%)
43
32
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NEFERTITIS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
nefertitis.cz
385 ms
nefertitis.cz
406 ms
www.nefertitis.cz
926 ms
web.78.css
215 ms
web.52.js
642 ms
web.78.css
430 ms
platform.js
21 ms
web.52.js
640 ms
widget.js
113 ms
gtm.js
166 ms
all.js
121 ms
cs.svg
183 ms
popup_login_bg.jpg
264 ms
logo.svg
307 ms
hexagon.svg
393 ms
blank.gif
393 ms
hp_cover.jpg
393 ms
1279_banner-web.png
575 ms
1281_1200x400.jpg
578 ms
1283_cz.png
674 ms
hpc1.png
578 ms
hpc2.png
670 ms
hpc3.png
577 ms
hpc4.png
670 ms
hp_horoscope.jpg
671 ms
loading.gif
671 ms
pozadi-kniha.png
672 ms
shop_2.png
1043 ms
shop_1.png
877 ms
shop-nausnice-385x216.png
961 ms
ruka.jpg
765 ms
logo_hlava.svg
766 ms
punc.png
771 ms
certificate.svg
876 ms
comgate_all.png
878 ms
hlava_footer.svg
879 ms
nefertitis.woff
882 ms
cb=gapi.loaded_0
12 ms
badge
191 ms
all.js
9 ms
f99415b893fe534b074fafd0740a8c61.js
576 ms
js
94 ms
destination
53 ms
rc.js
691 ms
no_rating.png
101 ms
landing
85 ms
retargeting
99 ms
nefertitis.cz 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
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.
nefertitis.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
nefertitis.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 Nefertitis.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 Nefertitis.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.
nefertitis.cz
Open Graph description is not detected on the main page of NEFERTITIS. 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: