Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

surflos.de

Surflos.de

Page Load Speed

4.3 sec in total

First Response

686 ms

Resources Loaded

3.4 sec

Page Rendered

282 ms

surflos.de screenshot

About Website

Click here to check amazing Surflos content. Otherwise, check out these important facts you probably never knew about surflos.de

Visit surflos.de

Key Findings

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

surflos.de performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.126

83/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

surflos.de

686 ms

wp-emoji-release.min.js

285 ms

settings.css

293 ms

colorbox.min.css

204 ms

jquery.selectbox.css

206 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 66% of them (79 requests) were addressed to the original Surflos.de, 22% (26 requests) were made to Maps.google.com and 7% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Surflos.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (68%)

Content Size

3.0 MB

After Optimization

954.1 kB

In fact, the total size of Surflos.de main page is 3.0 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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 102.1 kB

  • Original 121.3 kB
  • After minification 118.2 kB
  • After compression 19.2 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 102.1 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 28.9 kB

  • Original 475.1 kB
  • After minification 446.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. Surflos images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 927.5 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 367.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 927.5 kB or 72% of the original size.

CSS Optimization

-89%

Potential reduce by 961.6 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 121.3 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. Surflos.de needs all CSS files to be minified and compressed as it can save up to 961.6 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (58%)

Requests Now

113

After Optimization

47

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

Accessibility Review

surflos.de accessibility score

100

Accessibility Issues

Best Practices

surflos.de best practices score

75

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

Browser errors were logged to the console

SEO Factors

surflos.de SEO score

85

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

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 Surflos.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 Surflos.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 Surflos. 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: