Tools & Wizards About Us
experienceyorkregion.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

experienceyorkregion.com

Experience York Region: Things to Do, See & Visit

Page Load Speed

2.5 sec in total

First Response

197 ms

Resources Loaded

1.5 sec

Page Rendered

807 ms

experienceyorkregion.com screenshot

About Website

Click here to check amazing Experience York Region content for Canada. Otherwise, check out these important facts you probably never knew about experienceyorkregion.com

The official source for fun things to do in York Region and its communities. Experience fun things to do, local events, attractions, restaurants, and culture.

Visit experienceyorkregion.com

Key Findings

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

Performance Metrics

experienceyorkregion.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

www.experienceyorkregion.com

197 ms

tribe-events-pro-mini-calendar-block.min.css

61 ms

dashicons.min.css

86 ms

variables-skeleton.min.css

63 ms

variables-full.min.css

64 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 97% of them (109 requests) were addressed to the original Experienceyorkregion.com, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (211 ms) belongs to the original domain Experienceyorkregion.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.1 kB (40%)

Content Size

530.7 kB

After Optimization

319.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Experienceyorkregion.com main page is 530.7 kB. 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 252.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 208.8 kB

  • Original 252.0 kB
  • After minification 251.7 kB
  • After compression 43.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 208.8 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 916 B

  • Original 56.1 kB
  • After minification 55.2 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. Experience York Region images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

  • Original 222.7 kB
  • After minification 222.7 kB
  • After compression 221.2 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 105 (96%)

Requests Now

109

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.experienceyorkregion.com

www.experienceyorkregion.com

197 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

61 ms

dashicons.min.css

dashicons.min.css

86 ms

variables-skeleton.min.css

variables-skeleton.min.css

63 ms

variables-full.min.css

variables-full.min.css

64 ms

common-skeleton.min.css

common-skeleton.min.css

66 ms

common-full.min.css

common-full.min.css

67 ms

tickets.min.css

tickets.min.css

81 ms

rsvp-v1.min.css

rsvp-v1.min.css

84 ms

sbi-styles.min.css

sbi-styles.min.css

87 ms

bbpress.min.css

bbpress.min.css

90 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

88 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

101 ms

widget-base.min.css

widget-base.min.css

105 ms

la-index.css

la-index.css

104 ms

login-index.css

login-index.css

107 ms

ti-index.css

ti-index.css

110 ms

fi-index.css

fi-index.css

110 ms

flist-index.css

flist-index.css

120 ms

topic-views-index.css

topic-views-index.css

123 ms

statistics-index.css

statistics-index.css

125 ms

search-index.css

search-index.css

127 ms

autoptimize_single_f80185da0113d9a933c58e7d303d55ee.css

autoptimize_single_f80185da0113d9a933c58e7d303d55ee.css

134 ms

autoptimize_single_b5b9ffb78ea0da57a8f90848961ee1e5.css

autoptimize_single_b5b9ffb78ea0da57a8f90848961ee1e5.css

132 ms

autoptimize_single_b81071258b335493df025098de46f424.css

autoptimize_single_b81071258b335493df025098de46f424.css

139 ms

autoptimize_single_37faeb50ef52da086e0f8c2c289e66d4.css

autoptimize_single_37faeb50ef52da086e0f8c2c289e66d4.css

142 ms

autoptimize_single_d86fe994e992ae607b466f7ee9e64a43.css

autoptimize_single_d86fe994e992ae607b466f7ee9e64a43.css

146 ms

style-front-end.css

style-front-end.css

149 ms

autoptimize_single_a89d53f919f4e1025916aa31bfe93fd7.css

autoptimize_single_a89d53f919f4e1025916aa31bfe93fd7.css

153 ms

autoptimize_single_06bd37f43844064963836d66da85e893.css

autoptimize_single_06bd37f43844064963836d66da85e893.css

154 ms

events-community-tickets.min.css

events-community-tickets.min.css

157 ms

style.min.css

style.min.css

162 ms

theme.min.css

theme.min.css

167 ms

header-footer.min.css

header-footer.min.css

169 ms

frontend-lite.min.css

frontend-lite.min.css

201 ms

post-12322.css

post-12322.css

179 ms

webfont.js

webfont.js

21 ms

api.js

api.js

43 ms

elementor-icons.min.css

elementor-icons.min.css

141 ms

swiper.min.css

swiper.min.css

127 ms

frontend-lite.min.css

frontend-lite.min.css

132 ms

global.css

global.css

134 ms

post-37.css

post-37.css

136 ms

post-12328.css

post-12328.css

136 ms

post-12341.css

post-12341.css

156 ms

events-virtual-single-block.min.css

events-virtual-single-block.min.css

131 ms

style.min.css

style.min.css

153 ms

rsvp.min.css

rsvp.min.css

134 ms

leaflet.min.css

leaflet.min.css

153 ms

openstreet.min.css

openstreet.min.css

136 ms

public-main.min.css

public-main.min.css

153 ms

select2.min.css

select2.min.css

137 ms

ez-media-uploader.min.css

ez-media-uploader.min.css

143 ms

slick.min.css

slick.min.css

161 ms

sweetalert.min.css

sweetalert.min.css

158 ms

autoptimize_single_830916d353f8f85890a8bcf4dc41ae46.css

autoptimize_single_830916d353f8f85890a8bcf4dc41ae46.css

159 ms

google-fonts-1-mod-p9pg9.css

google-fonts-1-mod-p9pg9.css

150 ms

fontawesome.min.css

fontawesome.min.css

149 ms

solid.min.css

solid.min.css

151 ms

brands.min.css

brands.min.css

148 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

150 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

150 ms

widget-loop-builder.min.css

widget-loop-builder.min.css

144 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

150 ms

widget-posts.min.css

widget-posts.min.css

150 ms

animations.min.css

animations.min.css

146 ms

jquery-ui-slider.min.css

jquery-ui-slider.min.css

144 ms

acf-global.css

acf-global.css

183 ms

autoptimize_single_b38a04fcd79a861edd13c7311702c01b.css

autoptimize_single_b38a04fcd79a861edd13c7311702c01b.css

150 ms

frontend-admin-min.css

frontend-admin-min.css

153 ms

modal-min.css

modal-min.css

147 ms

jquery.min.js

jquery.min.js

155 ms

jquery-migrate.min.js

jquery-migrate.min.js

139 ms

autoptimize_single_490f4209174a510cb9646f0676c05caf.js

autoptimize_single_490f4209174a510cb9646f0676c05caf.js

156 ms

autoptimize_single_eb63fe10bfa1ce6b46ec4caa171f6252.js

autoptimize_single_eb63fe10bfa1ce6b46ec4caa171f6252.js

155 ms

autoptimize_single_d2ef69e593105b75a319e38ad493a709.js

autoptimize_single_d2ef69e593105b75a319e38ad493a709.js

146 ms

rsvp.min.js

rsvp.min.js

144 ms

ticket-details.min.js

ticket-details.min.js

211 ms

mailoptin.min.js

mailoptin.min.js

208 ms

autoptimize_single_7d5b8a506f219d783db98476f6bce455.js

autoptimize_single_7d5b8a506f219d783db98476f6bce455.js

202 ms

hello-frontend.min.js

hello-frontend.min.js

198 ms

app.min.js

app.min.js

191 ms

jquery.sticky.min.js

jquery.sticky.min.js

181 ms

lc.js

lc.js

182 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

181 ms

imagesloaded.min.js

imagesloaded.min.js

179 ms

core.min.js

core.min.js

174 ms

mouse.min.js

mouse.min.js

157 ms

autoptimize_single_4cc86d1003c45134d6838f13e3885db1.js

autoptimize_single_4cc86d1003c45134d6838f13e3885db1.js

153 ms

autoptimize_single_e63556d9f748024669aff20930dea04d.js

autoptimize_single_e63556d9f748024669aff20930dea04d.js

154 ms

slider.min.js

slider.min.js

153 ms

sbi-scripts.min.js

sbi-scripts.min.js

154 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

211 ms

webpack.runtime.min.js

webpack.runtime.min.js

210 ms

frontend-modules.min.js

frontend-modules.min.js

203 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

201 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

202 ms

wp-polyfill.min.js

wp-polyfill.min.js

202 ms

hooks.min.js

hooks.min.js

194 ms

i18n.min.js

i18n.min.js

192 ms

frontend.min.js

frontend.min.js

190 ms

waypoints.min.js

waypoints.min.js

190 ms

frontend.min.js

frontend.min.js

179 ms

elements-handlers.min.js

elements-handlers.min.js

173 ms

modal-min.js

modal-min.js

173 ms

autoptimize_single_22f3d66fb410703cc0292c332fd0f895.js

autoptimize_single_22f3d66fb410703cc0292c332fd0f895.js

171 ms

lazyload.min.js

lazyload.min.js

154 ms

sbi-sprite.png

sbi-sprite.png

143 ms

Experience-York-Region-Logo-rgb-1024x363.png

Experience-York-Region-Logo-rgb-1024x363.png

147 ms

fa-solid-900.woff

fa-solid-900.woff

51 ms

fa-brands-400.woff

fa-brands-400.woff

69 ms

recaptcha__en.js

recaptcha__en.js

46 ms

Accessibility Review

experienceyorkregion.com accessibility score

84

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

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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 IDs 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

Links do not have a discernible name

Best Practices

experienceyorkregion.com best practices score

92

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

SEO Factors

experienceyorkregion.com SEO score

92

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

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

experienceyorkregion.com

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