4.8 sec in total
27 ms
2.4 sec
2.4 sec
Welcome to news.therecord.com homepage info - get ready to check News Therecord best content for Canada right away, or after learning these important things about news.therecord.com
Visit news.therecord.comWe analyzed News.therecord.com page load time and found that the first response time was 27 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
news.therecord.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value6.3 s
10/100
25%
Value10.3 s
8/100
10%
Value4,750 ms
0/100
30%
Value0
100/100
15%
Value32.8 s
0/100
10%
27 ms
187 ms
66 ms
71 ms
65 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original News.therecord.com, 48% (49 requests) were made to Bloximages.chicago2.vip.townnews.com and 7% (7 requests) were made to Googletagmanager.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 548.6 kB (35%)
1.6 MB
1.0 MB
In fact, the total size of News.therecord.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. 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 677.9 kB which makes up the majority of the site volume.
Potential reduce by 480.7 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 96.9 kB, which is 18% 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 480.7 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. News Therecord images are well optimized though.
Potential reduce by 56.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. This website has mostly compressed JavaScripts.
Potential reduce by 11.5 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. News.therecord.com needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 19% of the original size.
Number of requests can be reduced by 58 (61%)
95
37
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of News Therecord. 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 8 to 1 for CSS and as a result speed up the page load time.
news.therecord.com
27 ms
www.therecord.com
187 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
66 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
71 ms
oovvuu.css
65 ms
flex-utility-promo-designer.a27bf5e332f0dd667184ad38b7bf1638.css
76 ms
access.d7adebba498598b0ec2c.js
100 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
81 ms
user.js
144 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
77 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
78 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
77 ms
application.3c64d611e594b45dd35b935162e79d85.js
92 ms
polyfill.min.js
1082 ms
footer.nav.js
99 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
98 ms
gpt.js
174 ms
18488.js
107 ms
liftigniter.min.js
97 ms
promo_popup.min.js
100 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
96 ms
tracking.js
139 ms
save.asset.js
96 ms
index.js
72 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
111 ms
amp-iframe-0.1.js
74 ms
launch-9387fe3a1e9f.min.js
74 ms
css2
95 ms
tracker.js
138 ms
get.js
70 ms
newsletter-helper.min.js
75 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
71 ms
sticky-kit.cd42d35abf643b0a78798fe03bf6bc83.js
74 ms
tnt.regions.b44801b45845a81b995eeaad12f4f276.js
73 ms
gtm.js
59 ms
analytics.js
19 ms
gtm.js
63 ms
gtm.js
33 ms
publisher:getClientId
194 ms
destination
30 ms
collect
14 ms
collect
26 ms
apstag.js
117 ms
channels.cgi
232 ms
gtm.js
179 ms
a0e8d788-2006-11ee-9bfc-e39eaba5e978.png
174 ms
6f4f885e-c992-11ed-b48d-47279ee70221.png
79 ms
00ce6d10-200d-11ee-94a1-eb80dd45a33e.png
80 ms
663aa46ca422c.image.jpg
176 ms
663aa46ca422c.image.jpg
173 ms
6639298a00703.image.jpg
173 ms
663a5678d1987.image.jpg
173 ms
b2ed63c8-eab7-11ee-9229-8f1c8842a377.jpg
223 ms
0a9fd008-a1c4-11ed-9069-7f59f036cdd7.b74b456c24d2454d595a42a31af60335.png
221 ms
e9b6ea1e-a2b0-11ed-9e2e-2f91c35efa10.3e2ca2c5fd44cb49ac4ab7f736c66f95.png
220 ms
a6ec9054-9d00-11ed-9bcc-93f249c8efbd.e682996287e5c0adacf85bc8b447dabf.png
221 ms
663a17b3941a7.image.jpg
220 ms
6635576465588.image.jpg
220 ms
6635316d28e8e.image.jpg
260 ms
663a97641a6be.image.jpg
260 ms
65b2d937136a3.image.jpg
260 ms
663a034c2b5c9.image.jpg
261 ms
662872925b4e5.image.jpg
260 ms
661ea5b10b4a4.image.jpg
260 ms
661d539b54b9c.image.jpg
275 ms
662bf3575e70d.image.jpg
275 ms
662c058c96bfe.image.jpg
275 ms
663904696ded4.image.jpg
275 ms
658c44f4b8f7d.image.jpg
275 ms
662c234208f3d.image.jpg
276 ms
53bc41e4-c371-11ed-b48d-4f8c3261ff96.png
281 ms
todays-paper.png
280 ms
app-store.svg
281 ms
google-play.svg
275 ms
pubads_impl.js
43 ms
tracker.gif
129 ms
apstag.js
170 ms
analytics.min.js
104 ms
58580620
154 ms
web-vitals.iife.js
55 ms
web-vitals.iife.js
20 ms
10913.jsx
137 ms
AGSKWxUTR2Y1KuvnRnvDIMM1gt2epF93kdzJs0hSXSWAGpRj6TMvW0qo3Vcgo4nl51gzanUxx9f8zeD9s0QgtGL8bJD43K63LtPFkpyW3bVhzd5OAI6qe_rTo9ELyl0sB-S73vK_9uCY8A==
102 ms
esp.js
152 ms
esp.js
149 ms
uid2SecureSignal.js
152 ms
polyfill.min.js
169 ms
WidgetTemplate2.min.css
96 ms
jquery@3.1.0(jquery.slim.min.js),velocity@1.2.3(velocity.min.js+velocity.ui.min.js)
274 ms
jquery.fireSlider.min.js
135 ms
rad.js
136 ms
js
148 ms
js
230 ms
css
81 ms
css
176 ms
AGSKWxWtw5M-FxXrvwqGIBL06G0algVN5AzUthzRUhTwcNRwIrdsbO1aP2gQ_UkGU-gBUN1sMVTecUnvIq7nrRizCdW5nAdRIKU0ni1lRoPA4Uthy_8EdqVQxu6_zr9mLoW4OksMbXcAmw==
168 ms
settings
100 ms
p-uq0GLFySb_d1T.gif
198 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
77 ms
icomoon.woff
29 ms
870.bundle.6e2976b75e60ab2b2bf8.js
48 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
48 ms
news.therecord.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
[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
Image elements do not have [alt] attributes
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
news.therecord.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
news.therecord.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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise News.therecord.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 News.therecord.com 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.
news.therecord.com
Open Graph description is not detected on the main page of News Therecord. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: