22.9 sec in total
473 ms
21.3 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 473 ms and then it took 22.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
stolica.bg performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value8.1 s
2/100
25%
Value20.4 s
0/100
10%
Value6,650 ms
0/100
30%
Value0.021
100/100
15%
Value27.6 s
0/100
10%
473 ms
728 ms
148 ms
104 ms
126 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 50% of them (43 requests) were addressed to the original Stolica.bg, 10% (9 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Maps.luftdaten.info.
Page size can be reduced by 316.0 kB (16%)
1.9 MB
1.6 MB
In fact, the total size of Stolica.bg main page is 1.9 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.3 MB which makes up the majority of the site volume.
Potential reduce by 255.2 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 255.2 kB or 86% of the original size.
Potential reduce by 52.9 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 1.5 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 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 40 (55%)
73
33
The browser has sent 73 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 18 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
stolica.bg
473 ms
stolica.bg
728 ms
gtm.js
148 ms
brands.css
104 ms
fontawesome.css
126 ms
cookieconsent.min.css
84 ms
bootstrap.min.css
92 ms
font-awesome.min.css
335 ms
justifiedGallery.min.css
354 ms
framework_new.css
352 ms
main_new.css
466 ms
header_new.css
349 ms
footer.css
353 ms
grids.css
446 ms
respondivenes.css
462 ms
css
85 ms
css
110 ms
icon
116 ms
jquery.min.js
73 ms
e0b664edd1cfd747e3920a07d95a2846_1.js
182 ms
gpt.js
97 ms
js
162 ms
aaa-new-design.css
486 ms
aaa-new-design.js
489 ms
sdk.js
24 ms
jquery.justifiedGallery.min.js
292 ms
jquery.lazyload.js
353 ms
stolica_new.js
422 ms
cookieconsent.min.js
10 ms
lazysizes.min.js
36 ms
js-cloudimage-responsive.min.js
38 ms
dark-bg-1.jpg
654 ms
logo-small.png
135 ms
wgb-horizontal-3.png
135 ms
logo.png
134 ms
ic_round-menu.png
250 ms
ic_round-menu-close.png
424 ms
Polygon-1.png
425 ms
map-5.png
654 ms
thumb_ekranna_snimka_2024_09_09_083807.jpg
653 ms
thumb_CF74E917EF3340F2E0F00580CC8B64CA.jfif
983 ms
thumb_456866383_950426760219776_3198530390373787547_n.jpg
985 ms
thumb_409215296_695338119451335_4716838780801440459_n.jpg
655 ms
thumb_dreger.jpg
1175 ms
thumb_DSC05318_1.jpg
1176 ms
thumb_viber_image_2024_09_09_10_23_34_209.jpg
1177 ms
thumb_458972213_122156825114257230_9053162395251722164_n.jpg
1177 ms
thumb_metro_1983.jpg
1240 ms
thumb_resize_politsiyakpp.jpg
1176 ms
type-video.svg
1283 ms
pixel.png
1285 ms
type-photo.svg
1354 ms
logo-footer.png
1356 ms
pubads_impl.js
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQ.woff
294 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4taVQ.woff
523 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVQ.woff
524 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNa.woff
854 ms
u-440qyriQwlOrhSvowK_l5-cSZK.woff
854 ms
u-4n0qyriQwlOrhSvowK_l521wRZVcf8.woff
852 ms
u-4n0qyriQwlOrhSvowK_l52_wFZVcf8.woff
854 ms
transparent-back.png
1221 ms
maps.luftdaten.info
19511 ms
share_button.php
477 ms
envelope_bg.png
1115 ms
poll_bg.jpg
1155 ms
ads
747 ms
ads
840 ms
container.html
765 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV0exg.woff
560 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV0exg.woff
561 ms
ads
1063 ms
like.php
595 ms
k4GAxvzcPO_.js
643 ms
joke-bg.png
803 ms
GzgedhmzSQa.png
616 ms
ads
1065 ms
share_button.php
728 ms
luck-bg.png
756 ms
footer_background.jpg
757 ms
ads
966 ms
sdk.js
287 ms
k4GAxvzcPO_.js
249 ms
FEppCFCt76d.png
71 ms
47 ms
k4GAxvzcPO_.js
23 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
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
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: