Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

wallover.com

Quaker Houghton - Industrial Chemicals, Process Fluids & Lubricants

Page Load Speed

4.9 sec in total

First Response

68 ms

Resources Loaded

4.7 sec

Page Rendered

124 ms

wallover.com screenshot

About Website

Visit wallover.com now to see the best up-to-date Wallover content and also check out these interesting facts you probably never knew about wallover.com

If it’s made of metal, if it’s rolled, cut, drawn or cast, Quaker Houghton is there, optimizing processes, reducing costs, advancing safety & sustainability

Visit wallover.com

Key Findings

We analyzed Wallover.com page load time and found that the first response time was 68 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wallover.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

wallover.com

68 ms

home.quakerhoughton.com

357 ms

style.min.css

176 ms

style.min.css

173 ms

cms-navigation-base.css

174 ms

Our browser made a total of 183 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wallover.com, 97% (177 requests) were made to Home.quakerhoughton.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (509 ms) relates to the external source Home.quakerhoughton.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (47%)

Content Size

2.7 MB

After Optimization

1.4 MB

In fact, the total size of Wallover.com main page is 2.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 1.3 MB

  • Original 1.5 MB
  • After minification 1.4 MB
  • After compression 186.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 1.3 MB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. Wallover images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 52 B

  • Original 588 B
  • After minification 588 B
  • After compression 536 B

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.

Requests Breakdown

Number of requests can be reduced by 155 (90%)

Requests Now

173

After Optimization

18

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

Accessibility Review

wallover.com accessibility score

91

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

wallover.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wallover.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wallover.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wallover.com 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 Wallover. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: