Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

amo.bg

АМО ЕООД Дизайнерско и модулно обзавеждане за офиса, хотела и дома - кухни, спални, стенни системи, гардероби

Page Load Speed

10.8 sec in total

First Response

934 ms

Resources Loaded

9.3 sec

Page Rendered

566 ms

amo.bg screenshot

About Website

Click here to check amazing Amo content. Otherwise, check out these important facts you probably never knew about amo.bg

furniture furnishings and equipment: medium and large offices, administrative buildings and state institutions, ministries, agencies, states and municipalities - AMO

Visit amo.bg

Key Findings

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

Performance Metrics

amo.bg performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

www.amo.bg

934 ms

style.css

125 ms

ajax.css

246 ms

scripts.js

246 ms

ajax.js

261 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 98% of them (78 requests) were addressed to the original Amo.bg, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Amo.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.4 kB (20%)

Content Size

510.3 kB

After Optimization

409.8 kB

In fact, the total size of Amo.bg main page is 510.3 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. 35% of websites need less resources to load. Images take 395.3 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 73.7 kB

  • Original 84.2 kB
  • After minification 81.1 kB
  • After compression 10.4 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 73.7 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 16.7 kB

  • Original 395.3 kB
  • After minification 378.7 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. Amo images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 7.5 kB

  • Original 26.9 kB
  • After minification 25.4 kB
  • After compression 19.4 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 7.5 kB or 28% of the original size.

CSS Optimization

-65%

Potential reduce by 2.5 kB

  • Original 3.8 kB
  • After minification 3.2 kB
  • After compression 1.3 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. Amo.bg needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (14%)

Requests Now

79

After Optimization

68

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

Accessibility Review

amo.bg accessibility score

61

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

Links do not have a discernible name

Best Practices

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

High

Browser errors were logged to the console

SEO Factors

amo.bg SEO score

62

Search Engine Optimization Advices

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

    BG

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amo.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 Amo.bg main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Amo. 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: