2.2 sec in total
105 ms
1.7 sec
353 ms
Welcome to trythey.com homepage info - get ready to check Try The Y best content right away, or after learning these important things about trythey.com
Visit trythey.comWe analyzed Trythey.com page load time and found that the first response time was 105 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.
trythey.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value11.2 s
0/100
25%
Value7.7 s
24/100
10%
Value1,400 ms
16/100
30%
Value0.247
50/100
15%
Value17.4 s
4/100
10%
105 ms
9 ms
13 ms
14 ms
16 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Trythey.com, 28% (36 requests) were made to Ymcamidtn.org and 9% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (415 ms) relates to the external source Facebook.com.
Page size can be reduced by 378.1 kB (17%)
2.2 MB
1.8 MB
In fact, the total size of Trythey.com main page is 2.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. 85% 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 47.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. 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 47.4 kB or 78% of the original size.
Potential reduce by 32.3 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. Try The Y images are well optimized though.
Potential reduce by 254.2 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 254.2 kB or 50% of the original size.
Potential reduce by 44.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. Trythey.com needs all CSS files to be minified and compressed as it can save up to 44.2 kB or 76% of the original size.
Number of requests can be reduced by 74 (61%)
121
47
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Try The Y. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
ymcamidtn.org
105 ms
ModuleStyleSheets.css
9 ms
royalslider.css
13 ms
rs-default.css
14 ms
override.css
16 ms
nav.css
15 ms
jquery.dropdown.css
17 ms
less-1.4.1.min.js
18 ms
jquery-1.10.2.min.js
201 ms
jquery.easing-1.3.js
17 ms
jquery-1.8.3.min.js
199 ms
jquery.royalslider.min.js
200 ms
Box.css
199 ms
Java_Box.js
225 ms
element.js
245 ms
conversion.js
243 ms
hellobar.js
242 ms
gtm.js
29 ms
analytics.js
25 ms
sdk.js
22 ms
header-gradient.png
15 ms
logo-statement-blue.svg
17 ms
nav-sub-bg-light.png
15 ms
slider-meal-madness.jpg
91 ms
slider-free-health.jpg
100 ms
slider-2016-day-camp.jpg
99 ms
slider-swim-lessons.jpg
89 ms
slider-work-for-y.jpg
86 ms
mobile-ad.png
83 ms
home-promo-enews-v1.png
84 ms
home-promo-online-account-mgmt-v1.png
86 ms
icon-location.svg
85 ms
icon-plussign-white.svg
92 ms
icon-calendar-white.svg
91 ms
icon-check-white.svg
90 ms
icon-heart-white.svg
88 ms
footer-bg.png
94 ms
social-facebook.png
93 ms
social-twitter.png
93 ms
social-youtube.png
93 ms
translateelement.css
120 ms
main.js
128 ms
collect
53 ms
257 ms
dc.js
85 ms
analytics.js
104 ms
conversion_async.js
74 ms
collect
110 ms
collect
116 ms
107 ms
xd_arbiter.php
86 ms
xd_arbiter.php
99 ms
72513_113059.js
83 ms
72513_109286.js
82 ms
rs-default.png
53 ms
preloader-white.gif
28 ms
element_main.js
65 ms
34 ms
114 ms
111 ms
translate_24dp.png
57 ms
l
43 ms
cleardot.gif
20 ms
like_box.php
415 ms
te_ctrl3.gif
11 ms
hellobar-72513-109286.js
8 ms
hellobar-72513-113059.js
9 ms
hDvwL1_H7g-.css
50 ms
56WNbrUYLbL.css
44 ms
yZ--Yu0PDbV.css
43 ms
GN27K_co9Wc.css
59 ms
QD6_ejUFoCN.css
51 ms
xxJgcoj8mOR.css
63 ms
8T0HA74GVFW.css
60 ms
q68gy-v_YMF.js
61 ms
FJmpeSpHpjS.js
94 ms
0wM5s1Khldu.js
91 ms
1bNoFZUdlYZ.js
93 ms
njO1TPvGzoR.js
92 ms
OloiM1PZafe.js
123 ms
LTv6ZK-5zxz.js
114 ms
1FCa-btixu2.js
109 ms
Oagsvfb4VWi.js
108 ms
pObvZSrFc_4.js
110 ms
Kt4tkgSRvHH.js
106 ms
H3EKDTObx05.js
109 ms
eR-qA8bp1RM.js
110 ms
1QuX41zDRrx.js
111 ms
7BE0CZr3HTs.js
111 ms
irRqrSRO8Uu.js
112 ms
-7JBD_ybv4q.js
174 ms
88bxMY9LZAz.js
112 ms
IjqSyiwKeaX.js
112 ms
12003238_10153639642099451_8030990642906486001_n.jpg
182 ms
safe_image.php
180 ms
rBxSIHk4zIe.js
45 ms
n6VgtouijQL.js
42 ms
pQrUxxo5oQp.js
43 ms
_UYztdBNTjs.js
42 ms
css;base64,
12 ms
gbh6x73jsGH.css
44 ms
safe_image.php
132 ms
safe_image.php
129 ms
safe_image.php
134 ms
safe_image.php
134 ms
1653865_10153733061314451_7339677531492537871_n.jpg
125 ms
14076_1374695432851480_5314586939286615566_n.jpg
126 ms
12742821_10153236701545881_8575606534254043147_n.jpg
119 ms
12806120_981887021860820_4264727766133844319_n.jpg
118 ms
11206097_10205833111219624_3115861363044469098_n.jpg
125 ms
10292484_1993395974219209_8896055734197897777_n.jpg
126 ms
12376299_717029255066354_6807346629457057006_n.jpg
238 ms
12495259_981270738594820_7728285397488755543_n.jpg
132 ms
944092_195446877493457_9209152037226919337_n.jpg
134 ms
10981643_10206536957132155_3438890022060877677_n.jpg
135 ms
10580062_10208864940643443_4674535452313233725_n.jpg
143 ms
wL6VQj7Ab77.png
39 ms
s7jcwEQH7Sx.png
124 ms
QDwYpIaRyfG.png
124 ms
bNvHN6v1NeH.png
123 ms
t-wz8gw1xG1.png
123 ms
K00K-UgnsKu.png
128 ms
gxbPuQdXIZP.png
125 ms
b8XhdWI9eAN.js
66 ms
JNPO3NqYHEj.png
29 ms
QijIVO3ZIrO.png
30 ms
I6-MnjEovm5.js
5 ms
trythey.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
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
ARIA IDs are not unique
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
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
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.
trythey.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
trythey.com 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trythey.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Trythey.com 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.
trythey.com
Open Graph description is not detected on the main page of Try The Y. 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: