Tools & Wizards About Us
wizzm.com screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

wizzm.com

WIZZM - Abbotsford & Langley Marketing and Web Development Team

Page Load Speed

565 ms in total

First Response

107 ms

Resources Loaded

326 ms

Page Rendered

132 ms

wizzm.com screenshot

About Website

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

Abbotsford & Langley Freelance Graphic Designer, Web Developer and Digital Marketing Consultant. Exceptional Design Services in the Fraser Valley at Amazing Prices.

Visit wizzm.com

Key Findings

We analyzed Wizzm.com page load time and found that the first response time was 107 ms and then it took 458 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

wizzm.com performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.296

40/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

wizzm.com

107 ms

jquery-latest.min.js

33 ms

css

48 ms

jquery.easing.1.3.js

26 ms

jquery.animate-enhanced.min.js

45 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 86% of them (36 requests) were addressed to the original Wizzm.com, 10% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (162 ms) belongs to the original domain Wizzm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.5 kB (1%)

Content Size

3.9 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wizzm.com main page is 3.9 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. 75% 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. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 11.8 kB

  • Original 15.0 kB
  • After minification 12.5 kB
  • After compression 3.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 2.6 kB, which is 17% 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 11.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 5.5 kB

  • Original 3.8 MB
  • After minification 3.8 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. WIZZM images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 5.3 kB

  • Original 27.7 kB
  • After minification 27.7 kB
  • After compression 22.4 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 5.3 kB or 19% of the original size.

CSS Optimization

-27%

Potential reduce by 864 B

  • Original 3.2 kB
  • After minification 3.2 kB
  • After compression 2.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. Wizzm.com needs all CSS files to be minified and compressed as it can save up to 864 B or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (24%)

Requests Now

37

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wizzm.com

wizzm.com

107 ms

jquery-latest.min.js

jquery-latest.min.js

33 ms

css

css

48 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

26 ms

jquery.animate-enhanced.min.js

jquery.animate-enhanced.min.js

45 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

45 ms

jquery.superslides.js

jquery.superslides.js

46 ms

superslides.css

superslides.css

45 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

43 ms

wookmark.min.js

wookmark.min.js

45 ms

ini.js

ini.js

50 ms

main.css

main.css

56 ms

modernizr.custom.01246.js

modernizr.custom.01246.js

66 ms

boxgrid.js

boxgrid.js

68 ms

wizzm-logo.png

wizzm-logo.png

98 ms

splash-7.jpg

splash-7.jpg

125 ms

splash-1.jpg

splash-1.jpg

100 ms

splash-2.jpg

splash-2.jpg

109 ms

splash-3.jpg

splash-3.jpg

98 ms

splash-4.jpg

splash-4.jpg

102 ms

splash-5.jpg

splash-5.jpg

108 ms

splash-6.jpg

splash-6.jpg

114 ms

slideshow-nav.png

slideshow-nav.png

111 ms

MyYogaOnline_thumb.jpg

MyYogaOnline_thumb.jpg

112 ms

SafetyDriven_thumb.jpg

SafetyDriven_thumb.jpg

133 ms

BCChicken_thumb.jpg

BCChicken_thumb.jpg

133 ms

BeezTreez_thumb.jpg

BeezTreez_thumb.jpg

134 ms

AndersonsLodge_thumb.jpg

AndersonsLodge_thumb.jpg

136 ms

ClearbrookCoffee_thumb.jpg

ClearbrookCoffee_thumb.jpg

137 ms

CedarPointLodge_thumb.jpg

CedarPointLodge_thumb.jpg

142 ms

SafetyDriven_thumb.jpg

SafetyDriven_thumb.jpg

143 ms

SafetyDriven_thumb.jpg

SafetyDriven_thumb.jpg

144 ms

DoerksenRoofing_thumb.jpg

DoerksenRoofing_thumb.jpg

143 ms

DrStefanSchlagintweit_thumb.jpg

DrStefanSchlagintweit_thumb.jpg

147 ms

NovotnyResolutions_thumb.jpg

NovotnyResolutions_thumb.jpg

147 ms

about-bg.jpg

about-bg.jpg

162 ms

close-icon.png

close-icon.png

153 ms

contact-bg.jpg

contact-bg.jpg

154 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

20 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

28 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

32 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

41 ms

Accessibility Review

wizzm.com accessibility score

62

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

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

wizzm.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wizzm.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

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

wizzm.com

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