Tools & Wizards About Us
web3.ca screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

web3.ca

Edmonton Web Design & Development Company | Web3

Page Load Speed

1.8 sec in total

First Response

33 ms

Resources Loaded

1.1 sec

Page Rendered

739 ms

web3.ca screenshot

About Website

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

Built on the Web3 Framework, our websites are built for SEO and designed to help our clients stand out online! Call 780-760-3333

Visit web3.ca

Key Findings

We analyzed Web3.ca page load time and found that the first response time was 33 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

web3.ca performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

web3.ca

33 ms

web3.ca

35 ms

www.web3.ca

111 ms

plusone.js

51 ms

analytics.js

76 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 31% of them (11 requests) were addressed to the original Web3.ca, 11% (4 requests) were made to Googletagmanager.com and 9% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (498 ms) relates to the external source Sc.lfeeder.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 387.2 kB (33%)

Content Size

1.2 MB

After Optimization

781.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Web3.ca main page is 1.2 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. 70% of websites need less resources to load. HTML takes 491.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 386.1 kB

  • Original 491.6 kB
  • After minification 490.9 kB
  • After compression 105.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. 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 386.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 437 B

  • Original 380.8 kB
  • After minification 380.4 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. Web3 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 663 B

  • Original 296.5 kB
  • After minification 296.5 kB
  • After compression 295.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.

Requests Breakdown

Number of requests can be reduced by 18 (64%)

Requests Now

28

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

web3.ca

web3.ca

33 ms

web3.ca

web3.ca

35 ms

www.web3.ca

www.web3.ca

111 ms

plusone.js

plusone.js

51 ms

analytics.js

analytics.js

76 ms

js

js

401 ms

gtm.js

gtm.js

456 ms

css2

css2

63 ms

email-decode.min.js

email-decode.min.js

24 ms

conversion.js

conversion.js

268 ms

js

js

386 ms

109067.js

109067.js

386 ms

autoptimize_46799143112168cf572c55c7a59ad7ee.js

autoptimize_46799143112168cf572c55c7a59ad7ee.js

47 ms

icon_Google_G_Logo.png

icon_Google_G_Logo.png

46 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

224 ms

scroll-bg.png

scroll-bg.png

200 ms

collect

collect

158 ms

collect

collect

218 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

226 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

289 ms

web3-icon.ttf

web3-icon.ttf

150 ms

276 ms

app.js

app.js

392 ms

sub.min.js

sub.min.js

166 ms

picturefill.min.js

picturefill.min.js

167 ms

lftracker_v1_bElvO73KX217ZMqj.js

lftracker_v1_bElvO73KX217ZMqj.js

498 ms

232 ms

loader.js

loader.js

232 ms

js

js

113 ms

edmonton_web_design_landscape_lg.jpg

edmonton_web_design_landscape_lg.jpg

169 ms

js

js

187 ms

106 ms

call-tracking_9.js

call-tracking_9.js

8 ms

23 ms

wcm

wcm

14 ms

Accessibility Review

web3.ca accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

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

Heading elements are not in a sequentially-descending order

Best Practices

web3.ca 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

web3.ca SEO score

93

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

Links do not have descriptive text

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

web3.ca

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