huffingtonpost.com HuffPost - Breaking News, U.S. and World News | HuffPost

Mobile Usability

99/100

Good

Mobile Speed

36/100

Bad

Last tested: 2017-08-27

Rescan
huffingtonpost.com Mobile Usability: 99/100
huffingtonpost.com Mobile Usability Test Quick Overview

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target <a href="/us/author/dave-jamieson" class="bn-clickable">Dave Jamieson</a> and 8 others are close to other tap targets.
huffingtonpost.com Mobile Speed: 36/100
huffingtonpost.com Mobile Speed Test Quick Overview

Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1,003KiB (50% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590a48….jpeg?cache=4ujt6c7h4g could save 395.4KiB (98% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590356….jpeg?cache=7xja4n56fx could save 37.5KiB (44% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/591008….jpeg?cache=zks9f97g5p could save 32.3KiB (42% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fc7….jpeg?cache=kwrdltvwsz could save 28.9KiB (37% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fb3….jpeg?cache=omeua845ug could save 25.1KiB (35% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/59080c….jpeg?cache=0nkas8br7k could save 25.1KiB (41% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fb2751400001417f8baf5.jpeg could save 24.1KiB (42% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590f4f….jpeg?cache=36tb6walen could save 23.6KiB (75% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590d26071600002000c59c20.jpeg could save 22.3KiB (39% reduction).
Compressing https://o.aolcdn.com/images/dims?client=5c82fa76e5…5b1400001417f8badb.jpg could save 21.2KiB (45% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590b635e1700002000dd692a.jpeg could save 20.4KiB (37% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590f825117000020005a53bf.jpeg could save 20.3KiB (43% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/591062….jpeg?cache=h4ybclvioi could save 19.5KiB (44% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590b9a….jpeg?cache=cg9rm3uxsi could save 19.1KiB (35% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590df3fc17000024005a522e.jpg could save 18.4KiB (40% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fc6….jpeg?cache=fphf2nmckm could save 16.1KiB (38% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590e06….jpeg?cache=dqfj6dobiy could save 14.8KiB (72% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fd0….jpeg?cache=2n1riewgfn could save 13.6KiB (36% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590fc4….jpeg?cache=ljvmdlppuy could save 13.4KiB (69% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fa4….jpeg?cache=lv5lv8coxl could save 12.8KiB (35% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590fc0….jpeg?cache=7vn6xx82hh could save 12.7KiB (67% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590fb0….jpeg?cache=0kh06ytgoo could save 12.6KiB (63% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590fdf2d1600002000c59ed0.jpeg could save 12.4KiB (58% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/59103c….jpeg?cache=ctrkydszmo could save 12.1KiB (57% reduction).
Compressing https://o.aolcdn.com/images/dims?client=5c82fa76e5…131400005509f8b84c.jpg could save 11.9KiB (42% reduction).
Compressing http://img.huffingtonpost.com/asset/945_579,qualit….jpeg?cache=ud13vy91wv could save 11KiB (25% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590ffb….jpeg?cache=sylzopbwml could save 10.5KiB (62% reduction).
Compressing https://o.aolcdn.com/images/dims?client=5c82fa76e5…751400008b031a6547.jpg could save 10.5KiB (35% reduction).
Compressing https://o.aolcdn.com/images/dims?client=5c82fa76e5…ac1400001f00f8b8da.jpg could save 10KiB (30% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fc8….jpeg?cache=4e36mte9pm could save 9.9KiB (29% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590f75….jpeg?cache=bbesogynor could save 9.2KiB (29% reduction).
Compressing https://o.aolcdn.com/images/dims?client=5c82fa76e5…d01400002000f8b473.jpg could save 9KiB (21% reduction).
Compressing https://o.aolcdn.com/images/dims?client=5c82fa76e5…d91600002000c59cf1.jpg could save 8KiB (31% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590f89441400000b17f8baa9.jpg could save 7.3KiB (18% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fd7….jpeg?cache=8ojynaupc2 could save 7.1KiB (25% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590b3aa1150000f4068c7af2.jpeg could save 7.1KiB (13% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590f3bdc1400000d17f8ba28.jpeg could save 6.1KiB (53% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/590fc5….jpeg?cache=lemouuz5uv could save 6KiB (23% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590f66….jpeg?cache=6nnmd7kl7s could save 5.8KiB (42% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/59100b….jpeg?cache=irfzpotmjy could save 5.3KiB (46% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/59103c….jpeg?cache=m1gyjfcbvb could save 4.9KiB (47% reduction).
Compressing http://img.huffingtonpost.com/asset/580_325/59102e….jpeg?cache=atdzdvzyee could save 3.9KiB (12% reduction).
Compressing http://img.huffingtonpost.com/asset/160_160/590f57….jpeg?cache=ynbl7lwgdm could save 3KiB (26% reduction).
Compressing https://o.aolcdn.com/images/dims?client=5c82fa76e5…a51600001f00c59afe.jpg could save 3KiB (28% reduction).
Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources. This causes a delay in rendering your page.
http://s.m.huffpost.com/assets/mobileweb-ac7ab04e7…74c55f881844795850a.js
Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://huffingtonpost.com/
http://www.huffingtonpost.com/
http://m.huffpost.com/
Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://o.aolcdn.com/os/aol/beacon.min.js (expiration not specified)
http://o.aolcdn.com/os/aol/omniture.min.js (expiration not specified)
http://o.aolcdn.com/os/moat/prod/moatuac.js (expiration not specified)
http://s.blogsmithmedia.com/asvcs.aol.com/include/sn_sync-built.js (expiration not specified)
http://m.huffpost.com/mapi/v2/us/d/entertainment?device=mobileweb (30 seconds)
http://m.huffpost.com/mapi/v2/us/d/impact?device=mobileweb (30 seconds)
http://m.huffpost.com/mapi/v2/us/d/lifestyle?device=mobileweb (30 seconds)
http://m.huffpost.com/mapi/v2/us/d/voices?device=mobileweb (30 seconds)
http://m.huffpost.com/mapi/v2/us/section/contributor?device=mobileweb (30 seconds)
http://m.huffpost.com/mapi/v2/us/section/politics?device=mobileweb (30 seconds)
http://m.huffpost.com/mapi/v2/us/section/video?device=mobileweb (30 seconds)
http://meraxes-cdn.polarmobile.com/nativeads/v1.4.…76e?count=1&fragment=9 (46 seconds)
http://assets.pinterest.com/js/pinit.js (2.7 minutes)
http://assets.pinterest.com/js/pinit_main.js?0.1183736752718687 (3 minutes)
http://dtm.advertising.com/916f392e-1af6-43dd-bc12-239421d8b718.js (5 minutes)
http://dtm.advertising.com/9e865b16-bf55-4ffb-9f2a-70dadfc986c7.js (5 minutes)
http://meraxes-cdn.polarmobile.com/nativeads/v1.4.…76e?count=1&fragment=2 (5 minutes)
http://meraxes-cdn.polarmobile.com/mrm/v1.0.0/json…f5478d864f1b629b02a278 (6.9 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1043018625788392?v=2.7.6 (20 minutes)
https://connect.facebook.net/signals/config/1100125983380803?v=2.7.6 (20 minutes)
https://connect.facebook.net/signals/config/1621685564716533?v=2.7.6 (20 minutes)
http://plugin.mediavoice.com/mediaconductor/mc.js (46.8 minutes)
https://js-agent.newrelic.com/nr-1026.min.js (2 hours)
http://plugin.mediavoice.com/plugin.js (2.9 hours)
http://js.moatads.com/polar984REuc19/moatad.js (9.7 hours)
Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 43% of the final above-the-fold content could be rendered with the full HTML response.

huffingtonpost.com Mobile Resources


Total Resources152
Number of Hosts38
Static Resources104
JavaScript Resources42
CSS Resources3

huffingtonpost.com Mobile Resource Breakdown