2.9 sec in total
42 ms
2 sec
877 ms
Click here to check amazing Innisfilexaminer content. Otherwise, check out these important facts you probably never knew about innisfilexaminer.ca
Stay informed with the latest news updates from the Simcoe County news website. Breaking news, top stories, politics, business, sports, & more.
Visit innisfilexaminer.caWe analyzed Innisfilexaminer.ca page load time and found that the first response time was 42 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
innisfilexaminer.ca performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value10.5 s
0/100
25%
Value12.2 s
3/100
10%
Value5,700 ms
0/100
30%
Value0
100/100
15%
Value27.6 s
0/100
10%
42 ms
212 ms
105 ms
115 ms
134 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Innisfilexaminer.ca, 29% (28 requests) were made to Bloximages.chicago2.vip.townnews.com and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (689 ms) relates to the external source Volunteer-success.nyc3.digitaloceanspaces.com.
Page size can be reduced by 603.7 kB (12%)
5.2 MB
4.6 MB
In fact, the total size of Innisfilexaminer.ca main page is 5.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. 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. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 429.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. This page needs HTML code to be minified as it can gain 74.5 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 429.5 kB or 89% of the original size.
Potential reduce by 136.5 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. Innisfilexaminer images are well optimized though.
Potential reduce by 26.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. This website has mostly compressed JavaScripts.
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. Innisfilexaminer.ca 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 61 (74%)
82
21
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Innisfilexaminer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
innisfilexaminer.ca
42 ms
www.simcoe.com
212 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
105 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
115 ms
oovvuu.css
134 ms
flex-utility-promo-button.52347555fbb6668223efabadb9c9d111.css
128 ms
flex-utility-text-promo.945a2efac4892ce469180c513f411107.css
130 ms
flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css
114 ms
access.d7adebba498598b0ec2c.js
79 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
119 ms
user.js
98 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
123 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
153 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
128 ms
application.3c64d611e594b45dd35b935162e79d85.js
153 ms
polyfill.min.js
375 ms
footer.nav.js
153 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
153 ms
gpt.js
153 ms
18488.js
116 ms
alertbar.js
154 ms
api.js
86 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
153 ms
tracking.js
106 ms
save.asset.js
158 ms
index.js
80 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
156 ms
amp-iframe-0.1.js
87 ms
launch-9387fe3a1e9f.min.js
86 ms
css2
102 ms
tracker.js
105 ms
get.js
63 ms
newsletter-helper.min.js
127 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
128 ms
sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js
129 ms
tnt.regions.b44801b45845a81b995eeaad12f4f276.js
132 ms
gtm.js
60 ms
analytics.js
15 ms
gtm.js
86 ms
gtm.js
34 ms
publisher:getClientId
90 ms
destination
139 ms
collect
128 ms
collect
255 ms
apstag.js
378 ms
channels.cgi
601 ms
gtm.js
331 ms
f350d956-80a8-11ed-bb06-5391644accab.png
185 ms
eyJkIjo3MiwidyI6NjA0LCJoIjo4NTgsInVybCI6Imh0dHA6XC9cL2FkYXMtb3JlZ29uLWNhcy1vYml0cy5zMy5hbWF6b25hd3MuY29tXC9waG90b3NcL2NyZWF0ZV9zdG9yeVwvNjYzMjcxOTUwODI1ZVwvZThkOTQ3YmFhYzcxNjVlMzkzNjBlYjU2MjkwZi5qcGcifQ==
330 ms
BIALogo_1691769838-A3pLJsCxJaVJ9bU.png
556 ms
eyJjaCI6MTYxLCJjciI6MSwiY3ciOjE1MCwicm8iOjAsImgiOjIyMSwibSI6IkpQRyIsInciOjE1MCwieCI6MCwieSI6MzEsInVybCI6Imh0dHA6XC9cL2FkYXMtb3JlZ29uLWNhcy1vYml0cy5zMy5hbWF6b25hd3MuY29tXC9waG90b3NcL2NyZWF0ZV9zdG9yeVwvNjYzY2ZlODI0MGNjMVwvMjVhZTlkMmJhZjM2NDVmZGY4OWQyMzU1YzkyYi5wbmcifQ==
329 ms
eyJoIjoyMjEsIm0iOiJKUEciLCJ3IjoxNTAsInVybCI6Imh0dHA6XC9cL2FkYXMtb3JlZ29uLWNhcy1vYml0cy5zMy5hbWF6b25hd3MuY29tXC9waG90b3NcL2NyZWF0ZV9zdG9yeVwvNjYzY2ZmNzE0NGRhOFwvOWQyYTI2OTZiYjIxNGU4M2I5ZjczYTg4YjZjNy5wbmcifQ==
329 ms
eyJoIjoxNTI1LCJ3IjoxMDgwLCJ1cmwiOiJodHRwOlwvXC9hZGFzLW9yZWdvbi1jYXMtb2JpdHMuczMuYW1hem9uYXdzLmNvbVwvcGhvdG9zXC9jcmVhdGVfc3RvcnlcLzY2MzkwNjQxYWUwMjJcLzM1ZWExNWI3NjI2YTMyZTkwNzZlN2ZiYTQ5NjUucG5nIn0=
432 ms
IMG4013_1703790433-nIUNZt2mDzGt4qc.jpg
689 ms
f34f2c78-80a8-11ed-bb05-c767ba890cc7.png
187 ms
guest.svg
326 ms
signed-in.svg
181 ms
f34d5d08-80a8-11ed-bb04-fb7a906d666a.png
182 ms
d43d4038-9833-11ee-ac4f-1b4210ec7a95.jpg
324 ms
f32e5c5a-80a8-11ed-bb03-438506b8afe8.png
325 ms
pubads_impl.js
153 ms
recaptcha__en.js
408 ms
tracker.gif
285 ms
analytics.min.js
384 ms
58580620
363 ms
apstag.js
270 ms
web-vitals.iife.js
196 ms
10909.jsx
178 ms
web-vitals.iife.js
90 ms
WidgetTemplate2.min.css
37 ms
jquery@3.1.0(jquery.slim.min.js),velocity@1.2.3(velocity.min.js+velocity.ui.min.js)
149 ms
jquery.fireSlider.min.js
36 ms
rad.js
37 ms
css
114 ms
css
137 ms
polyfill.min.js
200 ms
AGSKWxVORjAFN4vlk_Hs2GRrlAKtazKEMaSbGl0UURvnbKfxUyjFddGDFBnHOmS8rzZXdNWzzEgUa5xBK0CRGhrXdg9GNFIk8NyNpjfFeNx2AkWMXklXTBwvmsc9hRUeB3sra3ukYVmXFA==
143 ms
esp.js
419 ms
esp.js
418 ms
uid2SecureSignal.js
213 ms
js
183 ms
js
178 ms
p-uq0GLFySb_d1T.gif
345 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
317 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
318 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
333 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
346 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
344 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
343 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XljLdSL57k.ttf
344 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5XljLdSL57k.ttf
343 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5XljLdSL57k.ttf
342 ms
icomoon.woff
68 ms
AGSKWxXFze-pMVu_-GBKYV4jd9BVOZEsH16rrISix_9VRMueM2EZHAJ4zHsghmS7T-AROeVRwNpvv6bLcF8r-PssNIcPIQOK-iZRl4aUeVPflvvj5D-D2Nynw99ISotQrvZ-VAYAOzhHug==
307 ms
settings
223 ms
870.bundle.6e2976b75e60ab2b2bf8.js
34 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
50 ms
innisfilexaminer.ca 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.
innisfilexaminer.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
innisfilexaminer.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Innisfilexaminer.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 Innisfilexaminer.ca main page’s claimed encoding is iso-8859-1. 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.
innisfilexaminer.ca
Open Graph data is detected on the main page of Innisfilexaminer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: