19.9 sec in total
393 ms
18.9 sec
583 ms
Visit sofiatraffic.bg now to see the best up-to-date Sofiatraffic content for Bulgaria and also check out these interesting facts you probably never knew about sofiatraffic.bg
Център за Градска Мобилност, София - информация за Градски Транспорт и паркиране в "Синя Зона".
Visit sofiatraffic.bgWe analyzed Sofiatraffic.bg page load time and found that the first response time was 393 ms and then it took 19.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
sofiatraffic.bg performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value21.1 s
0/100
25%
Value10.4 s
8/100
10%
Value1,320 ms
17/100
30%
Value0.304
39/100
15%
Value20.3 s
2/100
10%
393 ms
175 ms
149 ms
298 ms
654 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 60% of them (64 requests) were addressed to the original Sofiatraffic.bg, 17% (18 requests) were made to Static.xx.fbcdn.net and 11% (12 requests) were made to Razpisanieto.bg. The less responsive or slowest element that took the longest time to load (16.9 sec) belongs to the original domain Sofiatraffic.bg.
Page size can be reduced by 493.9 kB (14%)
3.5 MB
3.0 MB
In fact, the total size of Sofiatraffic.bg main page is 3.5 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. 45% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 23.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. This page needs HTML code to be minified as it can gain 4.4 kB, which is 14% 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 23.7 kB or 77% of the original size.
Potential reduce by 294.2 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. Sofiatraffic images are well optimized though.
Potential reduce by 31.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 31.0 kB or 40% of the original size.
Potential reduce by 145.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. Sofiatraffic.bg needs all CSS files to be minified and compressed as it can save up to 145.0 kB or 81% of the original size.
Number of requests can be reduced by 47 (46%)
102
55
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sofiatraffic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
sofiatraffic.bg
393 ms
175 ms
sumc_v2.css
149 ms
lightbox.css
298 ms
iframe.html
654 ms
likebox.php
333 ms
btn.facebook.png
458 ms
k.jpg
1202 ms
mob.jpg
2660 ms
snimai.jpg
2289 ms
banner-ebuspass.jpg
1353 ms
banner-vignettes.png
749 ms
ios.jpg
332 ms
banner-8-request_parking_vignette.jpg
894 ms
baner.jpg
331 ms
app.jpg
331 ms
banner-integrated_transport.bg.jpg
1483 ms
ic_vitual_tables.png
1346 ms
ic_tow_away.png
1438 ms
ic_schedules.png
1493 ms
ic_calc.png
2621 ms
ic_rt_changes.png
1584 ms
ic_virtual_records.png
1628 ms
ic_pd.png
1637 ms
ic_mobile_version.png
1729 ms
lightbox.js
1774 ms
banner-tel-bg.jpg
2072 ms
banerIstoria.jpg
2456 ms
letishte3.jpg
15165 ms
Banerwifi.jpg
2944 ms
banner-9-modum-bg.jpg
2720 ms
tolerance-portrait.png
3039 ms
banner-1-50st.png
2909 ms
banner-1-50st-flash.png
2799 ms
FbUd6dZS1Af.css
282 ms
dGJLq38YL-C.css
350 ms
f7m6HODnCDd.css
418 ms
i5_N_HL0uEJ.css
549 ms
_rx8naC75Dy.js
618 ms
x5F9OMjKyLw.js
635 ms
ICDbTSzjQEg.js
491 ms
TTCre3391I0.js
491 ms
njO1TPvGzoR.js
490 ms
b_6HNn_J2BZ.js
566 ms
7cm7D75Y0Sf.js
647 ms
rFmE1g6Dkoz.js
759 ms
ga.js
70 ms
bckg.png
2566 ms
header_bg.jpg
3664 ms
header_lang_en.png
2712 ms
header_mobile_bg.png
2754 ms
tm_bckg.png
2788 ms
tm_r_el.png
2841 ms
gp.jpg
16920 ms
mp1.jpg
3900 ms
baner.jpg
3060 ms
app.jpg
12944 ms
ios.jpg
3877 ms
__utm.gif
24 ms
tm_active.png
3753 ms
vendor.bef7df08.css
469 ms
iframe.8c923b3b.css
791 ms
vendor.50011056.js
3462 ms
scripts.8e76cbff.js
615 ms
tm_l_active.png
3515 ms
tm_vbline.png
3371 ms
12801096_986618471430980_4722045615722280438_n.jpg
328 ms
1390557_536113933148105_1455490650_n.jpg
387 ms
12376703_1140624889298283_1365487412821180931_n.jpg
459 ms
11245793_10202867874936292_4287189606843472220_n.jpg
526 ms
1917489_639105686229674_19129961029158183_n.jpg
566 ms
10354686_10150004552801856_220367501106153455_n.jpg
526 ms
12072723_1065033490182269_8381592305035599520_n.jpg
708 ms
wL6VQj7Ab77.png
106 ms
s7jcwEQH7Sx.png
105 ms
QDwYpIaRyfG.png
105 ms
a-ZN6WoEOje.png
106 ms
ic_phone.png
3181 ms
rp_bckg.png
3063 ms
rp_top_bckg.png
3059 ms
css
24 ms
rp_bottom_bckg.png
3080 ms
analytics.js
51 ms
lm_el_t.png
3489 ms
lm_bckg.png
3062 ms
collect
27 ms
lm_top.png
3083 ms
lm_bottom.png
3073 ms
rp_secBox_bckg.png
3175 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
135 ms
rp_secBox_top.png
3118 ms
rp_secBox_bottom.png
3195 ms
news_important.png
2919 ms
ft_mid.png
2774 ms
ft_left.png
2646 ms
ft_right.png
2521 ms
iframe.html
123 ms
getLinesList
532 ms
caret-down.png
423 ms
trolleybus_icon.svg
123 ms
tram_icon.svg
127 ms
bus_icon.svg
132 ms
metro_icon.svg
135 ms
overlay.png
148 ms
loading.gif
148 ms
close.gif
149 ms
sofiatraffic.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
[lang] attributes do not have a valid value
sofiatraffic.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
Missing source maps for large first-party JavaScript
sofiatraffic.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sofiatraffic.bg can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Sofiatraffic.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.
sofiatraffic.bg
Open Graph description is not detected on the main page of Sofiatraffic. 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: