Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

walleo.co

Loading...

Page Load Speed

2.9 sec in total

First Response

670 ms

Resources Loaded

2 sec

Page Rendered

178 ms

walleo.co screenshot

About Website

Welcome to walleo.co homepage info - get ready to check Walleo best content for Germany right away, or after learning these important things about walleo.co

Visit walleo.co

Key Findings

We analyzed Walleo.co page load time and found that the first response time was 670 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

walleo.co performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

www.walleo.co

670 ms

style.css

48 ms

black.css

61 ms

styles.css

58 ms

jquery.js

95 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 67% of them (34 requests) were addressed to the original Walleo.co, 10% (5 requests) were made to Pagead2.googlesyndication.com and 10% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (749 ms) relates to the external source S4.histats.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.1 kB (42%)

Content Size

400.5 kB

After Optimization

231.4 kB

In fact, the total size of Walleo.co main page is 400.5 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. 50% of websites need less resources to load. Javascripts take 246.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 20.4 kB

  • Original 26.5 kB
  • After minification 26.0 kB
  • After compression 6.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 20.4 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 8.3 kB

  • Original 103.8 kB
  • After minification 95.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. Walleo images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 122.1 kB

  • Original 246.0 kB
  • After minification 243.8 kB
  • After compression 123.9 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 122.1 kB or 50% of the original size.

CSS Optimization

-76%

Potential reduce by 18.3 kB

  • Original 24.2 kB
  • After minification 22.9 kB
  • After compression 5.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. Walleo.co needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (29%)

Requests Now

49

After Optimization

35

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

Accessibility Review

walleo.co accessibility score

86

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

walleo.co best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

walleo.co SEO score

92

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Walleo.co can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Walleo.co 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 Walleo. 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: