12.5 sec in total
441 ms
11.8 sec
254 ms
Click here to check amazing Digidy content. Otherwise, check out these important facts you probably never knew about digidy.com
Internetová řešení
Visit digidy.comWe analyzed Digidy.com page load time and found that the first response time was 441 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
digidy.com performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value3.9 s
51/100
25%
Value6.3 s
42/100
10%
Value170 ms
92/100
30%
Value0.172
70/100
15%
Value4.0 s
87/100
10%
441 ms
569 ms
462 ms
482 ms
488 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Digidy.com, 93% (77 requests) were made to Digidy.cz and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source Digidy.cz.
Page size can be reduced by 525.3 kB (27%)
2.0 MB
1.4 MB
In fact, the total size of Digidy.com main page is 2.0 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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 21.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 21.4 kB or 77% of the original size.
Potential reduce by 20.7 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. Digidy images are well optimized though.
Potential reduce by 321.4 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 321.4 kB or 68% of the original size.
Potential reduce by 161.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. Digidy.com needs all CSS files to be minified and compressed as it can save up to 161.8 kB or 81% of the original size.
Number of requests can be reduced by 50 (64%)
78
28
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digidy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
digidy.com
441 ms
www.digidy.cz
569 ms
style.css
462 ms
red.css
482 ms
boxed.css
488 ms
skeleton.css
490 ms
javascript.css
500 ms
shortcodes.css
3077 ms
style.css
914 ms
boxed.css
2471 ms
switcher.css
1461 ms
custom.css
2480 ms
icons.css
2728 ms
jetpack.css
3488 ms
jquery.js
3604 ms
jquery-migrate.min.js
3499 ms
jquery.ui.totop.js
3492 ms
jquery.easing.1.3.min.js
4480 ms
jquery-ui.min.js
4683 ms
jquery.cookie.js
4492 ms
jquery.uniform.min.js
4494 ms
ddsmoothmenu.js
4523 ms
jquery.flexslider.js
4505 ms
jquery.eislideshow.js
4938 ms
jquery.iconmenu.js
4941 ms
colortip.js
5315 ms
tytabs.js
5497 ms
carousel.js
5516 ms
jquery.prettyPhoto.js
5507 ms
jquery.isotope.min.js
5510 ms
selectnav.js
5520 ms
custom.js
5423 ms
jflickrfeed.min.js
5873 ms
comment-reply.min.js
5952 ms
devicepx-jetpack.js
35 ms
wp-embed.min.js
5619 ms
e-201610.js
35 ms
fonts.css
5516 ms
base.css
5510 ms
skeleton.css
5535 ms
javascript.css
5635 ms
shortcodes.css
5836 ms
custom.css
6095 ms
uniform.css
458 ms
ga.js
86 ms
wp-emoji-release.min.js
449 ms
TitilliumText22L004-webfont.woff
696 ms
digidy-logo1.jpg
481 ms
prezentace-02-webove-prezentace2.jpg
899 ms
prezentace-01-mobilni-aplikace.jpg
481 ms
prezentace-04-internetovy-marketing1.jpg
979 ms
prezentace-03-branding1.jpg
1057 ms
webdesign.png
906 ms
smartphone.png
893 ms
strategy.png
804 ms
branding.png
1258 ms
martinkup-cz-01.jpg
1885 ms
synotw-synotloterie-cz-00.jpg
1453 ms
michaeljaymusic-com-002.jpg
1685 ms
escadra-com-00.jpg
1809 ms
edildomus-cz-00.jpg
1806 ms
cesky-plyn-cz-00.jpg
1982 ms
cardetect-cz-00.jpg
2100 ms
bigfood-cz-00.jpg
2241 ms
aip-engineering-cz-00.jpg
2368 ms
tesla-blatna-cz-00.jpg
2818 ms
synotlotto-synotloterie-cz-00.jpg
2841 ms
sgs-synotloterie-00.jpg
2825 ms
synot.png
2211 ms
tesla-blatna.png
2730 ms
aip-engineering.png
2721 ms
moravan.png
2986 ms
filmfest.png
3178 ms
twitter-icon.png
3182 ms
twitter.png
3285 ms
flickr.png
3445 ms
skype.png
3429 ms
rss.png
3711 ms
TitilliumText22L005-webfont.woff
3939 ms
totop.png
3674 ms
__utm.gif
24 ms
g.gif
22 ms
TitilliumText22L003-webfont.woff
3563 ms
digidy.com accessibility score
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
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.
digidy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
digidy.com 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digidy.com can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it does not match the claimed English language. Our system also found out that Digidy.com 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.
digidy.com
Open Graph data is detected on the main page of Digidy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: