6.3 sec in total
538 ms
5.2 sec
543 ms
Welcome to mediapool.bg homepage info - get ready to check Mediapool best content for Bulgaria right away, or after learning these important things about mediapool.bg
Най-важните събития от деня и тяхното обяснение. Качествени анализи и коментари, обективна и навременна информация. Прочетете актуалните новини.
Visit mediapool.bgWe analyzed Mediapool.bg page load time and found that the first response time was 538 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
mediapool.bg performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value3.7 s
57/100
25%
Value7.7 s
25/100
10%
Value6,600 ms
0/100
30%
Value0.337
33/100
15%
Value15.3 s
7/100
10%
538 ms
934 ms
385 ms
513 ms
265 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 55% of them (57 requests) were addressed to the original Mediapool.bg, 8% (8 requests) were made to Tpc.googlesyndication.com and 7% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mediapool.bg.
Page size can be reduced by 930.7 kB (35%)
2.6 MB
1.7 MB
In fact, the total size of Mediapool.bg 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 83.0 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 12.7 kB, which is 12% 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 83.0 kB or 79% of the original size.
Potential reduce by 276.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. Obviously, Mediapool needs image optimization as it can save up to 276.4 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 392.9 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 392.9 kB or 64% of the original size.
Potential reduce by 178.4 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. Mediapool.bg needs all CSS files to be minified and compressed as it can save up to 178.4 kB or 85% of the original size.
Number of requests can be reduced by 45 (47%)
95
50
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mediapool. 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 5 to 1 for CSS and as a result speed up the page load time.
mediapool.bg
538 ms
www.mediapool.bg
934 ms
style.css
385 ms
jquery-1.2.min.js
513 ms
weather-icons.css
265 ms
style.css
396 ms
weather-icons.js
278 ms
scripts.js
396 ms
css
24 ms
font-awesome.min.css
414 ms
cookieconsent.min.js
7 ms
analytics.js
27 ms
gpt.js
7 ms
30.gif
40 ms
hybridauth_icon_facebook.png
139 ms
hybridauth_icon_google.png
136 ms
downarrow.png
137 ms
dw_logo.png
140 ms
capital.png
263 ms
BTA_1.png
1932 ms
kafene_net1.png
398 ms
open_parliament.png
262 ms
otvoreno_obshtestvo.png
436 ms
sadebni_reportaji.png
300 ms
safety%20net.png
388 ms
vapreki.png
524 ms
new_logo.png
438 ms
facebook_icon.png
516 ms
twitter_icon.png
528 ms
googleplus_icon.png
558 ms
all.js
268 ms
logo_header.png
557 ms
pubads_impl_81.js
26 ms
fbicon.png
638 ms
twittericon.png
645 ms
googleplusicon.png
647 ms
search_button.png
685 ms
menu_raz.png
685 ms
menu_raz.png
754 ms
modal_close.png
774 ms
collect
53 ms
weathericons-regular-webfont.woff
1016 ms
segoeuil.woff
2047 ms
ads
324 ms
container.html
26 ms
collect
79 ms
ajs.php
154 ms
107 ms
adi-513cc264.js
577 ms
ajs.php
610 ms
61 ms
xd_arbiter.php
277 ms
xd_arbiter.php
419 ms
adx.js
239 ms
343318078352019663
41 ms
osd.js
11 ms
0b898ef48ecbf1fd97640a7627d7dab0.jpg
1773 ms
e8efcec46b4340bb82eb16468bf4249a.jpg
1185 ms
984a83bd9cf86ae25125de4aee8ab6cd.jpg
1450 ms
51fef419fa4fa0a0af80f6018e7035f0.jpg
856 ms
39927503da9c592c8b9f556cfb1b3bc2.jpg
1420 ms
55bd90163639f1115530d3a546155e9c.jpg
1204 ms
275cb2b20223cdc85f73339df8f0301a.jpg
1461 ms
9c6cf4a6b98eab1440b4ebeb481218bd.jpg
1332 ms
6463b87e2e804b2237a5b448df8b1ffe.jpg
1368 ms
40f52e507742ae7c6c5c37f2740b3d28.jpg
1460 ms
216 ms
2576d4a154919477a1896ff7a769f6f7.jpg
1488 ms
a039b99fae790c9164847ad5ff2cc83a.jpg
1532 ms
29cf370f03251cd3926aed75b7fc3133.jpg
1691 ms
3ddfeef96f7ea8df05b5f678abfb319f.jpg
1730 ms
circle_bullet_blue3.png
1556 ms
circle_bullet_palered.png
1615 ms
adl-39430.js
144 ms
sprite.png
1888 ms
ajs.php
133 ms
127 ms
ads
244 ms
container.html
4 ms
activeview
14 ms
ajs.php
1397 ms
ads
284 ms
10100795831441807617
12 ms
activeview
14 ms
expansion_embed.js
14 ms
18330722359960970887
22 ms
abg.js
24 ms
m_js_controller.js
31 ms
googlelogo_color_112x36dp.png
22 ms
s
25 ms
x_button_blue2.png
21 ms
activeview
13 ms
activeview
13 ms
circle_bullet_grey.png
141 ms
xgemius.js
258 ms
37278
189 ms
activeview
20 ms
xd_arbiter.php
138 ms
ads.php
142 ms
fpdata.js
129 ms
adh-7c70360b.js
116 ms
lsget.html
255 ms
24953.jpg
517 ms
rexdot.js
138 ms
mediapool.bg 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-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
mediapool.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mediapool.bg 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
Tap targets are not sized appropriately
BG
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mediapool.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 Mediapool.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.
mediapool.bg
Open Graph description is not detected on the main page of Mediapool. 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: