76 sec in total
144 ms
44.8 sec
31.1 sec
Welcome to motherjones.com homepage info - get ready to check Mother Jones best content for United States right away, or after learning these important things about motherjones.com
Visit motherjones.comWe analyzed Motherjones.com page load time and found that the first response time was 144 ms and then it took 75.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
motherjones.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value12.2 s
0/100
25%
Value21.3 s
0/100
10%
Value37,450 ms
0/100
30%
Value0
100/100
15%
Value50.1 s
0/100
10%
144 ms
1198 ms
163 ms
312 ms
1391 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 22% of them (32 requests) were addressed to the original Motherjones.com, 6% (8 requests) were made to Tpc.googlesyndication.com and 6% (8 requests) were made to Ads.pictela.net. The less responsive or slowest element that took the longest time to load (12 sec) relates to the external source Tpc.googlesyndication.com.
Page size can be reduced by 3.1 MB (37%)
8.3 MB
5.2 MB
In fact, the total size of Motherjones.com main page is 8.3 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 4.3 MB which makes up the majority of the site volume.
Potential reduce by 50.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 50.4 kB or 73% of the original size.
Potential reduce by 147.5 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. Mother Jones images are well optimized though.
Potential reduce by 1.6 MB
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 1.6 MB or 66% of the original size.
Potential reduce by 1.3 MB
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. Motherjones.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 86% of the original size.
Number of requests can be reduced by 76 (61%)
125
49
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mother Jones. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and as a result speed up the page load time.
motherjones.com
144 ms
www.motherjones.com
1198 ms
wp-emoji-release.min.js
163 ms
312 ms
css
1391 ms
jetpack.css
558 ms
735 ms
devicepx-jetpack.js
2850 ms
734 ms
e-201736.js
2919 ms
analytics.js
1119 ms
fbevents.js
2069 ms
MJ_comp.png
743 ms
170829_dreamer-sign.png
696 ms
20170830-trumplies.jpg
695 ms
170901_daca-protest.png
695 ms
barker-83117.jpg
938 ms
mynabirds_224-e1504218243455.jpeg
938 ms
schoollunchmasterfinal.jpg
940 ms
20170901-nurse.png
903 ms
20170831-trumpcomey.jpeg
903 ms
20170817-trump.jpg
902 ms
kevin.png
970 ms
lewishine-01064u.jpg
969 ms
taurus_2000x1124.jpg
1119 ms
worldbank-630x354.jpg
1120 ms
MJ_comp_grey.png
1311 ms
vip-powered-light-small.png
1119 ms
Calluna-Regular.otf
605 ms
Calluna-Black.otf
605 ms
Mallory-Bold.woff
1173 ms
Mallory-Light.woff
1000 ms
collect
62 ms
;misc=1504624147333;aduho=+180
182 ms
712336422304921
316 ms
post_adtech
832 ms
grey_line.png
812 ms
;misc=1504624149735;aduho=+180
234 ms
1654 ms
jitabox.js
2166 ms
post_adtech
1110 ms
pixel
3728 ms
membership_ads.png
2136 ms
Mallory-BoldItalic.woff
1196 ms
Mallory-LightItalic.woff
902 ms
;misc=1504624151005;aduho=+180
1248 ms
639 ms
cfcm.ashx
2018 ms
ajs.php
1562 ms
post_adtech
1453 ms
mapuser
244 ms
ecc
791 ms
jita.js
589 ms
pixel
575 ms
lg.php
1574 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1504624154180
1516 ms
prebid
3544 ms
trinity.js
3177 ms
getjs.static.js
668 ms
header
3332 ms
prebid
3395 ms
prebid
3952 ms
gshowad.js
3345 ms
prebid
3658 ms
1447 ms
prebid
3737 ms
match.aspx
2209 ms
cs
1873 ms
gpt.js
1356 ms
user_sync.html
1406 ms
async_usersync.html
1625 ms
AdCallAggregator
2200 ms
showad.js
1249 ms
bounce
660 ms
pubads_impl_147.js
4668 ms
generic
4501 ms
ad
4413 ms
PugMaster
4427 ms
sync
2123 ms
us.gif
7478 ms
pixel
6558 ms
;misc=1504624162179;aduho=+180
1747 ms
showad.js
1236 ms
us.gif
5071 ms
sync
1691 ms
publishertag.js
3456 ms
extFile1.js
3259 ms
post_adtech
3824 ms
user-sync
6719 ms
us.gif
6419 ms
p-P7x87XHnVfbWr.gif
7268 ms
pixel
4763 ms
generic
3096 ms
ads
2233 ms
us.gif
3819 ms
container.html
1199 ms
ajs.php
2929 ms
Pug
6875 ms
container.html
1349 ms
osd.js
1766 ms
Pug
7266 ms
sync
2282 ms
sync
3482 ms
abg.js
4557 ms
m_js_controller.js
7127 ms
m_window_focus_non_hydra.js
10278 ms
osd_listener.js
9963 ms
12901484829646952889
11969 ms
x_button_blue2.png
10882 ms
lg.php
1701 ms
ADTECH;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1504624170649
1354 ms
MotherJones_970x250_store.jpg
1349 ms
orange-border.png
1343 ms
Pug
5529 ms
match.aspx
1558 ms
Pug
5603 ms
user-sync
4410 ms
Pug
6838 ms
;misc=1504624173008;aduho=+180
1192 ms
fontawesome-webfont.woff
838 ms
Pug
6390 ms
Pug
6520 ms
adtechRichMediaLib_2_63_0.js
4439 ms
post_adtech
2898 ms
generic
4762 ms
iconx2-000000.png
9576 ms
googlelogo_dark_color_84x28dp.png
9574 ms
s
9812 ms
cookie_push.html
7568 ms
receive
7263 ms
quant.js
4354 ms
beacon.js
4412 ms
index.html
3152 ms
g.gif
980 ms
Pug
1166 ms
ADTECH_1_12_0.js
667 ms
interstitial.js
874 ms
cse
2003 ms
user-sync
1428 ms
rules-p-Be0QSW1bbb6Qv.js
688 ms
pixel
638 ms
close-button.png
631 ms
1x1-transparent.png
842 ms
unmute32.png
817 ms
mute32.png
729 ms
motherjones.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
motherjones.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
Page has valid source maps
motherjones.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
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Motherjones.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 Motherjones.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
motherjones.com
Open Graph description is not detected on the main page of Mother Jones. 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: