Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

inbound.bg

Inbound.bg: Студио за Дигитален Маркетинг, SEO, SEM, Интернет Реклама

Page Load Speed

5.5 sec in total

First Response

558 ms

Resources Loaded

4.6 sec

Page Rendered

327 ms

inbound.bg screenshot

About Website

Visit inbound.bg now to see the best up-to-date Inbound content for Bulgaria and also check out these interesting facts you probably never knew about inbound.bg

Inbound.bg - Интернет реклама, която продава! Предплагаме SEO & SEM Услуги и Стратегии, PPC Реклама, Консултации, Маркетинг чрез Съдържание, Копирайтинг, Бранд Кампании, Медия Планиране...

Visit inbound.bg

Key Findings

We analyzed Inbound.bg page load time and found that the first response time was 558 ms and then it took 4.9 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

inbound.bg performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value2,790 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.213

58/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

inbound.bg

558 ms

wp-emoji-release.min.js

15 ms

flick.css

29 ms

inbound.bg

551 ms

layerslider.css

32 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 67% of them (108 requests) were addressed to the original Inbound.bg, 6% (9 requests) were made to Heyoliver.com and 5% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (858 ms) belongs to the original domain Inbound.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.9 kB (18%)

Content Size

1.3 MB

After Optimization

1.1 MB

In fact, the total size of Inbound.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. 75% 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 563.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 80.3 kB

  • Original 103.8 kB
  • After minification 103.6 kB
  • After compression 23.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 80.3 kB or 77% of the original size.

Image Optimization

-13%

Potential reduce by 71.9 kB

  • Original 563.8 kB
  • After minification 491.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. Obviously, Inbound needs image optimization as it can save up to 71.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 87.2 kB

  • Original 539.3 kB
  • After minification 539.3 kB
  • After compression 452.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 87.2 kB or 16% of the original size.

CSS Optimization

-2%

Potential reduce by 2.5 kB

  • Original 107.3 kB
  • After minification 107.3 kB
  • After compression 104.8 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. Inbound.bg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 76 (55%)

Requests Now

138

After Optimization

62

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

Accessibility Review

inbound.bg accessibility score

85

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

Links do not have a discernible name

Best Practices

inbound.bg best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

inbound.bg SEO score

69

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

High

robots.txt is not valid

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inbound.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 Inbound.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 data is detected on the main page of Inbound. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: