Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

prego.ua

ᐉ Інтернет магазин взуття PREGO ≡ купити взуття в Києві та Україні - Prego.ua

Page Load Speed

5.1 sec in total

First Response

48 ms

Resources Loaded

4.3 sec

Page Rendered

805 ms

prego.ua screenshot

About Website

Click here to check amazing PREGO content for Ukraine. Otherwise, check out these important facts you probably never knew about prego.ua

Інтернет магазин взуття та сумок в Києві ✿ Взуття Prego ✿ Широкий асортимент брендового взуття та сумок за доступними цінами ➦ Доставка по Україні ☎ 38 (063) 721-40-69

Visit prego.ua

Key Findings

We analyzed Prego.ua page load time and found that the first response time was 48 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

prego.ua performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value2,480 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.938

3/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

prego.ua

48 ms

prego.ua

977 ms

style.min.css

48 ms

blog.css

44 ms

main.css

25 ms

Our browser made a total of 189 requests to load all elements on the main page. We found that 9% of them (17 requests) were addressed to the original Prego.ua, 72% (136 requests) were made to Static.prego.ua and 7% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Static.prego.ua.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (40%)

Content Size

2.9 MB

After Optimization

1.7 MB

In fact, the total size of Prego.ua main page is 2.9 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 260.4 kB

  • Original 293.6 kB
  • After minification 244.2 kB
  • After compression 33.2 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 49.4 kB, which is 17% 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 260.4 kB or 89% of the original size.

Image Optimization

-43%

Potential reduce by 860.7 kB

  • Original 2.0 MB
  • After minification 1.1 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. Obviously, PREGO needs image optimization as it can save up to 860.7 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 31.5 kB

  • Original 528.1 kB
  • After minification 528.1 kB
  • After compression 496.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 5.7 kB

  • Original 64.3 kB
  • After minification 64.3 kB
  • After compression 58.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. Prego.ua has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (23%)

Requests Now

160

After Optimization

124

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

Accessibility Review

prego.ua accessibility score

64

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-hidden="true"] elements contain focusable descendents

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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.

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

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

prego.ua 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

prego.ua SEO score

83

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

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

    UK

  • Language Claimed

    UK

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prego.ua can be misinterpreted by Google and other search engines. Our service has detected that Ukrainian is used on the page, and it matches the claimed language. Our system also found out that Prego.ua 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 PREGO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: