2.8 sec in total
737 ms
2 sec
76 ms
Click here to check amazing Fantasy Sportsnet content for Canada. Otherwise, check out these important facts you probably never knew about fantasy.sportsnet.ca
Visit fantasy.sportsnet.caWe analyzed Fantasy.sportsnet.ca page load time and found that the first response time was 737 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
fantasy.sportsnet.ca performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value16.2 s
0/100
25%
Value15.8 s
0/100
10%
Value3,470 ms
2/100
30%
Value0.004
100/100
15%
Value33.9 s
0/100
10%
737 ms
69 ms
43 ms
54 ms
61 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fantasy.sportsnet.ca, 10% (16 requests) were made to Use.typekit.net and 3% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (737 ms) relates to the external source Sportsnet.ca.
Page size can be reduced by 1.4 MB (41%)
3.4 MB
2.0 MB
In fact, the total size of Fantasy.sportsnet.ca main page is 3.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. Only a small number of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 314.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. 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 314.7 kB or 84% of the original size.
Potential reduce by 210.0 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. Obviously, Fantasy Sportsnet needs image optimization as it can save up to 210.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 774 B
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 898.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. Fantasy.sportsnet.ca needs all CSS files to be minified and compressed as it can save up to 898.5 kB or 81% of the original size.
Number of requests can be reduced by 134 (95%)
141
7
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fantasy Sportsnet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 111 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
737 ms
bqe3qao.css
69 ms
react.production.min.js
43 ms
react-dom.production.min.js
54 ms
axios.min.js
61 ms
style.min.css
42 ms
style.min.css
52 ms
style.min.css
49 ms
style.min.css
48 ms
style.min.css
49 ms
blocks.style.build.css
48 ms
swp-style.css
86 ms
w3.css
177 ms
qrs8kfa.css
184 ms
css
63 ms
rdm-daac-notice-public.css
61 ms
rdm-dynamic-tag-management-public.css
58 ms
rdm-solr-form.css
59 ms
ump.css
59 ms
style.css
61 ms
style-et-prefcentre.css
66 ms
bootstrap.min.css
67 ms
style.css
65 ms
global.css
72 ms
style.css
79 ms
wp-polyfill-inert.min.js
74 ms
regenerator-runtime.min.js
75 ms
wp-polyfill.min.js
73 ms
autop.min.js
82 ms
blob.min.js
83 ms
block-serialization-default-parser.min.js
83 ms
react.min.js
84 ms
hooks.min.js
87 ms
deprecated.min.js
169 ms
dom.min.js
90 ms
react-dom.min.js
166 ms
escape-html.min.js
89 ms
element.min.js
88 ms
is-shallow-equal.min.js
168 ms
i18n.min.js
167 ms
keycodes.min.js
166 ms
priority-queue.min.js
166 ms
compose.min.js
173 ms
modernizr.min.js
47 ms
detectizr.min.js
45 ms
launch-cad84d3ce4c4.min.js
50 ms
utilityx.js
235 ms
utility.js
268 ms
common_footer.s_code.js
172 ms
vf-v2.js
46 ms
brightcove.css
168 ms
tickerv2.css
143 ms
private-apis.min.js
135 ms
redux-routine.min.js
135 ms
data.min.js
136 ms
html-entities.min.js
168 ms
shortcode.min.js
167 ms
blocks.min.js
164 ms
dom-ready.min.js
155 ms
a11y.min.js
155 ms
url.min.js
155 ms
api-fetch.min.js
161 ms
p.css
35 ms
lodash.min.js
156 ms
moment.min.js
154 ms
date.min.js
154 ms
primitives.min.js
168 ms
rich-text.min.js
174 ms
warning.min.js
172 ms
components.min.js
189 ms
keyboard-shortcuts.min.js
167 ms
notices.min.js
166 ms
preferences-persistence.min.js
165 ms
preferences.min.js
172 ms
style-engine.min.js
171 ms
token-list.min.js
170 ms
wordcount.min.js
169 ms
block-editor.min.js
186 ms
core-data.min.js
176 ms
media-utils.min.js
176 ms
nhl_logo_2x.png
84 ms
reusable-blocks.min.js
98 ms
server-side-render.min.js
99 ms
editor.min.js
104 ms
swp-onload.js
104 ms
helper.js
105 ms
swp-api-caller.js
100 ms
jquery-1.12.4-wp.js
105 ms
jquery-migrate-1.4.1-wp.js
114 ms
rdm-daac-notice-public.js
118 ms
statelet.js
116 ms
ump-bootstrap-modal.js
156 ms
p.css
4 ms
utils.min.js
157 ms
janrain-init-et-flow.js
126 ms
ump-webfont.js
133 ms
newsletters-unsubscribe.js
136 ms
public-et-flow.js
138 ms
ump-viafoura.js
134 ms
jquery.mobile.custom.js
129 ms
jquery.noconflict_disable.js
130 ms
snet.global.js
134 ms
jquery.cookie.js
115 ms
snet.breakpoint_watcher.js
114 ms
nav.js
126 ms
footer.js
120 ms
exContentAjax.min.js
115 ms
rdm-solr-form.js
115 ms
core.min.js
116 ms
client.js
116 ms
bootstrap-typeahead.js
108 ms
url.min.js
110 ms
autocomplete_solr.js
116 ms
loadingoverlay.min.js
111 ms
front-end.js
101 ms
jquery.snet.SNPlayer.js
101 ms
snet.SNPlayerUtil.js
102 ms
snet.SNPlayerLazyLoadUtil.js
101 ms
snet.SNPlayerModalUtil.js
101 ms
snet.scoresDatav2.js
97 ms
snet.scoresDatav2.utils.js
97 ms
snet.tickerv2.tickercarousel.js
103 ms
snet.tickerv2.js
103 ms
stickyfill.js
88 ms
snet.sticky.js
279 ms
jquery.snet.alerts.js
84 ms
all-libs.js
45 ms
snet.header.init.js
235 ms
snet.footer.init.js
235 ms
snet.minifymenu.js
234 ms
snet.nav.js
229 ms
webfont.js
519 ms
snet.analytics_events_tracking.js
223 ms
snet.passive_display_adblock.js
519 ms
close-btn.svg
517 ms
The-Fantasy-Show-Board-No-Dominos-Logo.jpeg
517 ms
Image-3.png
716 ms
Image-4.png
711 ms
fbevents.js
643 ms
uwt.js
706 ms
scevent.min.js
707 ms
YGTLA-87MWN-Z627Q-C5USJ-TUKRL
639 ms
d
487 ms
d
492 ms
d
605 ms
d
582 ms
d
491 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
471 ms
d
367 ms
d
405 ms
d
405 ms
d
467 ms
d
168 ms
d
167 ms
d
168 ms
d
171 ms
d
171 ms
fantasy.sportsnet.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
fantasy.sportsnet.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fantasy.sportsnet.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fantasy.sportsnet.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 Fantasy.sportsnet.ca 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.
fantasy.sportsnet.ca
Open Graph description is not detected on the main page of Fantasy Sportsnet. 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: