1.4 sec in total
140 ms
902 ms
398 ms
Click here to check amazing Yankees content for United States. Otherwise, check out these important facts you probably never knew about yankees.com
The official website of the New York Yankees with the most up-to-date information on scores, schedule, stats, tickets, and team news.
Visit yankees.comWe analyzed Yankees.com page load time and found that the first response time was 140 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
yankees.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value62.4 s
0/100
25%
Value44.6 s
0/100
10%
Value22,810 ms
0/100
30%
Value0
100/100
15%
Value70.3 s
0/100
10%
140 ms
39 ms
86 ms
77 ms
79 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yankees.com, 27% (26 requests) were made to Builds.mlbstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (370 ms) relates to the external source Builds.mlbstatic.com.
Page size can be reduced by 883.5 kB (59%)
1.5 MB
605.0 kB
In fact, the total size of Yankees.com main page is 1.5 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. HTML takes 1.1 MB which makes up the majority of the site volume.
Potential reduce by 878.0 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 878.0 kB or 82% 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. Yankees images are well optimized though.
Potential reduce by 5.3 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 226 B
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. Yankees.com has all CSS files already compressed.
Number of requests can be reduced by 41 (48%)
86
45
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yankees. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and as a result speed up the page load time.
yankees
140 ms
Ixnon6Nk9xou2jR8_m5H0h8H4q4.js
39 ms
mlb-okta.js
86 ms
makeTFL.js
77 ms
VisitorAPI.js
79 ms
at.js
79 ms
AppMeasurement-mlb.js
79 ms
AppMeasurement.js
78 ms
adobe-client-data-layer.min.js
81 ms
launch-0febec0c5fac.min.js
76 ms
mlb.css
81 ms
7eae26a6777bacfb.css
79 ms
polyfills-5cd94c89d3acac5f.js
179 ms
webpack-906465828da41bc3.js
82 ms
framework-fc1f2e8247ad02c2.js
197 ms
main-013ed5e937cbafef.js
168 ms
_app-4d25c2dcfbbfd04a.js
209 ms
78537f27-42185e0a77dadfff.js
196 ms
952ae657-9bd842404a4da910.js
219 ms
e999873e-563f307a5602f302.js
196 ms
a29ae703-cf98c0f8bbf396d4.js
196 ms
faf0dfaa-e58ba85f1d6ab56d.js
196 ms
9922685e-ef125a69f5cfc779.js
208 ms
9b61e6c5-afd3c196a6ae48d4.js
204 ms
b548615e-77a905354a612119.js
204 ms
2edb282b-b8f4863366339abc.js
204 ms
66dee5eb-1c9ac7fb197a1179.js
207 ms
20ccc6d2-22e02c5c9f239c32.js
204 ms
a6c7d93c-2bff0f5b3ea8d817.js
307 ms
26b4518c-4f50042f86a9d7da.js
310 ms
0ef9dd76-5230562dc221b756.js
310 ms
96459ee1-323f8a7fca3a349a.js
309 ms
557-89c8527f71fa00cf.js
370 ms
%5B%5B...path%5D%5D-45a7462e0b1f67e9.js
345 ms
_buildManifest.js
349 ms
_ssgManifest.js
349 ms
_middlewareManifest.js
359 ms
t147-global-properties-t147-background-skins-t147-base-palette.css
74 ms
id
267 ms
gtm.js
299 ms
tags.js
364 ms
t147_url_logo.svg
279 ms
t147_bodyBackgroundSkin1.jpg
316 ms
147.svg
192 ms
110.svg
191 ms
111.svg
190 ms
147.svg
199 ms
139.svg
190 ms
141.svg
187 ms
145.svg
208 ms
114.svg
203 ms
116.svg
202 ms
118.svg
203 ms
142.svg
201 ms
117.svg
209 ms
108.svg
241 ms
133.svg
241 ms
136.svg
238 ms
140.svg
240 ms
144.svg
246 ms
146.svg
245 ms
121.svg
310 ms
143.svg
309 ms
120.svg
310 ms
112.svg
309 ms
113.svg
312 ms
158.svg
311 ms
134.svg
320 ms
138.svg
322 ms
109.svg
323 ms
115.svg
323 ms
119.svg
320 ms
135.svg
321 ms
137.svg
338 ms
117.svg
339 ms
147.svg
342 ms
1.svg
341 ms
bgca.svg
339 ms
dest5.html
144 ms
id
150 ms
proxima-nova-bold.woff
165 ms
proxima-nova-extrabold.woff
168 ms
proxima-nova-black.woff
230 ms
proxima-nova-semibold.woff
167 ms
proxima-nova-medium.woff
230 ms
proxima-nova-regular.woff
167 ms
proxima-nova-light.woff
241 ms
proxima-nova-thin.woff
242 ms
datadog-rum.js
137 ms
gtm.js
145 ms
gtm.js
144 ms
otSDKStub.js
216 ms
otCCPAiab.js
216 ms
ibs:dpid=411&dpuuid=ZjxaeAAAAJxJeQN-
75 ms
122 ms
yankees.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
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
<frame> or <iframe> elements do not have a title
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
yankees.com 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
yankees.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yankees.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 Yankees.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.
yankees.com
Open Graph data is detected on the main page of Yankees. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: