1.7 sec in total
202 ms
1.3 sec
113 ms
Welcome to stats.boston.com homepage info - get ready to check Stats Boston best content for United States right away, or after learning these important things about stats.boston.com
Visit stats.boston.comWe analyzed Stats.boston.com page load time and found that the first response time was 202 ms and then it took 1.5 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.
stats.boston.com performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value3.2 s
73/100
25%
Value8.8 s
16/100
10%
Value1,460 ms
14/100
30%
Value0
100/100
15%
Value18.1 s
3/100
10%
202 ms
43 ms
29 ms
19 ms
6 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Stats.boston.com, 12% (14 requests) were made to Us-u.openx.net and 10% (11 requests) were made to Ox-d.boston.servedbyopenx.com. The less responsive or slowest element that took the longest time to load (546 ms) relates to the external source Ox-d.boston.servedbyopenx.com.
Page size can be reduced by 737.8 kB (71%)
1.0 MB
306.3 kB
In fact, the total size of Stats.boston.com main page is 1.0 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 14.7 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 14.7 kB or 75% of the original size.
Potential reduce by 2 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. Stats Boston images are well optimized though.
Potential reduce by 717.8 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 717.8 kB or 71% of the original size.
Potential reduce by 5.3 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. Stats.boston.com needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 43% of the original size.
Number of requests can be reduced by 69 (70%)
98
29
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stats Boston. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
stats.boston.com
202 ms
non-resp-tmpl-article.css
43 ms
jquery-1.11.0.min.js
29 ms
bat.js
19 ms
gpt.js
6 ms
head.min.js
28 ms
shsdefault.css
79 ms
shs.css
23 ms
urchin.js
5 ms
tracking.min.js
29 ms
body.min.js
23 ms
pubads_impl_81.js
11 ms
container.html
138 ms
blueconic.min.js
136 ms
no_jq_dpm_59129aacfb6cebbe2c52f30ef3424209f7252e82.min.js
137 ms
bcom-logo.svg
128 ms
v2_02_01.gif
119 ms
__utm.gif
113 ms
vrs.js
149 ms
jstag
131 ms
show_companion_ad.js
57 ms
ads
281 ms
mag.svg
89 ms
mag-white.svg
89 ms
social-cir-sprite.png
88 ms
Effra_Std_W_Rg.woff
90 ms
Effra_Std_W_Md.woff
89 ms
Effra_Std_W_Bd.woff
88 ms
firstevent
52 ms
56 ms
vrt.outbrain.com
56 ms
vrp.outbrain.com
53 ms
event
37 ms
abp.gif
16 ms
1
21 ms
abp.gif
9 ms
index.php
22 ms
pixel
38 ms
index.php
17 ms
acj
494 ms
pixel
18 ms
acj
491 ms
acj
546 ms
r2
10 ms
ads
251 ms
container.html
6 ms
2-002139858-00001j;size=728x90;tag_id=14931;ref=boston.com;cb=1694937649
19 ms
2-002139858-00001j;size=300x250;tag_id=14931;ref=boston.com;cb=276472326
27 ms
osd.js
3 ms
ads
252 ms
ADTECH;cfp=1;rndc=1456837547;loc=100;target=_blank;grp=[group];misc==
62 ms
pb
7 ms
generic
29 ms
aol
37 ms
pixel
37 ms
ads
266 ms
generic
18 ms
mapuser
23 ms
mapuser
22 ms
mapuser
17 ms
mapuser
21 ms
providerid=1037;userid=bc8b8205-90ad-41f5-ab7e-32487b950055
10 ms
mapuser
6 ms
mapuser
5 ms
mapuser
5 ms
jstag
14 ms
1
23 ms
pb
12 ms
jstag
13 ms
rud
59 ms
pb
6 ms
pd
9 ms
st
30 ms
bo
31 ms
showad.js
41 ms
openx
5 ms
pixel
21 ms
sd
5 ms
pd
7 ms
st
52 ms
bo
53 ms
sd
7 ms
f962dd79-3efa-efcf-b562-aee5cedd0c93
42 ms
sd
10 ms
sd
10 ms
sd
30 ms
sd
29 ms
sd
27 ms
showad.js
41 ms
AdServerServlet
48 ms
pd
28 ms
st
35 ms
bo
36 ms
PugMaster
25 ms
p25
11 ms
redirect
51 ms
OpenX.ashx
80 ms
pb
11 ms
sd
36 ms
jstag
26 ms
ibs:dpid=19566&dpuuid=3F92245E-6866-438A-91D8-ED17CDDA2C04
26 ms
p-P7x87XHnVfbWr.gif
15 ms
pixel
27 ms
generic
7 ms
Pug
29 ms
Pug
23 ms
Pug
20 ms
Pug
22 ms
sd
9 ms
match.gif
43 ms
sd
9 ms
Pug
10 ms
sd
12 ms
ibs:dpid=13870&dpuuid=c3a00f9e96404c1ca85cd4a4
5 ms
stats.boston.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
stats.boston.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
stats.boston.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stats.boston.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 Stats.boston.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.
stats.boston.com
Open Graph description is not detected on the main page of Stats Boston. 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: