10.6 sec in total
445 ms
9.1 sec
1.1 sec
Click here to check amazing Stolica content for Bulgaria. Otherwise, check out these important facts you probably never knew about stolica.bg
Последните новини от Столична община.Всички регионални новини от София на едно място. Събития, ремонти, задръствания, инциденти от столицата и София райони.
Visit stolica.bgWe analyzed Stolica.bg page load time and found that the first response time was 445 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
stolica.bg performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value8.8 s
1/100
25%
Value16.1 s
0/100
10%
Value4,540 ms
0/100
30%
Value0.016
100/100
15%
Value17.6 s
4/100
10%
445 ms
4254 ms
60 ms
170 ms
224 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 43% of them (43 requests) were addressed to the original Stolica.bg, 9% (9 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Stolica.bg.
Page size can be reduced by 369.6 kB (18%)
2.0 MB
1.7 MB
In fact, the total size of Stolica.bg 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 249.3 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 56.6 kB, which is 19% 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 249.3 kB or 86% of the original size.
Potential reduce by 52.8 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. Stolica images are well optimized though.
Potential reduce by 61.0 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 61.0 kB or 12% of the original size.
Potential reduce by 6.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. Stolica.bg needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 12% of the original size.
Number of requests can be reduced by 50 (57%)
88
38
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stolica. 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 17 to 1 for CSS and as a result speed up the page load time.
stolica.bg
445 ms
stolica.bg
4254 ms
gtm.js
60 ms
brands.css
170 ms
fontawesome.css
224 ms
cookieconsent.min.css
56 ms
bootstrap.min.css
48 ms
font-awesome.min.css
320 ms
justifiedGallery.min.css
331 ms
framework_new.css
332 ms
main_new.css
442 ms
header_new.css
345 ms
footer.css
347 ms
grids.css
427 ms
respondivenes.css
440 ms
css
54 ms
css
82 ms
icon
84 ms
jquery.min.js
51 ms
e0b664edd1cfd747e3920a07d95a2846_1.js
159 ms
gpt.js
96 ms
js
82 ms
aaa-new-design.css
437 ms
aaa-new-design.js
502 ms
analytics.js
28 ms
45 ms
collect
14 ms
collect
33 ms
37 ms
ga-audiences
21 ms
sdk.js
15 ms
jquery.justifiedGallery.min.js
309 ms
jquery.lazyload.js
355 ms
stolica_new.js
355 ms
cookieconsent.min.js
11 ms
lazysizes.min.js
125 ms
js-cloudimage-responsive.min.js
131 ms
js
60 ms
pubads_impl.js
78 ms
dark-bg-1.jpg
570 ms
logo-small.png
185 ms
wgb-horizontal-3.png
184 ms
logo.png
355 ms
ic_round-menu.png
186 ms
ic_round-menu-close.png
186 ms
Polygon-1.png
355 ms
map-5.png
454 ms
thumb_moskovska33.jpeg.jfif
568 ms
thumb_1705594592_DSC04419_1.jpg
574 ms
thumb_1705590312_398820297_677538224564658_695313565182692122_n.jpg
621 ms
thumb_1705589548_DSC06528_2.jpg
621 ms
thumb_289615535_5225582680888381_5850569715057968637_n_(1).jpg
672 ms
thumb_1705602594_DSC06528_2.jpg
777 ms
thumb_aleksandar_valeriev_v_klub_na_porotsite2.jpg
672 ms
thumb_1705597026_resize_resize_remonti__sredets.jpg
775 ms
thumb_collage(1).jpg
815 ms
thumb_419237147_366955246081947_7947655555322860372_n.jpg
906 ms
pixel.png
779 ms
type-photo.svg
813 ms
type-video.svg
883 ms
logo-footer.png
894 ms
js
146 ms
collect
73 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVc.ttf
138 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4taVc.ttf
303 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVc.ttf
305 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf
428 ms
u-440qyriQwlOrhSvowK_l5-cSZJ.ttf
406 ms
u-4n0qyriQwlOrhSvowK_l521wRZVcf_.ttf
404 ms
u-4n0qyriQwlOrhSvowK_l52_wFZVcf_.ttf
404 ms
collect
235 ms
transparent-back.png
776 ms
ads
579 ms
container.html
439 ms
maps.luftdaten.info
1483 ms
share_button.php
302 ms
envelope_bg.png
623 ms
poll_bg.jpg
627 ms
ads
797 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV0exQ.ttf
144 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV0exQ.ttf
143 ms
ads
954 ms
ga-audiences
213 ms
like.php
300 ms
joke-bg.png
567 ms
ads
954 ms
share_button.php
169 ms
luck-bg.png
535 ms
footer_background.jpg
538 ms
9HAvP07Y3jY.js
123 ms
GzgedhmzSQa.png
120 ms
ads
915 ms
sdk.js
48 ms
61 ms
9HAvP07Y3jY.js
12 ms
FEppCFCt76d.png
11 ms
9HAvP07Y3jY.js
7 ms
maps.sensor.community
1319 ms
main.js
461 ms
index.css
318 ms
matomo.js
664 ms
stolica.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
stolica.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
stolica.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
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stolica.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 Stolica.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.
stolica.bg
Open Graph data is detected on the main page of Stolica. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: