4.1 sec in total
178 ms
3.2 sec
750 ms
Welcome to mlb.com homepage info - get ready to check MLB best content for United States right away, or after learning these important things about mlb.com
Coverage includes audio and video clips, interviews, statistics, schedules and exclusive stories.
Visit mlb.comWe analyzed Mlb.com page load time and found that the first response time was 178 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mlb.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value29.0 s
0/100
25%
Value37.3 s
0/100
10%
Value51,980 ms
0/100
30%
Value0.075
95/100
15%
Value100.4 s
0/100
10%
178 ms
234 ms
276 ms
275 ms
276 ms
Our browser made a total of 204 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Mlb.com, 25% (51 requests) were made to Mlbstatic.com and 23% (47 requests) were made to Img.mlbstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Z.moatads.com.
Page size can be reduced by 666.8 kB (68%)
984.8 kB
318.1 kB
In fact, the total size of Mlb.com main page is 984.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 822.1 kB which makes up the majority of the site volume.
Potential reduce by 663.3 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 663.3 kB or 81% of the original size.
Potential reduce by 1 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. MLB images are well optimized though.
Potential reduce by 3.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.
Number of requests can be reduced by 62 (90%)
69
7
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MLB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
www.mlb.com
178 ms
d90UhUI7dbUGNZqbN2Ef-OJ6X6U.js
234 ms
mlb-okta.js
276 ms
makeTFL.js
275 ms
adobe-client-data-layer.min.js
276 ms
analytics.js
276 ms
VisitorAPI.js
276 ms
at.js
277 ms
AppMeasurement-mlb.js
277 ms
AppMeasurement.js
277 ms
launch-0febec0c5fac.min.js
1353 ms
mlb.css
278 ms
7eae26a6777bacfb.css
263 ms
polyfills-5cd94c89d3acac5f.js
263 ms
webpack-a75b8b662c6acaad.js
263 ms
framework-fc1f2e8247ad02c2.js
263 ms
main-013ed5e937cbafef.js
263 ms
_app-cf0969ebd5e67d9a.js
263 ms
78537f27-42185e0a77dadfff.js
263 ms
952ae657-9bd842404a4da910.js
253 ms
e999873e-563f307a5602f302.js
253 ms
a29ae703-cf98c0f8bbf396d4.js
253 ms
faf0dfaa-e58ba85f1d6ab56d.js
253 ms
9922685e-ef125a69f5cfc779.js
253 ms
9b61e6c5-afd3c196a6ae48d4.js
253 ms
b548615e-77a905354a612119.js
253 ms
2edb282b-b8f4863366339abc.js
252 ms
66dee5eb-1c9ac7fb197a1179.js
253 ms
20ccc6d2-22e02c5c9f239c32.js
253 ms
a6c7d93c-2bff0f5b3ea8d817.js
252 ms
26b4518c-4f50042f86a9d7da.js
249 ms
0ef9dd76-5230562dc221b756.js
250 ms
584-8931ee8ab2f37668.js
251 ms
%5B%5B...path%5D%5D-f0b28a5294ae9194.js
250 ms
_buildManifest.js
250 ms
_ssgManifest.js
250 ms
_middlewareManifest.js
249 ms
mlb-global-properties-mlb-xhp2-mlb-base-palette.css
286 ms
gtm.js
602 ms
gtm.js
878 ms
tags.js
698 ms
mbeluoscu7euistcp9eo.jpg
774 ms
Game_Stories.svg
881 ms
x1wm7rnmlcvih4ppywhs
711 ms
pario21z1cjjyt3c4wgs
711 ms
oeyfjegqhvgv5vvlo1u1
711 ms
qzrwolitxakpyifxcyxi
712 ms
dk2wdjkc0wopt2jmidca
712 ms
agbkctx7qydhjyyeeoyt
711 ms
mwuidrvbe3urgbrnvbrr
712 ms
xyrdkur8juuadoa9vlrg
712 ms
cgjseofu6oaihdpbrzfj
713 ms
lkaplheg2eiinrgcu5un
712 ms
wgi72ec5s7jvn8mjwlqn
713 ms
jwpea56xhv4pm6p312is
713 ms
imfxix7odtes2h5s4il0
713 ms
pfneevpsfsmeve6vda1q
713 ms
lqpvafxqain6jjtblefs
712 ms
zztizixly3e3vbbm3lok
712 ms
dbz2qinmayyzodxkfucs
713 ms
lntpg4edqvsc6eqrdvd0
713 ms
ykclbumwghcdugyrr8rr
713 ms
e8d7v6ocjaqw5qaj5ebv
712 ms
sqw1ouiqc9zqysn6menv
712 ms
eltymtvktwzwirfav1yf
712 ms
g4rsskgd0ire1og8fodj
712 ms
q2lnbs09supvsnpprtch
712 ms
royupoacxuv2dmnqyhry
712 ms
idlqdhpkh0jealhbzv6c
712 ms
xl56vkonzpgaiqx0cqfe
712 ms
kvcgy0ccyxlk2ewkracg
704 ms
m5rsv2quwkorp1zbblur
703 ms
gtlu5odvvlwg1dyoirxf
703 ms
jizzhbqepbcqq8o8vu2f
703 ms
koz8wnq3ohibiheqajzx
704 ms
ui2ilwkrezrvoahiauzz
703 ms
smoqdivhzuusjkeyglhe
703 ms
ohr5urgkilmrjd3kthgw
703 ms
1.svg
341 ms
110.svg
345 ms
111.svg
344 ms
147.svg
345 ms
139.svg
345 ms
141.svg
358 ms
145.svg
358 ms
114.svg
357 ms
116.svg
357 ms
118.svg
357 ms
142.svg
357 ms
117.svg
357 ms
108.svg
357 ms
133.svg
357 ms
136.svg
357 ms
140.svg
357 ms
144.svg
356 ms
146.svg
356 ms
121.svg
357 ms
143.svg
357 ms
120.svg
357 ms
112.svg
356 ms
113.svg
356 ms
158.svg
356 ms
134.svg
356 ms
138.svg
357 ms
109.svg
356 ms
115.svg
356 ms
119.svg
356 ms
135.svg
356 ms
137.svg
348 ms
bgca.svg
347 ms
proxima-nova-bold.woff
160 ms
proxima-nova-extrabold.woff
160 ms
proxima-nova-black.woff
160 ms
proxima-nova-semibold.woff
160 ms
datadog-rum-v4.js
753 ms
proxima-nova-medium.woff
75 ms
proxima-nova-regular.woff
75 ms
proxima-nova-light.woff
75 ms
proxima-nova-thin.woff
75 ms
uwt.js
481 ms
analytics.js
371 ms
fbevents.js
364 ms
sync
498 ms
bat.js
497 ms
scevent.min.js
356 ms
quant.js
286 ms
events.js
353 ms
myh3sikuffzv84xv0fa4
34 ms
ltqufb4h68gkrqmogu03
34 ms
smswc1fljal4hrkmeimy
35 ms
kzpgksexk38xxnntjaw2
34 ms
ai92r37vlz6vuijrjlik
34 ms
dnlrg6gv9l7lew049dzf
33 ms
alkfeztyzyacsaqm84ky
33 ms
rqmsjj0k9evwpswjm87z
33 ms
tqdhtxe4mojqd27tlqc8
33 ms
rrkrh7nj9h5ski6m8zjf
33 ms
jwjtox8o6wbndrlqkdlf
32 ms
MIN-70700.js
339 ms
moatheader.js
1414 ms
mlb.svg
268 ms
chartbeat_mab.js
305 ms
branch-latest.min.js
306 ms
otSDKStub.js
288 ms
otCCPAiab.js
350 ms
iu3
184 ms
adsct
585 ms
adsct
758 ms
pr
48 ms
611 ms
amazon
746 ms
sync
86 ms
map
899 ms
v1
735 ms
partner
82 ms
v2
767 ms
TC-3673-1.gif
607 ms
pixel
798 ms
87e3b067-33e7-4a28-84ad-4aaeb74b4d5a.json
309 ms
dnsfeed
796 ms
location
554 ms
ecm3
195 ms
match
183 ms
ecm3
207 ms
ecm3
223 ms
pixel
133 ms
ecm3
207 ms
ecm3
195 ms
ecm3
186 ms
ecm3
178 ms
ecm3
174 ms
ecm3
148 ms
ecm3
146 ms
ecm3
158 ms
ecm3
157 ms
pixel
129 ms
ecm3
133 ms
ecm3
129 ms
ecm3
127 ms
ecm3
120 ms
ecm3
138 ms
ecm3
136 ms
otBannerSdk.js
63 ms
ecm3
85 ms
ecm3
86 ms
ecm3
82 ms
ecm3
79 ms
ecm3
90 ms
ecm3
88 ms
ecm3
88 ms
ecm3
87 ms
cksync
85 ms
ecm3
83 ms
ecm3
80 ms
ecm3
77 ms
ecm3
76 ms
ecm3
82 ms
ecm3
52 ms
pixel
13 ms
ecm3
43 ms
v2
52 ms
n.js
56 ms
ecm3
11 ms
75 ms
mlb.com 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
Links do not have a discernible name
mlb.com SEO score
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 Mlb.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 Mlb.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.
mlb.com
Open Graph data is detected on the main page of MLB. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: