Tools & Wizards About Us
whardy.com screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

whardy.com

Walter Hardy -- Software Developer, Engineer

Page Load Speed

1.2 sec in total

First Response

235 ms

Resources Loaded

845 ms

Page Rendered

92 ms

whardy.com screenshot

About Website

Welcome to whardy.com homepage info - get ready to check W Hardy best content right away, or after learning these important things about whardy.com

Software Developer

Visit whardy.com

Key Findings

We analyzed Whardy.com page load time and found that the first response time was 235 ms and then it took 937 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

whardy.com performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

whardy.com

235 ms

www.walterhardy.com

174 ms

html5reset-1.6.1.css

75 ms

jquery.min.js

8 ms

jquery-ui.min.js

13 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Whardy.com, 56% (9 requests) were made to Walterhardy.com and 19% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (288 ms) relates to the external source Walterhardy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.8 kB (53%)

Content Size

486.7 kB

After Optimization

229.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whardy.com main page is 486.7 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. 20% of websites need less resources to load. Javascripts take 287.6 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 5.1 kB

  • Original 7.6 kB
  • After minification 6.2 kB
  • After compression 2.5 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 1.4 kB, which is 18% 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.1 kB or 67% of the original size.

Image Optimization

-35%

Potential reduce by 65.5 kB

  • Original 189.0 kB
  • After minification 123.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. Obviously, W Hardy needs image optimization as it can save up to 65.5 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 185.4 kB

  • Original 287.6 kB
  • After minification 287.6 kB
  • After compression 102.2 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 185.4 kB or 64% of the original size.

CSS Optimization

-33%

Potential reduce by 851 B

  • Original 2.6 kB
  • After minification 2.6 kB
  • After compression 1.7 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. Whardy.com needs all CSS files to be minified and compressed as it can save up to 851 B or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (40%)

Requests Now

10

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whardy.com

whardy.com

235 ms

www.walterhardy.com

www.walterhardy.com

174 ms

html5reset-1.6.1.css

html5reset-1.6.1.css

75 ms

jquery.min.js

jquery.min.js

8 ms

jquery-ui.min.js

jquery-ui.min.js

13 ms

style.css

style.css

148 ms

wh_logo1.gif

wh_logo1.gif

147 ms

walter_priceisright.jpg

walter_priceisright.jpg

147 ms

cory_headshot2.jpg

cory_headshot2.jpg

148 ms

walter_priceisright.jpg

walter_priceisright.jpg

216 ms

wh_logo1.gif

wh_logo1.gif

73 ms

css2

css2

30 ms

css2

css2

47 ms

css2

css2

25 ms

cory_headshot2.jpg

cory_headshot2.jpg

288 ms

font

font

87 ms

Accessibility Review

whardy.com accessibility score

72

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

Image elements do not have [alt] attributes

Best Practices

whardy.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

whardy.com SEO score

58

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

Image elements do not have [alt] attributes

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

whardy.com

Open Graph description is not detected on the main page of W Hardy. 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: