Tools & Wizards About Us
purewoodinc.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

purewoodinc.com

Kitchen Cabinets & Doors Mississauga | Purewood Inc.

Page Load Speed

2.9 sec in total

First Response

889 ms

Resources Loaded

1.6 sec

Page Rendered

405 ms

purewoodinc.com screenshot

About Website

Welcome to purewoodinc.com homepage info - get ready to check Purewood Inc best content right away, or after learning these important things about purewoodinc.com

Purewood cabinets exceed our competitors’ products which are priced significantly higher. We Are is conscientiousness about the environment!

Visit purewoodinc.com

Key Findings

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

Performance Metrics

purewoodinc.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

purewoodinc.com

889 ms

wp-emoji-release.min.js

15 ms

209 ms

css

31 ms

jquery.js

22 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 83% of them (29 requests) were addressed to the original Purewoodinc.com, 6% (2 requests) were made to Google-analytics.com and 6% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (889 ms) belongs to the original domain Purewoodinc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.1 kB (2%)

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Purewoodinc.com main page is 2.8 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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 58.4 kB

  • Original 69.5 kB
  • After minification 66.8 kB
  • After compression 11.1 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 58.4 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 2.5 kB

  • Original 2.5 MB
  • After minification 2.5 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. Purewood Inc images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 196 B

  • Original 220.5 kB
  • After minification 220.5 kB
  • After compression 220.3 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.

Requests Breakdown

Number of requests can be reduced by 7 (22%)

Requests Now

32

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

purewoodinc.com

purewoodinc.com

889 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

15 ms

209 ms

css

css

31 ms

jquery.js

jquery.js

22 ms

main.min.js

main.min.js

31 ms

email-decode.min.js

email-decode.min.js

30 ms

jquery-migrate.min.js

jquery-migrate.min.js

28 ms

85 ms

analytics.js

analytics.js

224 ms

purewood_logo.png

purewood_logo.png

212 ms

3d_laminate_parallax6.jpg

3d_laminate_parallax6.jpg

226 ms

3d_laminate_thm.png

3d_laminate_thm.png

226 ms

1_piece_parallax.jpg

1_piece_parallax.jpg

227 ms

1_piece_thm.png

1_piece_thm.png

226 ms

painted-two-piece_page_title.jpg

painted-two-piece_page_title.jpg

227 ms

2-piece-thm.png

2-piece-thm.png

226 ms

5_piece_parallax.jpg

5_piece_parallax.jpg

239 ms

5_piece_thm.png

5_piece_thm.png

240 ms

wood_parallax.jpg

wood_parallax.jpg

238 ms

solid_wood_thm.png

solid_wood_thm.png

238 ms

13173850-2-300x225.jpg

13173850-2-300x225.jpg

237 ms

whitwood-portfolio-0.jpg

whitwood-portfolio-0.jpg

239 ms

kitchen-3-2.jpg

kitchen-3-2.jpg

249 ms

kitchen-2-1.jpg

kitchen-2-1.jpg

248 ms

davisville_kitchens_feat3.jpg

davisville_kitchens_feat3.jpg

249 ms

font

font

125 ms

icomoon.woff

icomoon.woff

261 ms

font

font

138 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

301 ms

collect

collect

24 ms

js

js

63 ms

whitwood-2.jpg

whitwood-2.jpg

18 ms

kitchen-transitional-cabinets.jpg

kitchen-transitional-cabinets.jpg

18 ms

kitchen-cabinet-doors.jpg

kitchen-cabinet-doors.jpg

15 ms

Accessibility Review

purewoodinc.com accessibility score

93

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

Links do not have a discernible name

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

purewoodinc.com SEO score

93

Search Engine Optimization Advices

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

purewoodinc.com

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