8.4 sec in total
494 ms
7.5 sec
360 ms
Visit worldcup.bg now to see the best up-to-date Worldcup content and also check out these interesting facts you probably never knew about worldcup.bg
Световно първенство по футбол, Бразилия 2014, Мондиал - новини, мачове, галерия, история, коментари, видео, статистика
Visit worldcup.bgWe analyzed Worldcup.bg page load time and found that the first response time was 494 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
worldcup.bg performance score
494 ms
766 ms
489 ms
250 ms
255 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Worldcup.bg, 76% (108 requests) were made to Worldcup.sportal.bg and 4% (6 requests) were made to Sportaladbg.hit.gemius.pl. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Worldcup.sportal.bg.
Page size can be reduced by 978.8 kB (36%)
2.7 MB
1.7 MB
In fact, the total size of Worldcup.bg main page is 2.7 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 61.7 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 61.7 kB or 79% of the original size.
Potential reduce by 209.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. Obviously, Worldcup needs image optimization as it can save up to 209.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 621.6 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 621.6 kB or 78% of the original size.
Potential reduce by 86.5 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. Worldcup.bg needs all CSS files to be minified and compressed as it can save up to 86.5 kB or 85% of the original size.
Number of requests can be reduced by 27 (20%)
138
111
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Worldcup. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
worldcup.bg
494 ms
worldcup.sportal.bg
766 ms
style.css
489 ms
live.css
250 ms
jquery.countdown.css
255 ms
jquery-1.11.0.min.js
9 ms
jquery-ui-1.10.4.custom.js
1057 ms
custom-form-elements.js
267 ms
jquery.flexslider.js
507 ms
jquery.textresizer.js
381 ms
global.js
388 ms
jquery.countdown.js
534 ms
ado.js
530 ms
jwplayer.js
763 ms
analytics.js
20 ms
xgemius.js
390 ms
collect
11 ms
collect
54 ms
ga-audiences
33 ms
ad.js
141 ms
fpdata.js
140 ms
sarg=56E9D0BF9E756327
139 ms
ad.js
141 ms
00030.png
132 ms
00028.png
279 ms
00018.png
122 ms
00025.png
248 ms
00001.png
133 ms
00009.png
254 ms
00021.png
245 ms
00007.png
260 ms
00013.png
277 ms
00003271.jpg
769 ms
00003251.jpg
991 ms
00003252.jpg
769 ms
00003247.jpg
793 ms
00003271.jpg
410 ms
00003251.jpg
409 ms
00003252.jpg
541 ms
00003247.jpg
543 ms
00003263.jpg
1134 ms
00003248.jpg
1030 ms
00003246.jpg
890 ms
00003245.jpg
1304 ms
00003244.jpg
1309 ms
00003240.jpg
1113 ms
00003238.jpg
1385 ms
00003237.jpg
1271 ms
1_thumb.jpg
1252 ms
2_thumb.jpg
1474 ms
3_thumb.jpg
1370 ms
4_thumb.jpg
1392 ms
5_thumb.jpg
1437 ms
6_thumb.jpg
1440 ms
7_thumb.jpg
1488 ms
8_thumb.jpg
1508 ms
9_thumb.jpg
1513 ms
10_thumb.jpg
1570 ms
11_thumb.jpg
1572 ms
sarg=56E9D0BF9E756327%7C_cdata%3A380695_0%2C897843_0
140 ms
lsget.html
338 ms
12_thumb.jpg
1479 ms
referees.jpg
1484 ms
cups.jpg
1630 ms
all.js
68 ms
sarg=56E9D0BF9E756327%7C_cdata%3A380695_0%2C897843_0
142 ms
139 ms
xd_arbiter.php
85 ms
xd_arbiter.php
160 ms
balls.jpg
1395 ms
mascots.jpg
1598 ms
1.png
1590 ms
2.png
1703 ms
3.png
1823 ms
4.png
1733 ms
gapro-2.js
64 ms
show_ads.js
6 ms
sarg=56E9D0BF9E756327%7C_cdata%3A380695_0%2C897843_0
139 ms
rexdot.js
140 ms
ca-pub-7031831557830335.js
32 ms
zrt_lookup.html
35 ms
show_ads_impl.js
55 ms
5.png
1738 ms
6.png
1696 ms
ads
198 ms
osd.js
5 ms
sarg=56E9D0BF9E756327%7C_cdata%3A380695_0%2C897843_0
139 ms
7.png
1572 ms
8.png
1781 ms
atrk.js
36 ms
sarg=56E9D0BF9E756327%7C_cdata%3A380695_0%2C897843_0
140 ms
atrk.gif
32 ms
test.png
21 ms
9.png
1366 ms
10.png
1451 ms
11.png
1480 ms
xd_arbiter.php
37 ms
12.png
1574 ms
13.png
1648 ms
14.png
1468 ms
15.png
1553 ms
16.png
1266 ms
17.png
1191 ms
18.png
1255 ms
19.png
1281 ms
0000123043,c=0,h=554.bild.jpg
1575 ms
000000139Liderin3.jpeg.jpg
1407 ms
26.jpg
1586 ms
00000027.jpg
1312 ms
logo.png
1465 ms
header_bg_top.png
1358 ms
search_icon.png
1458 ms
bg.jpg
1587 ms
map.png
1890 ms
comm_icon.png
1520 ms
view_icon.png
1469 ms
arrow_up.png
1493 ms
koboardwc_new.jpg
2035 ms
00006.png
1560 ms
00016.png
1536 ms
00004.png
1441 ms
00010.png
1363 ms
00024.png
1462 ms
00029.png
1346 ms
00020.png
1319 ms
arrow_down.png
1340 ms
list_icon.png
1345 ms
grid_active_icon.png
1341 ms
comm_icon_small.png
1398 ms
view_icon_small.png
1412 ms
title_smoke_big.png
1480 ms
title_smoke_small.png
1426 ms
359.jpg
1500 ms
photo_icon.png
1260 ms
title_smoke_small_2.png
1367 ms
footer_bg.png
1605 ms
sportal_logo.png
1450 ms
radio.png
128 ms
slider_arrow_prev_2.png
126 ms
slider_arrow_next_2.png
133 ms
slide_arrow_prev.png
125 ms
slide_arrow_next.png
243 ms
worldcup.bg SEO score
BG
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worldcup.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Worldcup.bg 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.
worldcup.bg
Open Graph description is not detected on the main page of Worldcup. 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: