Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

infobel.bg

Infobel България - Телефонен указател

Page Load Speed

3.5 sec in total

First Response

550 ms

Resources Loaded

2.7 sec

Page Rendered

260 ms

infobel.bg screenshot

About Website

Welcome to infobel.bg homepage info - get ready to check Infobel best content for Bulgaria right away, or after learning these important things about infobel.bg

Търсене в България с онлайн телефонния указател, търсене в бизнес указателя и в указателя на частните абонати!

Visit infobel.bg

Key Findings

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

Performance Metrics

infobel.bg performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value1.073

2/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

bulgaria

550 ms

css

50 ms

kendo.common.min.css

66 ms

kendo.default.min.css

53 ms

bootstrap.min.css

27 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Infobel.bg, 15% (13 requests) were made to Infobel.com and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (550 ms) relates to the external source Infobel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 831.7 kB (62%)

Content Size

1.3 MB

After Optimization

514.4 kB

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

HTML Optimization

-89%

Potential reduce by 194.1 kB

  • Original 218.2 kB
  • After minification 130.8 kB
  • After compression 24.1 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 87.4 kB, which is 40% 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 194.1 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 4.2 kB

  • Original 196.0 kB
  • After minification 191.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. Infobel images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 296.9 kB

  • Original 534.0 kB
  • After minification 531.2 kB
  • After compression 237.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 296.9 kB or 56% of the original size.

CSS Optimization

-85%

Potential reduce by 336.4 kB

  • Original 397.9 kB
  • After minification 397.2 kB
  • After compression 61.5 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. Infobel.bg needs all CSS files to be minified and compressed as it can save up to 336.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (65%)

Requests Now

74

After Optimization

26

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

Accessibility Review

infobel.bg accessibility score

76

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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.

Best Practices

infobel.bg best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

infobel.bg SEO score

91

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

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

High

Tap targets are not sized appropriately

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 Infobel.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 Infobel.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 Infobel. 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: