Tools & Wizards About Us
northshorewwtp.ca screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

northshorewwtp.ca

North Shore Wastewater Treatment Plant Program | Metro Vancouver

Page Load Speed

3.9 sec in total

First Response

36 ms

Resources Loaded

3.8 sec

Page Rendered

82 ms

northshorewwtp.ca screenshot

About Website

Click here to check amazing North Shore Wwtp content. Otherwise, check out these important facts you probably never knew about northshorewwtp.ca

Project updates and timelines for the construction of a new tertiary treatment plant.

Visit northshorewwtp.ca

Key Findings

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

Performance Metrics

northshorewwtp.ca performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value11.6 s

5/100

10%

TBT (Total Blocking Time)

Value1,200 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

northshorewwtp.ca

36 ms

north-shore-wastewater-treatment-plant-project

939 ms

pagelayouts15.css

180 ms

corev15.css

397 ms

searchv15.css

353 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Northshorewwtp.ca, 91% (68 requests) were made to Metrovancouver.org and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Metrovancouver.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 500.6 kB (42%)

Content Size

1.2 MB

After Optimization

685.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Northshorewwtp.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. 55% of websites need less resources to load. Javascripts take 820.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 178.5 kB

  • Original 208.7 kB
  • After minification 201.1 kB
  • After compression 30.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. 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 178.5 kB or 86% of the original size.

Image Optimization

-20%

Potential reduce by 5.5 kB

  • Original 27.3 kB
  • After minification 21.8 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. Obviously, North Shore Wwtp needs image optimization as it can save up to 5.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-35%

Potential reduce by 284.8 kB

  • Original 820.8 kB
  • After minification 805.5 kB
  • After compression 536.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 284.8 kB or 35% of the original size.

CSS Optimization

-25%

Potential reduce by 31.8 kB

  • Original 129.6 kB
  • After minification 129.6 kB
  • After compression 97.8 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. Northshorewwtp.ca needs all CSS files to be minified and compressed as it can save up to 31.8 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (71%)

Requests Now

73

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

northshorewwtp.ca

northshorewwtp.ca

36 ms

north-shore-wastewater-treatment-plant-project

north-shore-wastewater-treatment-plant-project

939 ms

pagelayouts15.css

pagelayouts15.css

180 ms

corev15.css

corev15.css

397 ms

searchv15.css

searchv15.css

353 ms

css2

css2

35 ms

jquery-ui.min.css

jquery-ui.min.css

355 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

366 ms

uikit.min.css

uikit.min.css

568 ms

uikit-custom.css

uikit-custom.css

358 ms

app.css

app.css

477 ms

5a1f65d7ce.js

5a1f65d7ce.js

235 ms

initstrings.js

initstrings.js

440 ms

init.js

init.js

841 ms

theming.js

theming.js

456 ms

fixeditbuttons.js

fixeditbuttons.js

495 ms

ScriptResource.axd

ScriptResource.axd

687 ms

blank.js

blank.js

532 ms

ScriptResource.axd

ScriptResource.axd

591 ms

sp.res.js

sp.res.js

593 ms

sp.runtime.js

sp.runtime.js

702 ms

sp.init.js

sp.init.js

654 ms

sp.search.js

sp.search.js

702 ms

clientrenderer.js

clientrenderer.js

695 ms

srch.resources.js

srch.resources.js

735 ms

search.clientcontrols.js

search.clientcontrols.js

945 ms

search.cbs.js

search.cbs.js

784 ms

WebResource.axd

WebResource.axd

802 ms

jquery.js

jquery.js

956 ms

jquery-ui.min.js

jquery-ui.min.js

845 ms

uikit.min.js

uikit.min.js

1068 ms

uikit-icons.min.js

uikit-icons.min.js

1067 ms

jquery.cookie.js

jquery.cookie.js

898 ms

colors.js

colors.js

954 ms

app.js

app.js

1067 ms

consent.js

consent.js

1066 ms

element.js

element.js

39 ms

gtm.js

gtm.js

74 ms

favicon.ico

favicon.ico

175 ms

spcommon.png

spcommon.png

174 ms

mv-logo-dark.png

mv-logo-dark.png

198 ms

searchresultui.png

searchresultui.png

525 ms

pagelayouts15.css

pagelayouts15.css

522 ms

corev15.css

corev15.css

521 ms

searchv15.css

searchv15.css

521 ms

metro-bg.svg

metro-bg.svg

465 ms

font

font

394 ms

font

font

395 ms

searchcenterurl

searchcenterurl

333 ms

strings.js

strings.js

356 ms

ProcessQuery

ProcessQuery

622 ms

ProcessQuery

ProcessQuery

600 ms

ProcessQuery

ProcessQuery

600 ms

ProcessQuery

ProcessQuery

640 ms

ProcessQuery

ProcessQuery

683 ms

ProcessQuery

ProcessQuery

681 ms

ProcessQuery

ProcessQuery

960 ms

ProcessQuery

ProcessQuery

959 ms

ProcessQuery

ProcessQuery

963 ms

item_accordionsingle.js

item_accordionsingle.js

176 ms

group_content.js

group_content.js

175 ms

control_accordion.js

control_accordion.js

177 ms

item_constructionupdate.js

item_constructionupdate.js

173 ms

control_panel.js

control_panel.js

209 ms

item_photogallerysmall.js

item_photogallerysmall.js

207 ms

control_gallery4across.js

control_gallery4across.js

207 ms

item_vimeo.js

item_vimeo.js

204 ms

control_grid1across.js

control_grid1across.js

244 ms

item_timeline.js

item_timeline.js

306 ms

control_timeline.js

control_timeline.js

323 ms

liquid-waste-bg.svg

liquid-waste-bg.svg

729 ms

loading.GIF

loading.GIF

263 ms

core.js

core.js

786 ms

customstrings.js

customstrings.js

270 ms

colors.js

colors.js

298 ms

Accessibility Review

northshorewwtp.ca accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

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

northshorewwtp.ca 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-10

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Northshorewwtp.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 Northshorewwtp.ca main page’s claimed encoding is utf-10. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

northshorewwtp.ca

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