Report Summary

  • 21

    Performance

    Renders faster than
    40% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

otter.ro

Otter Romania | Magazin Online de Incaltaminte | | otter.ro

Page Load Speed

4.6 sec in total

First Response

680 ms

Resources Loaded

3.6 sec

Page Rendered

356 ms

otter.ro screenshot

About Website

Welcome to otter.ro homepage info - get ready to check Otter best content for Romania right away, or after learning these important things about otter.ro

Peste 4500 modele de incaltaminte si genti. ✓Livrare rapida si retur gratuit la orice comanda. Descopera acum noua colectie!

Visit otter.ro

Key Findings

We analyzed Otter.ro page load time and found that the first response time was 680 ms and then it took 3.9 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

otter.ro performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

www.otter.ro

680 ms

73924a.js

346 ms

styles2.css

274 ms

button.css

188 ms

button.css

186 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 57% of them (75 requests) were addressed to the original Otter.ro, 11% (14 requests) were made to Static.xx.fbcdn.net and 3% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Otter.ro.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (43%)

Content Size

3.8 MB

After Optimization

2.2 MB

In fact, the total size of Otter.ro main page is 3.8 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 84.8 kB

  • Original 104.9 kB
  • After minification 100.3 kB
  • After compression 20.1 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 84.8 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 82.0 kB

  • Original 1.8 MB
  • After minification 1.7 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. Otter images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.2 MB

  • Original 1.6 MB
  • After minification 1.2 MB
  • After compression 397.2 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 1.2 MB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 289.9 kB

  • Original 336.6 kB
  • After minification 256.2 kB
  • After compression 46.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. Otter.ro needs all CSS files to be minified and compressed as it can save up to 289.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 79 (63%)

Requests Now

125

After Optimization

46

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

Accessibility Review

otter.ro accessibility score

87

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 input fields do not have accessible names

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements 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

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

otter.ro best practices score

83

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

Page has valid source maps

SEO Factors

otter.ro 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

    RO

  • Language Claimed

    RO

  • Encoding

    UTF-8

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