Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

navi.bg

GPS Навигации, Парктроници, и Double Din, GPS Навигация от Navi Bulgaria

Page Load Speed

7.5 sec in total

First Response

2.9 sec

Resources Loaded

4.5 sec

Page Rendered

204 ms

navi.bg screenshot

About Website

Click here to check amazing Navi content for Bulgaria. Otherwise, check out these important facts you probably never knew about navi.bg

Navi Bulgaria е официален вносител на GPS Навигации, Парктроници, и Double Din системи.

Visit navi.bg

Key Findings

We analyzed Navi.bg page load time and found that the first response time was 2.9 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

navi.bg performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

navi.bg

2879 ms

style.css

506 ms

mootools-1.2.2-core.js

792 ms

mootools-1.2.2.2-more.js

808 ms

SmartHoverBox.js

403 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 49% of them (33 requests) were addressed to the original Navi.bg, 22% (15 requests) were made to Scontent.xx.fbcdn.net and 15% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Navi.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 221.8 kB (45%)

Content Size

487.8 kB

After Optimization

266.0 kB

In fact, the total size of Navi.bg main page is 487.8 kB. 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. Javascripts take 216.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 42.5 kB

  • Original 49.8 kB
  • After minification 24.5 kB
  • After compression 7.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 25.3 kB, which is 51% 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 42.5 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 10.9 kB

  • Original 194.0 kB
  • After minification 183.0 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. Navi images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 145.0 kB

  • Original 216.1 kB
  • After minification 213.4 kB
  • After compression 71.1 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 145.0 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 23.4 kB

  • Original 27.9 kB
  • After minification 23.5 kB
  • After compression 4.6 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. Navi.bg needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (35%)

Requests Now

63

After Optimization

41

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Navi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

navi.bg accessibility score

45

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

navi.bg best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

navi.bg SEO score

58

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

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Navi.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Navi.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 Navi. 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: