Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

rofu.de

ROFU Spielzeug Shop | Günstiges Spielzeug online kaufen

Page Load Speed

2 sec in total

First Response

226 ms

Resources Loaded

1.5 sec

Page Rendered

209 ms

About Website

Welcome to rofu.de homepage info - get ready to check ROFU best content for Germany right away, or after learning these important things about rofu.de

Spielzeug Online-Shop - Riesige Spielwaren Auswahl zum Top-Preis bestellen! Beliebte Marken wie LEGO, Playmobil, Ravensburger, Bruder und Besttoy

Visit rofu.de

Key Findings

We analyzed Rofu.de page load time and found that the first response time was 226 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

rofu.de performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

rofu.de

226 ms

rofu.de

357 ms

www.rofu.de

514 ms

e95dd9f0bac27c0e.css

31 ms

polyfills-c67a75d1b6f99dc8.js

436 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that all of those requests were addressed to Rofu.de and no external sources were called. The less responsive or slowest element that took the longest time to load (514 ms) belongs to the original domain Rofu.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 162.5 kB (78%)

Content Size

207.7 kB

After Optimization

45.2 kB

In fact, the total size of Rofu.de main page is 207.7 kB. 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. HTML takes 198.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 162.5 kB

  • Original 198.5 kB
  • After minification 198.5 kB
  • After compression 36.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 162.5 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 9.2 kB
  • After minification 9.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. ROFU images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 20 (87%)

Requests Now

23

After Optimization

3

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

Accessibility Review

rofu.de accessibility score

82

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

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.

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rofu.de SEO score

100

Search Engine Optimization Advices

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

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 Rofu.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 Rofu.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 data is detected on the main page of ROFU. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: