Report Summary

  • 3

    Performance

    Renders faster than
    19% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

markita.net

Онлайн строителен магазин Маркита - Строителни материали

Page Load Speed

4.8 sec in total

First Response

852 ms

Resources Loaded

3.6 sec

Page Rendered

410 ms

markita.net screenshot

About Website

Welcome to markita.net homepage info - get ready to check Markita best content for Bulgaria right away, or after learning these important things about markita.net

Строителен магазин Маркита ➽ Търговия на едро и дребно със строителни материали ✓ За ремонта на дома ✓ За градината ✓ За обзавеждането. Достъпни цени ✓.

Visit markita.net

Key Findings

We analyzed Markita.net page load time and found that the first response time was 852 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

markita.net performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value40.9 s

0/100

25%

SI (Speed Index)

Value22.4 s

0/100

10%

TBT (Total Blocking Time)

Value13,120 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.789

5/100

15%

TTI (Time to Interactive)

Value44.4 s

0/100

10%

Network Requests Diagram

markita.net

852 ms

css_2a78fe2c2769c02301fc013d9b16b812.css

299 ms

css_c051a91d6aef837e450aebd082304ffe.css

322 ms

js_bb3befd2149c54450f0e7623d1b6f030.jsmin.js

522 ms

all.js

186 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 64% of them (57 requests) were addressed to the original Markita.net, 11% (10 requests) were made to Static.xx.fbcdn.net and 6% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Markita.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 737.5 kB (37%)

Content Size

2.0 MB

After Optimization

1.3 MB

In fact, the total size of Markita.net main page is 2.0 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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 233.8 kB

  • Original 287.4 kB
  • After minification 279.2 kB
  • After compression 53.7 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 233.8 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 15.2 kB

  • Original 1.0 MB
  • After minification 1.0 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. Markita images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 234.3 kB

  • Original 367.1 kB
  • After minification 367.1 kB
  • After compression 132.8 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 234.3 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 254.2 kB

  • Original 308.9 kB
  • After minification 307.4 kB
  • After compression 54.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. Markita.net needs all CSS files to be minified and compressed as it can save up to 254.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (29%)

Requests Now

84

After Optimization

60

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

Accessibility Review

markita.net accessibility score

81

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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 IDs are not unique

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

Low

No form fields have multiple labels

High

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

High

Links do not have a discernible name

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

markita.net best practices score

58

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

Displays images with incorrect aspect ratio

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

markita.net 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

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 Markita.net 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 Markita.net 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 Markita. 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: