Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

freioel.de

frei öl® - ölbasierte Hautpflegeprodukte in Apotheker-Qualität | frei öl

Page Load Speed

3.8 sec in total

First Response

388 ms

Resources Loaded

2.8 sec

Page Rendered

648 ms

freioel.de screenshot

About Website

Click here to check amazing Frei Oel content for Germany. Otherwise, check out these important facts you probably never knew about freioel.de

Die Marke frei öl® entstand aus Liebe - und diese Liebe ist nach wie vor in jedem unserer Produkte spürbar. Innovative, ölbasierte Wirkpflege-Produkt…

Visit freioel.de

Key Findings

We analyzed Freioel.de page load time and found that the first response time was 388 ms and then it took 3.5 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

freioel.de performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value2,540 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

freioel.de

388 ms

www.freioel.de

602 ms

1664192401_c6f5eb3bda22f500e576ad168b622faa.css

289 ms

1664192401_c6f5eb3bda22f500e576ad168b622faa.js

709 ms

hautbeduerfnisse-unterschiedlich-freioel_800x800.jpg.pagespeed.ce.Nf2k9iDOyo.jpg

686 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 57.1 kB (8%)

Content Size

688.6 kB

After Optimization

631.5 kB

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

HTML Optimization

-83%

Potential reduce by 56.9 kB

  • Original 69.0 kB
  • After minification 68.9 kB
  • After compression 12.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 56.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 187 B

  • Original 512.8 kB
  • After minification 512.6 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. Frei Oel images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frei Oel. According to our analytics all requests are already optimized.

Accessibility Review

freioel.de accessibility score

88

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

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

High

[role]s are not contained by their required parent element

Best Practices

freioel.de best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

freioel.de SEO score

92

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

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 Freioel.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 Freioel.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 Frei Oel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: