Tools & Wizards About Us
seethewhizard.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

seethewhizard.com

Whizard Strategy, marketing consultant for building materials companies.

Page Load Speed

1.7 sec in total

First Response

127 ms

Resources Loaded

890 ms

Page Rendered

667 ms

seethewhizard.com screenshot

About Website

Welcome to seethewhizard.com homepage info - get ready to check Seethe Whizard best content for Canada right away, or after learning these important things about seethewhizard.com

A More Effective Way to GrowYour Building Material Sales Let Your Customers Tell You How to Sell Them If You Want to Grow Your Sales, You Have Two Choices: Make incremental improvements based on what ...

Visit seethewhizard.com

Key Findings

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

Performance Metrics

seethewhizard.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

www.seethewhizard.com

127 ms

style.min.css

123 ms

styles.css

125 ms

style.css

132 ms

style.css

126 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Seethewhizard.com, 74% (40 requests) were made to Whizardly.wpenginepowered.com and 6% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (288 ms) relates to the external source Cdnjs.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.0 kB (14%)

Content Size

845.4 kB

After Optimization

730.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Seethewhizard.com main page is 845.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. 50% of websites need less resources to load. Images take 596.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 58.1 kB

  • Original 75.8 kB
  • After minification 67.4 kB
  • After compression 17.7 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 8.4 kB, 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 58.1 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 54.1 kB

  • Original 596.5 kB
  • After minification 542.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. Seethe Whizard images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 2.7 kB

  • Original 102.6 kB
  • After minification 102.6 kB
  • After compression 99.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 159 B

  • Original 70.5 kB
  • After minification 70.5 kB
  • After compression 70.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. Seethewhizard.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (76%)

Requests Now

50

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.seethewhizard.com

www.seethewhizard.com

127 ms

style.min.css

style.min.css

123 ms

styles.css

styles.css

125 ms

style.css

style.css

132 ms

style.css

style.css

126 ms

cookieblocker.min.css

cookieblocker.min.css

129 ms

ivory-search.min.css

ivory-search.min.css

129 ms

style.css

style.css

136 ms

normalize.css

normalize.css

134 ms

bootstrap.min.css

bootstrap.min.css

138 ms

jquery.flexnav.css

jquery.flexnav.css

137 ms

jquery.fancybox.css

jquery.fancybox.css

142 ms

fonts.css

fonts.css

145 ms

app.css

app.css

148 ms

vertical.css

vertical.css

156 ms

index.js

index.js

163 ms

jquery.min.js

jquery.min.js

155 ms

infusion.js

infusion.js

152 ms

jquery.uniform.min.js

jquery.uniform.min.js

156 ms

custom.js

custom.js

157 ms

idle-timer.min.js

idle-timer.min.js

182 ms

22215072.js

22215072.js

154 ms

css

css

124 ms

foundation.min.js

foundation.min.js

275 ms

app.js

app.js

172 ms

what-input.min.js

what-input.min.js

285 ms

motion-ui.min.js

motion-ui.min.js

288 ms

bootstrap.min.js

bootstrap.min.js

181 ms

jquery.flexnav.min.js

jquery.flexnav.min.js

166 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

185 ms

script.js

script.js

171 ms

api.js

api.js

128 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

178 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

177 ms

wp-polyfill.min.js

wp-polyfill.min.js

183 ms

index.js

index.js

186 ms

ivory-search.min.js

ivory-search.min.js

192 ms

complianz.min.js

complianz.min.js

195 ms

18862f18c1fe95b129aac2ce76e5fe058da4effd.js

18862f18c1fe95b129aac2ce76e5fe058da4effd.js

142 ms

lazyload.min.js

lazyload.min.js

191 ms

ubo3trk.css

ubo3trk.css

157 ms

p.css

p.css

25 ms

Mark-architect_opt.jpg

Mark-architect_opt.jpg

87 ms

d

d

31 ms

d

d

31 ms

logo.png

logo.png

42 ms

mark_new_optimized-2.jpg

mark_new_optimized-2.jpg

73 ms

Tactics@2x.png

Tactics@2x.png

239 ms

close.png

close.png

37 ms

Whizard_Strategy_Logo.png

Whizard_Strategy_Logo.png

37 ms

mobile-menu-black.png

mobile-menu-black.png

39 ms

mark_headshot_opt.jpg

mark_headshot_opt.jpg

163 ms

building-materials-book.jpg

building-materials-book.jpg

147 ms

logo-footer.png

logo-footer.png

38 ms

Accessibility Review

seethewhizard.com accessibility score

56

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.

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

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

High

Links do not have a discernible name

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

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

seethewhizard.com SEO score

84

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

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

seethewhizard.com

Open Graph data is detected on the main page of Seethe Whizard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: