Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

oozoo.by

OZOO Интернет-ЗооМагазин Бреста - OOZOO

Page Load Speed

10.3 sec in total

First Response

797 ms

Resources Loaded

9.2 sec

Page Rendered

326 ms

oozoo.by screenshot

About Website

Visit oozoo.by now to see the best up-to-date OOZOO content for Belarus and also check out these interesting facts you probably never knew about oozoo.by

Удобный интернет-магазин товаров для кошек, собак, птиц и грызунов. Доставка по Бресту и району. Удобная оплата, выгодные цены.

Visit oozoo.by

Key Findings

We analyzed Oozoo.by page load time and found that the first response time was 797 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

oozoo.by performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.238

52/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

oozoo.by

797 ms

960.css

123 ms

stylesheet.css

257 ms

carousel.css

263 ms

jquery-ui.css

264 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 88% of them (70 requests) were addressed to the original Oozoo.by, 5% (4 requests) were made to Static.siteheart.com and 3% (2 requests) were made to Widget.siteheart.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Stats.digistr.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 580.6 kB (45%)

Content Size

1.3 MB

After Optimization

719.6 kB

In fact, the total size of Oozoo.by 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. 45% of websites need less resources to load. Images take 610.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 40.6 kB

  • Original 51.7 kB
  • After minification 51.1 kB
  • After compression 11.0 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 40.6 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 56.9 kB

  • Original 610.1 kB
  • After minification 553.2 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. OOZOO images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 343.4 kB

  • Original 473.9 kB
  • After minification 440.8 kB
  • After compression 130.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 343.4 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 139.7 kB

  • Original 164.7 kB
  • After minification 134.0 kB
  • After compression 25.0 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. Oozoo.by needs all CSS files to be minified and compressed as it can save up to 139.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

78

After Optimization

50

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

Accessibility Review

oozoo.by accessibility score

86

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

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

Best Practices

oozoo.by best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

oozoo.by 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

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oozoo.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Oozoo.by 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 OOZOO. 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: