5.9 sec in total
353 ms
5.3 sec
266 ms
Welcome to img24.eu homepage info - get ready to check Img 24 best content right away, or after learning these important things about img24.eu
Nahrávejte obrázky zdarma. Spolehlivý obrázkový hosting od roku 2010.
Visit img24.euWe analyzed Img24.eu page load time and found that the first response time was 353 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
img24.eu performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value6.4 s
9/100
25%
Value8.2 s
20/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
353 ms
1982 ms
233 ms
237 ms
590 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Img24.eu, 33% (40 requests) were made to Img24.cz and 18% (22 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Img24.cz.
Page size can be reduced by 194.1 kB (19%)
1.0 MB
806.3 kB
In fact, the total size of Img24.eu main page is 1.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. 70% of websites need less resources to load. Images take 752.3 kB which makes up the majority of the site volume.
Potential reduce by 18.6 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 2.8 kB, which is 11% 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 18.6 kB or 73% of the original size.
Potential reduce by 34.4 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. Img 24 images are well optimized though.
Potential reduce by 127.3 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 127.3 kB or 62% of the original size.
Potential reduce by 13.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. Img24.eu needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 79% of the original size.
Number of requests can be reduced by 67 (56%)
120
53
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Img 24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
img24.eu
353 ms
img24.cz
1982 ms
style.css
233 ms
reklama.css
237 ms
jquery-1.7.2.min.js
590 ms
genjscript.js
237 ms
phpjs_00029.js
358 ms
jquery.jdMenu.js
343 ms
jquery.bgiframe.js
462 ms
jquery.positionBy.js
470 ms
jquery.dimensions.js
470 ms
pixlr.js
573 ms
lightbox.css
610 ms
lightbox.js
692 ms
plusone.js
60 ms
widgets.js
22 ms
ag.php
612 ms
simple-slider.js
712 ms
simple-slider-volume.css
714 ms
all.js
21 ms
main_bg.png
577 ms
site_logo.png
346 ms
blue_box_bg.gif
239 ms
input_bg.gif
308 ms
nav_mem_bar.gif
327 ms
pc_foot_bg.gif
333 ms
progress_bar.gif
544 ms
tbl_foot_bg.gif
475 ms
tbl_top_bg.gif
537 ms
bxlayout_prev.png
1675 ms
stdlayout_prev.png
1442 ms
cb=gapi.loaded_0
37 ms
02477503979372921108.png
350 ms
78235434286688772280.png
352 ms
24409744928291664352.png
354 ms
none.png
475 ms
vtip.php
572 ms
menu.png
656 ms
prava_roh.png
759 ms
iphone_lezici_nahore.png
945 ms
iphone_lezici_leva.png
1224 ms
iphone_lezici_prava.png
1274 ms
iphone_lezici_dole.png
1222 ms
125 ms
ajs.php
245 ms
xd_arbiter.php
24 ms
xd_arbiter.php
35 ms
script.js
326 ms
lg.php
244 ms
ajax-loader.gif
846 ms
cookie
357 ms
context
133 ms
afr.php
241 ms
leva_roh.png
901 ms
ajs.php
230 ms
likebox.php
227 ms
95403254.jpg
457 ms
banner-packa.png
457 ms
banner-logo.png
454 ms
impression
454 ms
iphone.php
590 ms
lg.php
431 ms
context
433 ms
lg.php
426 ms
paticka_odkaz.png
540 ms
dot.asp
408 ms
E3TzvQNU166.css
74 ms
Q-OWgaJvbhn.css
75 ms
BsqupWYzsUW.css
84 ms
q68gy-v_YMF.js
85 ms
FJmpeSpHpjS.js
83 ms
0wM5s1Khldu.js
79 ms
1bNoFZUdlYZ.js
115 ms
OloiM1PZafe.js
116 ms
LTv6ZK-5zxz.js
145 ms
1FCa-btixu2.js
143 ms
Oagsvfb4VWi.js
142 ms
pObvZSrFc_4.js
142 ms
HgJbVwzBr8E.js
138 ms
H3EKDTObx05.js
141 ms
OZFAYTv-ZUg.js
182 ms
ga.js
69 ms
ping
307 ms
cb=gapi.loaded_1
21 ms
fastbutton
293 ms
loading.gif
688 ms
close.png
607 ms
276 ms
postmessageRelay
273 ms
__utm.gif
197 ms
1544550_680333395353194_3842704174051642846_n.png
206 ms
10258334_680330968686770_2655125984411779697_n.png
141 ms
12313827_609149575905731_3320482710522057857_n.jpg
134 ms
1977446_367593003407687_4059328256809551876_n.jpg
133 ms
11904748_133996416950547_2570942151930567480_n.jpg
156 ms
11035923_907161919358870_3010182621078915556_n.jpg
134 ms
12235121_1665702770376804_4984186270658318492_n.jpg
166 ms
12509695_1498614187115175_8164257443560636420_n.jpg
198 ms
12208773_1053483238030815_5081300827212750398_n.jpg
198 ms
10801630_1394173814211981_6160577167469465315_n.jpg
138 ms
12346363_489659591221668_7641514865047683278_n.jpg
140 ms
1379841_10150004552801901_469209496895221757_n.jpg
141 ms
11866255_130159373993901_3745445183281686126_n.jpg
254 ms
318513_167626083316121_1785740754_n.jpg
152 ms
12400750_1681428085446019_7991397447090014970_n.jpg
212 ms
wL6VQj7Ab77.png
46 ms
s7jcwEQH7Sx.png
45 ms
gxbPuQdXIZP.png
45 ms
cb=gapi.loaded_0
23 ms
cb=gapi.loaded_1
26 ms
like.php
112 ms
3193398744-postmessagerelay.js
28 ms
rpc:shindig_random.js
30 ms
cb=gapi.loaded_0
3 ms
95403253.jpg
336 ms
h5Lp5Et_eC4.js
14 ms
LVx-xkvaJ0b.png
6 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
8 ms
rotator.js
245 ms
print.css
118 ms
65176257587234020698.png
586 ms
img24.eu accessibility score
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
img24.eu 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
img24.eu 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
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Img24.eu 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 Img24.eu 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.
img24.eu
Open Graph description is not detected on the main page of Img 24. 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: