Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

sofiatraffic.bg

Център за градска мобилност

Page Load Speed

19.9 sec in total

First Response

393 ms

Resources Loaded

18.9 sec

Page Rendered

583 ms

sofiatraffic.bg screenshot

About Website

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.bg

Key Findings

We 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.

Performance Metrics

sofiatraffic.bg performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.304

39/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

sofiatraffic.bg

393 ms

175 ms

sumc_v2.css

149 ms

lightbox.css

298 ms

iframe.html

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 Optimization Overview & Recommendations

Page size can be reduced by 493.9 kB (14%)

Content Size

3.5 MB

After Optimization

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.

HTML Optimization

-77%

Potential reduce by 23.7 kB

  • Original 30.7 kB
  • After minification 26.3 kB
  • After compression 7.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 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.

Image Optimization

-9%

Potential reduce by 294.2 kB

  • Original 3.2 MB
  • After minification 2.9 MB

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.

JavaScript Optimization

-40%

Potential reduce by 31.1 kB

  • Original 77.4 kB
  • After minification 77.4 kB
  • After compression 46.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 31.1 kB or 40% of the original size.

CSS Optimization

-81%

Potential reduce by 145.0 kB

  • Original 178.7 kB
  • After minification 177.1 kB
  • After compression 33.7 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.

Requests Breakdown

Number of requests can be reduced by 47 (46%)

Requests Now

102

After Optimization

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.

Accessibility Review

sofiatraffic.bg accessibility score

66

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[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

High

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

High

[lang] attributes do not have a valid value

Best Practices

sofiatraffic.bg best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

sofiatraffic.bg SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: