1.9 sec in total
145 ms
1.2 sec
503 ms
Visit wrigleyfield.com now to see the best up-to-date Wrigley Field content and also check out these interesting facts you probably never knew about wrigleyfield.com
Welcome to the home of the 1060 Project to restore Wrigley Field.
Visit wrigleyfield.comWe analyzed Wrigleyfield.com page load time and found that the first response time was 145 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
wrigleyfield.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value31.5 s
0/100
25%
Value27.0 s
0/100
10%
Value4,330 ms
1/100
30%
Value0.038
100/100
15%
Value43.1 s
0/100
10%
145 ms
196 ms
106 ms
27 ms
29 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wrigleyfield.com, 60% (81 requests) were made to Chicago.cubs.mlb.com and 5% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (432 ms) relates to the external source Chicago.cubs.mlb.com.
Page size can be reduced by 977.0 kB (20%)
4.8 MB
3.8 MB
In fact, the total size of Wrigleyfield.com main page is 4.8 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. 80% 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 3.5 MB which makes up the majority of the site volume.
Potential reduce by 39.1 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 39.1 kB or 74% of the original size.
Potential reduce by 11.8 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. Wrigley Field images are well optimized though.
Potential reduce by 685.5 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 685.5 kB or 73% of the original size.
Potential reduce by 240.6 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. Wrigleyfield.com needs all CSS files to be minified and compressed as it can save up to 240.6 kB or 83% of the original size.
Number of requests can be reduced by 98 (82%)
120
22
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wrigley Field. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
wrigleyfield.com
145 ms
196 ms
css
106 ms
global.css
27 ms
chc.css
29 ms
jquery-ui-1.8.custom.css
31 ms
jquery-ui-1.8.8.custom.css
35 ms
mlb_header_account_2012.css
33 ms
facebook_button.css
40 ms
bam.buttons.css
38 ms
main.css
63 ms
bam.css.jsp
39 ms
global2.css
39 ms
bootstrap.min.css
42 ms
font-awesome.min.css
50 ms
jquery.bxslider.css
52 ms
jquery.fancybox.css
69 ms
main.css
65 ms
custom.css
68 ms
jquery.js
49 ms
jquery.etc.js
50 ms
jquery.enable.js
48 ms
jquery.sajax.min.js
50 ms
jquery.template.min.js
51 ms
jquery.validate.min.js
52 ms
jquery-ui.1.8.8.bamcore.min.js
52 ms
jquery.ui.autocomplete.min.js
53 ms
jquery.ui.autocomplete.html.js
53 ms
jquery.ui.dialog.min.js
54 ms
flashobject.js
54 ms
global.js
54 ms
legacy.js
54 ms
playMedia.js
54 ms
bam.js
54 ms
jsloader.min.js
59 ms
required.js
61 ms
bam.media.js
60 ms
mlb_player.js
61 ms
external_players.js
60 ms
css
159 ms
css
161 ms
bk-coretag.js
159 ms
main.js
43 ms
dc_ads.js
56 ms
json_source_autocomplete.js
55 ms
registrationServiceUtils_client.js
56 ms
identityPointService_client.js
54 ms
UserAccountStatus.js
51 ms
bam.session.js
48 ms
bam.xd.js
49 ms
bam.fbconnect.js
48 ms
bam.opengraph.js
47 ms
mlb_fbconnect.js
48 ms
myaccountmini.js
35 ms
modernizr.js
125 ms
jquery.bxslider.min.js
126 ms
mlbamscv2.js
36 ms
bam.tracking.js
33 ms
bluekai.js
34 ms
form_validation.js
32 ms
form_validation_vDate.js
165 ms
form_validation_vAge.jsp
165 ms
retina.min.js
116 ms
jquery.fancybox.pack.js
179 ms
jquery.lazyload.min.js
172 ms
jquery.easyListSplitter.js
170 ms
events.js
170 ms
custom.js
170 ms
rta.js
84 ms
gtm.js
64 ms
hdr_en_inner_chc.png
310 ms
cubs_logo_mobile.png
142 ms
cubs_logo.png
143 ms
mediawall_marquee.jpg
297 ms
mediawall_construction.jpg
299 ms
mediawall_groundbreaking2.jpg
182 ms
mediawall_fan_benefits.jpg
342 ms
chicago_benefits.jpg
256 ms
job_creation.jpg
184 ms
fan_benefits.jpg
294 ms
neighborhood_benefits.jpg
319 ms
responsible_preservation.jpg
325 ms
neighborhood_development.jpg
389 ms
message.json
308 ms
socialmedia_cover.jpg
432 ms
facebook.png
363 ms
google.png
381 ms
twitter.png
426 ms
UyYrYy3ltEffJV9QueSi4VLE0juxe_YrR4_5kH0wfhI.ttf
162 ms
Q_pTky3Sc3ubRibGToTAYsLoeaHq4xHkvX1Lp5aKUY8.ttf
162 ms
bx_loader.gif
308 ms
14633
40 ms
conversion_async.js
77 ms
fbevents.js
19 ms
com-chicub.netmng.com
124 ms
bat.js
203 ms
aquant.js
84 ms
d1q9pbwh58f7h5.cloudfront.net
102 ms
moatcontent.js
124 ms
0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf
41 ms
G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf
71 ms
bH7276GfdCjMjApa_dkG6SZ2oysoEQEeKwjgmXLRnTc.ttf
82 ms
lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf
82 ms
HqHm7BVC_nzzTui2lzQTDSZ2oysoEQEeKwjgmXLRnTc.ttf
99 ms
6ec61f10-00ea-4ffd-a36b-26e2577a83f1-3.woff
211 ms
fontawesome-webfont.woff
273 ms
166 ms
91 ms
pixel;r=1500064674;a=p-dKkbRjc2QetUw;orderid=;revenue=;labels=_fp.event.Default;fpan=1;fpa=P0-756532434-1458485092373;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458485092373;tzo=-180;ref=;url=http%3A%2F%2Fchicago.cubs.mlb.com%2Fchc%2Frestore-wrigley%2F;ogl=title.Welcome%2Curl.http%3A%2F%2Fchicago%252Ecubs%252Emlb%252Ecom%2Fchc%2Frestore-wrigley%2F%2Cimage.http%3A%2F%2Fchicago%252Ecubs%252Emlb%252Ecom%2Fmlb%2Fimages%2Fteam_logos%2Fsocial_media%2Fog_1200x630_image%2Ctype.website%2Csite_name.Chicago%20Cubs
22 ms
com-chicub.netmng.com
61 ms
99 ms
pixel
73 ms
rtset
63 ms
Pug
73 ms
rum
54 ms
13209
30 ms
78 ms
match.aspx
63 ms
12 ms
sync
48 ms
u.php
74 ms
tap.php
28 ms
mapuser
39 ms
r2
29 ms
merge
30 ms
33 ms
rum
36 ms
sd
30 ms
bounce
31 ms
382706.gif
42 ms
26 ms
pixel.gif
21 ms
lr.gif
4 ms
23 ms
20 ms
dlxdata.netmng.com
103 ms
wrigleyfield.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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
wrigleyfield.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wrigleyfield.com 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
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 Wrigleyfield.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 Wrigleyfield.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.
wrigleyfield.com
Open Graph description is not detected on the main page of Wrigley Field. 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: