Tools & Wizards About Us
handydart.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

handydart.com

BC Transit - handyDART | Schedules and Maps | BC Transit

Page Load Speed

1.1 sec in total

First Response

126 ms

Resources Loaded

871 ms

Page Rendered

121 ms

handydart.com screenshot

About Website

Welcome to handydart.com homepage info - get ready to check HandyDART best content for Canada right away, or after learning these important things about handydart.com

Victoria – handyDART is a transit service that helps those with disabilities reach their destinations.

Visit handydart.com

Key Findings

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

Performance Metrics

handydart.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value2,810 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

handydart.com

126 ms

handydart

372 ms

78 ms

gtm.js

48 ms

js

126 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Handydart.com, 79% (19 requests) were made to Bctransit.com and 8% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (372 ms) relates to the external source Bctransit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (67%)

Content Size

1.6 MB

After Optimization

505.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Handydart.com main page is 1.6 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. 35% of websites need less resources to load. Javascripts take 909.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 93.9 kB

  • Original 109.0 kB
  • After minification 88.4 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 20.6 kB, which is 19% 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 93.9 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 1.0 kB

  • Original 9.1 kB
  • After minification 8.1 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, HandyDART needs image optimization as it can save up to 1.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 480.7 kB

  • Original 909.5 kB
  • After minification 909.5 kB
  • After compression 428.8 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 480.7 kB or 53% of the original size.

CSS Optimization

-90%

Potential reduce by 470.4 kB

  • Original 524.1 kB
  • After minification 522.6 kB
  • After compression 53.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. Handydart.com needs all CSS files to be minified and compressed as it can save up to 470.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (62%)

Requests Now

21

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

handydart.com

handydart.com

126 ms

handydart

handydart

372 ms

78 ms

gtm.js

gtm.js

48 ms

js

js

126 ms

style.min.css

style.min.css

25 ms

styles.css

styles.css

22 ms

default.css

default.css

28 ms

frontend.css

frontend.css

63 ms

hooks.min.js

hooks.min.js

27 ms

i18n.min.js

i18n.min.js

26 ms

index.js

index.js

25 ms

index.js

index.js

26 ms

api.js

api.js

34 ms

wp-polyfill.min.js

wp-polyfill.min.js

32 ms

index.js

index.js

27 ms

frontend.js

frontend.js

90 ms

BCT_Logo_Print_rev_noborder.svg

BCT_Logo_Print_rev_noborder.svg

29 ms

bus-icon.png

bus-icon.png

31 ms

recaptcha__en.js

recaptcha__en.js

61 ms

2b87ee9349050e987093.webp

2b87ee9349050e987093.webp

47 ms

be39c776fc5005f3c4a7.webp

be39c776fc5005f3c4a7.webp

46 ms

6e6ed037acada77367d8.webp

6e6ed037acada77367d8.webp

47 ms

watermark-large.png

watermark-large.png

47 ms

Accessibility Review

handydart.com accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

handydart.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

handydart.com SEO score

81

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

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

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

handydart.com

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