4.7 sec in total
513 ms
3.9 sec
327 ms
Visit shum.bg now to see the best up-to-date Shum content for Bulgaria and also check out these interesting facts you probably never knew about shum.bg
ШУМ.BG - новинарски сайт на Шумен. Новини от Шумен, страната и света.
Visit shum.bgWe analyzed Shum.bg page load time and found that the first response time was 513 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
shum.bg performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value13.1 s
0/100
25%
Value6.7 s
36/100
10%
Value0 ms
100/100
30%
Value0.524
15/100
15%
Value6.2 s
62/100
10%
513 ms
393 ms
822 ms
517 ms
613 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Shum.bg, 71% (47 requests) were made to Cdn.shum.bg and 8% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn.shum.bg.
Page size can be reduced by 119.8 kB (9%)
1.3 MB
1.2 MB
In fact, the total size of Shum.bg main page is 1.3 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 875.9 kB which makes up the majority of the site volume.
Potential reduce by 101.8 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 16.4 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 101.8 kB or 75% of the original size.
Potential reduce by 11.6 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. Shum images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.0 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. Shum.bg needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 41% of the original size.
Number of requests can be reduced by 12 (20%)
59
47
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
shum.bg
513 ms
shum.bg
393 ms
www.shum.bg
822 ms
style.0e09f8fcec92.css
517 ms
all.4874c2da1cf1.js
613 ms
adsbygoogle.js
115 ms
display.js
697 ms
adsbygoogle.js
205 ms
js
62 ms
css
32 ms
search-phone.d9652d014111.svg
96 ms
logo.6da331de49b7.png
97 ms
home.c6cec1cd4be0.svg
190 ms
02923a93-ff34-4466-ae12-a27327b21dab.gif
487 ms
menu.6330ee99854e.svg
290 ms
logo-phone.699b6edfc170.svg
291 ms
weather.698909051da7.svg
295 ms
temperature.258f7a461c95.svg
292 ms
wind.fe29bf324acf.svg
292 ms
pressure.a15383cedc0f.svg
410 ms
humidity.cd450cf366d0.svg
412 ms
rain.c3de9b876041.svg
411 ms
f861532c-fc5b-45c7-83d6-908cfa827211.gif
965 ms
11f29fae-7eb1-43aa-801d-8a90d8cfead8.jpg
488 ms
aeb8413e-5cc1-44eb-a924-888ce7f79cc6.jpg
581 ms
5fd17a55-83ec-4851-a155-a1c884aa73e1.jpg
581 ms
513fdea2-2e60-4be9-9112-0ce7867603ed.webp
1244 ms
5c5b3c97-ea1d-4b19-b8e7-92758bae9b2b.jpg
582 ms
1787cf4a-8737-4445-8dc8-80425e709dad.jpg
869 ms
316e4d76-978a-4dc9-b0f5-dcaa8b6bef3e.webp
1054 ms
e2823b8d-fd1c-4a29-bdfe-bf871cf44537.jpg
676 ms
327618dd-6994-492b-9b95-a3a74eeb8b28.jpg
677 ms
2b1cc9ae-4999-49c3-89a8-457d31dbd39f.jpg
770 ms
cc3babd1-228a-499d-a88a-55e250233bfa.jpg
770 ms
32664549-f299-4f2b-8ec4-82a48d891217.jpg
865 ms
c20a5275-77bf-4144-840b-13a4d4808b1c.jpg
865 ms
69976333-9ce6-4ac4-afed-34dde4d3ed64.jpg
960 ms
9ab99ad4-e725-4a20-8fba-bafd58875eec.jpg
961 ms
283e2fdd-d900-48f8-adcc-0df467e85eda.jpg
964 ms
de005e48-8328-46b2-91b2-ee97d3778f27.jpg
1054 ms
5a9171b1-5382-4ef3-8fa7-c47f61cf5cc0.jpg
1055 ms
1d086ec8-391d-4883-9c8f-19f2ad33d0f5.jpg
1057 ms
9ec29c3c-7ce1-49ec-8c12-d6fea39f8e32.jpg
1059 ms
ab15b4c8-bd7b-4035-807b-57d54beb94ce.jpg
1148 ms
2130fdd2-e954-474d-85c6-59c42ed3b5c7.jpg
1150 ms
d2ae79bd-3ae9-4f3d-a341-64b1ed045387.jpg
1133 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
55 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
61 ms
show_ads_impl.js
286 ms
display.php
118 ms
f94e302b-f058-42c2-aebd-9501415c3ccd.jpg
1060 ms
36e85015-5f7e-4e4e-a926-ebcf7143b5e1.jpg
1061 ms
1507e3ae-5c41-4213-b91b-7374461ae80d.webp
1342 ms
00a1bc0b-f4fc-408a-9681-f7d50057bb69.jpg
959 ms
2fff0d23-f25a-4116-8bfd-3a96232e47a2.jpg
957 ms
views.02976d935fde.svg
958 ms
comments.6879ffbdcc80.svg
958 ms
close-white.ab3c1eae93c9.svg
994 ms
zrt_lookup.html
30 ms
ads
348 ms
ads
364 ms
ads
117 ms
ads
312 ms
ca-pub-9846586486030987
66 ms
36e85015-5f7e-4e4e-a926-ebcf7143b5e1.jpg
184 ms
shum.bg 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
shum.bg 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
Browser errors were logged to the console
Page has valid source maps
shum.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
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shum.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Shum.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.
shum.bg
Open Graph data is detected on the main page of Shum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: