Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

what-walls-want.com

Barbara's Big Blog of Auto Service Info, Tips and More

Page Load Speed

692 ms in total

First Response

180 ms

Resources Loaded

371 ms

Page Rendered

141 ms

About Website

Visit what-walls-want.com now to see the best up-to-date What Walls Want content and also check out these interesting facts you probably never knew about what-walls-want.com

Working on your car doesn't have to be a big, overwhelming challenge. Learn tips for doing auto service on your own.

Visit what-walls-want.com

Key Findings

We analyzed What-walls-want.com page load time and found that the first response time was 180 ms and then it took 512 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

what-walls-want.com performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

what-walls-want.com

180 ms

font-awesome.min.css

24 ms

styles.css

26 ms

css

58 ms

lunr.min.js

50 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 44% of them (4 requests) were addressed to the original What-walls-want.com, 22% (2 requests) were made to Maxcdn.bootstrapcdn.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (180 ms) belongs to the original domain What-walls-want.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.8 kB (43%)

Content Size

18.4 kB

After Optimization

10.6 kB

In fact, the total size of What-walls-want.com main page is 18.4 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. 15% of websites need less resources to load. HTML takes 7.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 5.7 kB

  • Original 7.9 kB
  • After minification 7.1 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 842 B, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.7 kB or 72% of the original size.

Image Optimization

-24%

Potential reduce by 1.8 kB

  • Original 7.6 kB
  • After minification 5.8 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. Obviously, What Walls Want needs image optimization as it can save up to 1.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 17 B

  • Original 412 B
  • After minification 412 B
  • After compression 395 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.

CSS Optimization

-9%

Potential reduce by 231 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 2.2 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. What-walls-want.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

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

Accessibility Review

what-walls-want.com accessibility score

81

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

what-walls-want.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

what-walls-want.com SEO score

82

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise What-walls-want.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that What-walls-want.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 description is not detected on the main page of What Walls Want. 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: