Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

ocelot.de

Buchhandlung ocelot, Berlin bei genialokal - Buchhandlung

Page Load Speed

3.1 sec in total

First Response

274 ms

Resources Loaded

2.2 sec

Page Rendered

572 ms

About Website

Visit ocelot.de now to see the best up-to-date Ocelot content for Germany and also check out these interesting facts you probably never knew about ocelot.de

Willkommen in der Buchhandlung ocelot, in Berlin Wir sind regulär Montag bis Samstag von 10 bis 20 Uhr für Euch da. Wir freuen uns auf Euren Besuch....

Visit ocelot.de

Key Findings

We analyzed Ocelot.de page load time and found that the first response time was 274 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ocelot.de performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

ocelot.de

274 ms

166 ms

583 ms

chameleon_2.css

91 ms

genialokalRetailerTheme.css

149 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ocelot.de, 55% (32 requests) were made to Images.genialokal-cdn.de and 21% (12 requests) were made to Cover.genialokal-cdn.de. The less responsive or slowest element that took the longest time to load (841 ms) relates to the external source Sst.genialokal.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 306.5 kB (21%)

Content Size

1.5 MB

After Optimization

1.2 MB

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

HTML Optimization

-91%

Potential reduce by 303.3 kB

  • Original 335.0 kB
  • After minification 168.2 kB
  • After compression 31.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. This page needs HTML code to be minified as it can gain 166.8 kB, which is 50% 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 303.3 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 947.5 kB
  • After minification 947.5 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. Ocelot images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.8 kB

  • Original 153.8 kB
  • After minification 153.8 kB
  • After compression 152.0 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

-3%

Potential reduce by 1.5 kB

  • Original 53.1 kB
  • After minification 53.1 kB
  • After compression 51.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. Ocelot.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (33%)

Requests Now

54

After Optimization

36

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

Accessibility Review

ocelot.de accessibility score

67

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

ocelot.de 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

High

Browser errors were logged to the console

SEO Factors

ocelot.de SEO score

81

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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