Tools & Wizards About Us
gpiweb.ca screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

gpiweb.ca

Home and Commercial Property Inspections | Global Property Inspections

Page Load Speed

4.4 sec in total

First Response

75 ms

Resources Loaded

3.9 sec

Page Rendered

417 ms

gpiweb.ca screenshot

About Website

Visit gpiweb.ca now to see the best up-to-date Gpiweb content and also check out these interesting facts you probably never knew about gpiweb.ca

Founded in 1987, GPI is among the oldest and most widely-respected names in the commercial and home inspection business. Each year, we perform tens of thousands of independent, objective real estate i...

Visit gpiweb.ca

Key Findings

We analyzed Gpiweb.ca page load time and found that the first response time was 75 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

gpiweb.ca performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

gpiweb.ca

75 ms

gpiweb.ca

2066 ms

css

46 ms

js

83 ms

uc.js

66 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 78% of them (49 requests) were addressed to the original Gpiweb.ca, 11% (7 requests) were made to Npiweb.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Gpiweb.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (45%)

Content Size

4.0 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gpiweb.ca main page is 4.0 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. 60% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 46.7 kB

  • Original 55.4 kB
  • After minification 41.4 kB
  • After compression 8.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 14.0 kB, which is 25% 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 46.7 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 50.3 kB

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

JavaScript Optimization

-71%

Potential reduce by 904.7 kB

  • Original 1.3 MB
  • After minification 1.0 MB
  • After compression 369.0 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 904.7 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 785.3 kB

  • Original 911.5 kB
  • After minification 820.5 kB
  • After compression 126.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. Gpiweb.ca needs all CSS files to be minified and compressed as it can save up to 785.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (50%)

Requests Now

58

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gpiweb.ca

gpiweb.ca

75 ms

gpiweb.ca

gpiweb.ca

2066 ms

css

css

46 ms

js

js

83 ms

uc.js

uc.js

66 ms

default.css

default.css

392 ms

SearchSkinObjectPreview.css

SearchSkinObjectPreview.css

360 ms

portal.css

portal.css

363 ms

NPI2a.base.css

NPI2a.base.css

514 ms

Home.css

Home.css

159 ms

Style.css

Style.css

363 ms

NPI2a.theme.css

NPI2a.theme.css

522 ms

js

js

72 ms

jquery.js

jquery.js

472 ms

jquery-migrate.js

jquery-migrate.js

409 ms

jquery-ui.js

jquery-ui.js

753 ms

webAPI.min.js

webAPI.min.js

433 ms

WebResource.axd

WebResource.axd

453 ms

ScriptResource.axd

ScriptResource.axd

473 ms

ScriptResource.axd

ScriptResource.axd

499 ms

dnn.js

dnn.js

707 ms

dnn.modalpopup.js

dnn.modalpopup.js

706 ms

dnncore.js

dnncore.js

711 ms

SearchSkinObjectPreview.js

SearchSkinObjectPreview.js

711 ms

dnn.servicesframework.js

dnn.servicesframework.js

709 ms

menu.min.js

menu.min.js

752 ms

css

css

57 ms

NPI2a.base.js

NPI2a.base.js

752 ms

NPI2a.js

NPI2a.js

691 ms

npicorporate.custom.css

npicorporate.custom.css

396 ms

NPI2a.base-1.css

NPI2a.base-1.css

320 ms

NPI2a.base-2.css

NPI2a.base-2.css

547 ms

NPI2a.custom.css

NPI2a.custom.css

282 ms

house-orange.png

house-orange.png

318 ms

building-orange.png

building-orange.png

320 ms

tools-orange.png

tools-orange.png

322 ms

themostimportantfeaturesforanaccessiblehome-04.jpg

themostimportantfeaturesforanaccessiblehome-04.jpg

429 ms

how%20to%20clean%20outside%20your%20house%20the%20right%20way-04.jpg

how%20to%20clean%20outside%20your%20house%20the%20right%20way-04.jpg

469 ms

Bleach-04.jpg

Bleach-04.jpg

322 ms

how%20to%20revive%20a%20tired%20deck%20this%20spring-04.jpg

how%20to%20revive%20a%20tired%20deck%20this%20spring-04.jpg

496 ms

GPIheaderlogo.png

GPIheaderlogo.png

318 ms

findaninspector.png

findaninspector.png

56 ms

heromobile.jpg

heromobile.jpg

57 ms

Square%20-%20Green.png

Square%20-%20Green.png

323 ms

buyers.jpg

buyers.jpg

324 ms

prelisting.png

prelisting.png

318 ms

more%20res.jpg

more%20res.jpg

322 ms

apartment.jpeg

apartment.jpeg

322 ms

commercialdraw.png

commercialdraw.png

357 ms

restaurant.jpg

restaurant.jpg

367 ms

radon-03.jpg

radon-03.jpg

372 ms

mold.jpg

mold.jpg

368 ms

more%20add%20ons.jpg

more%20add%20ons.jpg

370 ms

With%20Text%20and%20Slogan%20Transparent%20White.png

With%20Text%20and%20Slogan%20Transparent%20White.png

370 ms

hero.jpg

hero.jpg

399 ms

map.jpg

map.jpg

352 ms

map-mobile.jpg

map-mobile.jpg

355 ms

projectsgraphic.png

projectsgraphic.png

357 ms

social-sprites.png

social-sprites.png

357 ms

font

font

135 ms

font

font

213 ms

fa-solid-900.woff

fa-solid-900.woff

590 ms

fa-regular-400.woff

fa-regular-400.woff

577 ms

Accessibility Review

gpiweb.ca accessibility score

85

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

gpiweb.ca best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

gpiweb.ca SEO score

85

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gpiweb.ca 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 Gpiweb.ca 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

gpiweb.ca

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