4.9 sec in total
36 ms
2.2 sec
2.7 sec
Click here to check amazing Parentcentral content. Otherwise, check out these important facts you probably never knew about parentcentral.ca
Make the best of life in Toronto, including food, fashion, travel, health, homes & tech at thestar.com.
Visit parentcentral.caWe analyzed Parentcentral.ca page load time and found that the first response time was 36 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
parentcentral.ca performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value10.0 s
0/100
25%
Value9.9 s
10/100
10%
Value4,040 ms
1/100
30%
Value0.014
100/100
15%
Value30.5 s
0/100
10%
36 ms
113 ms
117 ms
162 ms
177 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Parentcentral.ca, 36% (27 requests) were made to Bloximages.chicago2.vip.townnews.com and 9% (7 requests) were made to Thestar.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 520.3 kB (38%)
1.4 MB
850.7 kB
In fact, the total size of Parentcentral.ca main page is 1.4 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. 75% 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 762.3 kB which makes up the majority of the site volume.
Potential reduce by 483.4 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 90.2 kB, which is 17% 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 483.4 kB or 89% of the original size.
Potential reduce by 0 B
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. Parentcentral images are well optimized though.
Potential reduce by 25.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. This website has mostly compressed JavaScripts.
Potential reduce by 11.1 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. Parentcentral.ca needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 19% of the original size.
Number of requests can be reduced by 58 (83%)
70
12
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Parentcentral. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
parentcentral.ca
36 ms
parent.html
113 ms
117 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
162 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
177 ms
oovvuu.css
170 ms
flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css
159 ms
access.d7adebba498598b0ec2c.js
130 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
153 ms
user.js
168 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
216 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
170 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
171 ms
application.3c64d611e594b45dd35b935162e79d85.js
224 ms
polyfill.min.js
1053 ms
tag
145 ms
thestar-sdk.js
144 ms
edition-selector.js
212 ms
footer.nav.js
225 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
231 ms
gpt.js
235 ms
18488.js
225 ms
alertbar.js
225 ms
promo_popup.min.js
228 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
225 ms
tracking.js
211 ms
save.asset.js
226 ms
index.js
139 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
228 ms
amp-iframe-0.1.js
139 ms
client
221 ms
swg.js
141 ms
launch-9387fe3a1e9f.min.js
137 ms
css2
151 ms
tracker.js
217 ms
newsletter-helper.min.js
172 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
172 ms
sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js
171 ms
tnt.regions.b44801b45845a81b995eeaad12f4f276.js
171 ms
tag
24 ms
gtm.js
65 ms
analytics.js
19 ms
gtm.js
30 ms
gtm.js
51 ms
publisher:getClientId
111 ms
destination
28 ms
collect
97 ms
collect
109 ms
apstag.js
142 ms
channels.cgi
444 ms
gtm.js
167 ms
31c48758-8d44-11ed-8c30-0bcb8697ec11.png
86 ms
30f06842-8d44-11ed-8c25-c7d72135c77a.png
86 ms
2faeee7c-8d44-11ed-8c18-eb5483a10695.png
85 ms
todays-paper.png
81 ms
app-store.svg
84 ms
google-play.svg
86 ms
pubads_impl.js
49 ms
tracker.gif
115 ms
analytics.min.js
93 ms
58580620
286 ms
web-vitals.iife.js
164 ms
polyfill.min.js
84 ms
web-vitals.iife.js
57 ms
js
126 ms
js
117 ms
settings
230 ms
AGSKWxUjpCjeOBphbQN4d2XHnEB7TkaYxDZ6NT3eJP6nfiaE2JGLrxIUrkBi8Hgm_31qWyv1O2Eg6mUJqJsjx4B4A1QqOC1LU_aUFAAMijBTHeaqsV2poArx45LOyQcT_AEdqhX99Q12tA==
253 ms
esp.js
264 ms
esp.js
256 ms
uid2SecureSignal.js
245 ms
870.bundle.6e2976b75e60ab2b2bf8.js
14 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
16 ms
AGSKWxWv0IyHFU_rnCYhUCCqTG6ZiDMJzdc35i-Lu1n2RjC7kwbwjPSaXkrrN5p96i55BqNEBSuIJEWYDM6JrRof8J-9Ui_vwq0F9D_HC3JBF1Oqlof5jpE8bQ82HZ0I3t1NuvZcEaU7eg==
37 ms
ajs-destination.bundle.ed53a26b6edc80c65d73.js
6 ms
schemaFilter.bundle.5c2661f67b4b71a6d9bd.js
2 ms
parentcentral.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
[aria-*] attributes do not match their roles
[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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
parentcentral.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
parentcentral.ca SEO score
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 Parentcentral.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 Parentcentral.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.
parentcentral.ca
Open Graph data is detected on the main page of Parentcentral. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: