3.7 sec in total
187 ms
2.6 sec
890 ms
Visit ycteam.ca now to see the best up-to-date YC Team content and also check out these interesting facts you probably never knew about ycteam.ca
Visit ycteam.caWe analyzed Ycteam.ca page load time and found that the first response time was 187 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ycteam.ca performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.5 s
19/100
25%
Value9.4 s
12/100
10%
Value840 ms
34/100
30%
Value0.168
71/100
15%
Value11.3 s
19/100
10%
187 ms
1208 ms
182 ms
190 ms
188 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ycteam.ca, 57% (53 requests) were made to Ycrealty.ca and 29% (27 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Ycrealty.ca.
Page size can be reduced by 1.5 MB (9%)
16.9 MB
15.4 MB
In fact, the total size of Ycteam.ca main page is 16.9 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 16.1 MB which makes up the majority of the site volume.
Potential reduce by 269.8 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 269.8 kB or 87% of the original size.
Potential reduce by 1.1 MB
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. YC Team images are well optimized though.
Potential reduce by 58.9 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 58.9 kB or 15% of the original size.
Potential reduce by 8.2 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. Ycteam.ca needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 16% of the original size.
Number of requests can be reduced by 24 (41%)
59
35
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of YC Team. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
ycteam.ca
187 ms
ycrealty.ca
1208 ms
sbi-styles.min.css
182 ms
sticky-social-media-icons-public.css
190 ms
pagenavi-css.css
188 ms
jquery.min.js
189 ms
jquery-migrate.min.js
132 ms
sticky-social-media-icons-public.js
137 ms
slick.js
38 ms
font-awesome.min.css
49 ms
sticky-icons-display.css
151 ms
scripts.min.js
383 ms
smoothscroll.js
187 ms
es6-promise.auto.min.js
286 ms
api.js
41 ms
recaptcha.js
287 ms
jquery.fitvids.js
287 ms
jquery.mobile.js
287 ms
salvattore.js
288 ms
common.js
288 ms
new-logo.png
206 ms
Neighbourhood_01_11zon-2.jpg
418 ms
blur2.jpg
330 ms
team.jpg
336 ms
Thumbnail-1.png
451 ms
Thumbnail.png
449 ms
Precon-web-Cover-img.png
468 ms
main-image-jpglow.jpg
450 ms
LSQ2-Web-Cover-img_11zon-scaled.jpg
476 ms
Q-Tower-Web-Cover-img_11zon-scaled.jpg
556 ms
6080-Yonge-Web-Cover-img_11zon-1-scaled.jpg
497 ms
Arcadia-District-Web-Cover-img_11zon-scaled.jpg
528 ms
yoon-choi-2-crop.png
496 ms
dennis-tang-2.png
551 ms
mark-lee-1-crop.png
583 ms
hyunji-kim-1-crop-v2.png
556 ms
daniel-lim-1.png
553 ms
jay-kim-2.png
650 ms
david-kim-2.png
622 ms
jenny-lee-1-crop.png
627 ms
%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B7-2023-10-24-142101.png
688 ms
80-1.jpg
636 ms
347-Caboto-Tr-1.jpg
656 ms
950.png
689 ms
115-Blue-Jays-Way-820-1.jpg
696 ms
251-3802-1.jpg
703 ms
251-Jarvis-St-E-3612.jpg
720 ms
lo.png
723 ms
YC-Realty-Horizontal-type3.png
690 ms
S6u9w4BMUTPHh7USSwiPHw.woff
27 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
28 ms
S6u8w4BMUTPHh30AXC-s.woff
22 ms
S6u8w4BMUTPHh30AXC-v.ttf
28 ms
S6uyw4BMUTPHjx4wWA.woff
27 ms
S6uyw4BMUTPHjx4wWw.ttf
28 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
28 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
29 ms
S6u9w4BMUTPHh50XSwiPHw.woff
29 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
54 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff
30 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
54 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtU.woff
56 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf
54 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtU.woff
55 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf
56 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff
56 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
56 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtU.woff
57 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf
57 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff
58 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf
59 ms
modules.ttf
686 ms
MwQ5bhbm2POE2V9BOw.woff
57 ms
MwQ5bhbm2POE2V9BOA.ttf
57 ms
fontawesome-webfont.woff
43 ms
fa-brands-400.woff
689 ms
fa-regular-400.woff
689 ms
fa-solid-900.woff
716 ms
recaptcha__en.js
80 ms
Banner-bravo.png
544 ms
Banner.png
571 ms
anchor
32 ms
styles__ltr.css
3 ms
recaptcha__en.js
9 ms
MiNarUAOgmcBTtb-B9dqJsIEHzGnODmmbX7rqJecvmc.js
61 ms
webworker.js
63 ms
logo_48.png
52 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
18 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
19 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
19 ms
recaptcha__en.js
26 ms
style.min.css
72 ms
style.min.css
69 ms
ycteam.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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ycteam.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
ycteam.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ycteam.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 Ycteam.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.
ycteam.ca
Open Graph description is not detected on the main page of YC Team. 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: