3.7 sec in total
53 ms
2.8 sec
801 ms
Click here to check amazing Durham Region content for Canada. Otherwise, check out these important facts you probably never knew about durhamregion.com
Stay informed with the latest news updates from our Durham Region news website. Breaking news, top stories, politics, business, sports, & more.
Visit durhamregion.comWe analyzed Durhamregion.com page load time and found that the first response time was 53 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
durhamregion.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value13.4 s
0/100
25%
Value14.3 s
1/100
10%
Value6,610 ms
0/100
30%
Value0.001
100/100
15%
Value29.1 s
0/100
10%
53 ms
181 ms
110 ms
118 ms
137 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 6% of them (7 requests) were addressed to the original Durhamregion.com, 47% (59 requests) were made to Bloximages.chicago2.vip.townnews.com and 7% (9 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 Polyfill.io.
Page size can be reduced by 634.3 kB (28%)
2.3 MB
1.6 MB
In fact, the total size of Durhamregion.com main page is 2.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 960.5 kB which makes up the majority of the site volume.
Potential reduce by 457.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 76.1 kB, which is 15% 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 457.1 kB or 89% of the original size.
Potential reduce by 33.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. Durham Region images are well optimized though.
Potential reduce by 132.4 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 132.4 kB or 14% of the original size.
Potential reduce by 11.6 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. Durhamregion.com needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 19% of the original size.
Number of requests can be reduced by 65 (59%)
111
46
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Durham 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 52 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
durhamregion.com
53 ms
www.durhamregion.com
181 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
110 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
118 ms
oovvuu.css
137 ms
flex-utility-promo-button.52347555fbb6668223efabadb9c9d111.css
138 ms
flex-utility-text-promo.945a2efac4892ce469180c513f411107.css
135 ms
flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css
129 ms
access.d7adebba498598b0ec2c.js
87 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
133 ms
user.js
127 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
132 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
132 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
168 ms
application.3c64d611e594b45dd35b935162e79d85.js
171 ms
polyfill.min.js
1079 ms
footer.nav.js
170 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
170 ms
gpt.js
180 ms
18488.js
178 ms
alertbar.js
166 ms
api.js
130 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
168 ms
tracking.js
129 ms
save.asset.js
176 ms
index.js
94 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
177 ms
amp-iframe-0.1.js
98 ms
launch-9387fe3a1e9f.min.js
97 ms
css2
128 ms
tracker.js
161 ms
get.js
66 ms
newsletter-helper.min.js
138 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
138 ms
sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js
137 ms
tnt.regions.b44801b45845a81b995eeaad12f4f276.js
137 ms
gtm.js
59 ms
analytics.js
20 ms
gtm.js
26 ms
gtm.js
49 ms
publisher:getClientId
103 ms
destination
35 ms
collect
17 ms
collect
99 ms
apstag.js
165 ms
channels.cgi
162 ms
gtm.js
141 ms
e38191f8-a657-11ed-b48d-0f20d867b51f.png
138 ms
eyJkIjo3MiwieCI6IjAiLCJ5IjoiMTYxIiwiY3ciOiIxMDgwIiwiY2giOiIxMzg5LjEwMzQ0ODI3NTg2MTkiLCJybyI6IjAiLCJjciI6IjEiLCJ3IjoxMDgwLCJoIjoxNzEzLCJ1cmwiOiJodHRwOlwvXC9hZGFzLW9yZWdvbi1jYXMtb2JpdHMuczMuYW1hem9uYXdzLmNvbVwvcGhvdG9zXC9jcmVhdGVfc3RvcnlcLzY2MzI5MjY1NzllNDVcL2I4NmVkMjEzNTlhN2Q5OTM2ODU5NWViOTIyMDAuanBnIn0=
140 ms
logo-with-tagline_1663581596-aLvwXJ0fe8Jf9Og.jpg
540 ms
eyJoIjoxMTc0LCJ3Ijo4NDMsInVybCI6Imh0dHA6XC9cL2FkYXMtb3JlZ29uLWNhcy1vYml0cy5zMy5hbWF6b25hd3MuY29tXC9waG90b3NcL2NyZWF0ZV9zdG9yeVwvNjYzM2JkZTk0ZTliN1wvNTMyMzlmY2YyZWI0ODc5OTJmZjhjZjRjNmVmNi5qcGcifQ==
139 ms
eyJkIjo3MiwieCI6IjAiLCJ5IjoiMTI2IiwiY3ciOiI3MTIiLCJjaCI6IjkxNS43NzkzMTAzNDQ4Mjc2Iiwicm8iOiIwIiwiY3IiOiIxIiwidyI6NzEyLCJoIjoxMTY2LCJ1cmwiOiJodHRwOlwvXC9hZGFzLW9yZWdvbi1jYXMtb2JpdHMuczMuYW1hem9uYXdzLmNvbVwvcGhvdG9zXC9jcmVhdGVfc3RvcnlcLzY2MzE1NTQzMTEzOTRcLzk3YzQxYTg5ZjNiYmNkZWY5MDI3MTA0YTFhM2MuanBnIn0=
139 ms
eyJoIjo0NzEsInciOjM1OCwidXJsIjoiaHR0cDpcL1wvYWRhcy1vcmVnb24tY2FzLW9iaXRzLnMzLmFtYXpvbmF3cy5jb21cL3Bob3Rvc1wvY3JlYXRlX3N0b3J5XC82NjJjMTQzMTg2YzU1XC9jMTBjYWE3MDdhMDhiZjU0NjZhMDI0ZTViNWRmLmpwZyJ9
103 ms
98291d2c-808a-11ed-bb05-e711f815154e.png
132 ms
guest.svg
133 ms
signed-in.svg
129 ms
9824298e-808a-11ed-bb04-235b451df541.png
130 ms
663bb44b62c84.image.jpg
325 ms
663be6647078c.image.jpg
370 ms
663bc495ec39c.image.jpg
324 ms
663b8326a2e66.image.jpg
324 ms
663bd8a87e230.image.jpg
324 ms
663a8dcad4946.image.jpg
369 ms
66313551f2344.image.jpg
392 ms
663be86c289a2.image.jpg
393 ms
663bd7049ec37.image.jpg
392 ms
663930d181b30.image.jpg
392 ms
663a7df985567.image.jpg
390 ms
a534d724-e86f-11ee-9826-4f556dbba10e.jpg
391 ms
663bcbc4a18d5.image.jpg
534 ms
663ba29c26c45.image.jpg
536 ms
6632b87011da7.image.jpg
535 ms
663aa464bb4da.image.jpg
535 ms
65cba50b25f6b.image.jpg
535 ms
66269f5371f45.image.jpg
534 ms
66195e5bdd4c8.image.jpg
602 ms
6604779b13089.image.jpg
587 ms
66314ab4912ae.image.jpg
586 ms
663a031445e4d.image.jpg
585 ms
661ea883ecd19.image.jpg
586 ms
6616f753bd660.image.jpg
585 ms
65f604e202279.image.jpg
600 ms
66354c3d96685.image.jpg
600 ms
64edfa02848a8.image.jpg
599 ms
64edfa08e27e6.image.jpg
600 ms
66294ce045169.image.jpg
599 ms
66294d04d4efe.image.jpg
648 ms
661fcd3ac5a3d.image.jpg
649 ms
pubads_impl.js
140 ms
recaptcha__en.js
318 ms
tracker.gif
56 ms
analytics.min.js
456 ms
apstag.js
443 ms
661fcd022b54b.image.jpg
525 ms
97ec7912-808a-11ed-bb03-3788d5eecaa4.png
525 ms
web-vitals.iife.js
345 ms
58580620
241 ms
10896.jsx
235 ms
web-vitals.iife.js
66 ms
settings
58 ms
WidgetTemplate2.min.css
40 ms
jquery@3.1.0(jquery.slim.min.js),velocity@1.2.3(velocity.min.js+velocity.ui.min.js)
86 ms
jquery.fireSlider.min.js
38 ms
rad.js
39 ms
css
48 ms
css
70 ms
AGSKWxWO1C1_1Ad3cPHlcItKZkLTEbtdDpg9a7Vbf4i2E_FTxf7e1RXyoci6i7r2g3ov8Ivsa2DaoRIKIBJJqlhySaBhGAy-sF-JcBjUXn5_1gZmIhDbwC9_vjDEdEMpNmW-gBENxPr87w==
180 ms
esp.js
309 ms
esp.js
203 ms
uid2SecureSignal.js
169 ms
p-uq0GLFySb_d1T.gif
310 ms
870.bundle.6e2976b75e60ab2b2bf8.js
178 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
178 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
291 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
292 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
365 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
369 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
386 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
385 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
386 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf
387 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
384 ms
icomoon.woff
175 ms
AGSKWxXQ2Xk8BY0CWuB-KeaZrDgqba1eRovJi8yo_JpIFuMb3taRGjIM9xnMaIstOp5qkdIQnP0_BtaMcqJXLqRg51QIVGvxdyjD2x-iEZ740uCmXUmu5Dbz5YKzmcG2MSjtvrraoafpmA==
126 ms
js
241 ms
js
136 ms
durhamregion.com accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
durhamregion.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
durhamregion.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Durhamregion.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 Durhamregion.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.
durhamregion.com
Open Graph data is detected on the main page of Durham Region. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: