Mobile Usability



Mobile Speed



Last tested: 2017-08-27

Rescan Mobile Usability: 99/100 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="/artists?from=hpartists">artists</a> and 1 others are close to other tap targets.
The tap target <a href="/fans?from=hpfans">fans</a> is close to 1 other tap targets.
The tap target <a href="">Paul Grelet</a> is close to 1 other tap targets.
The tap target <a href="#" class="bcweekly-share-link">Share this Show</a> is close to 1 other tap targets.
The tap target <a href="https://daily.…amobi-feature/">The Artful Dis…Feature</a> is close to 1 other tap targets. Mobile Speed: 60/100 Mobile Speed Test Quick Overview

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.…fa01981fc3f0ed4396b.js
Optimize CSS Delivery of the following:…515edabc08398ba1c7.css…1f375ad1c9f2c4dd3d.css…6ed1b6e8567b1b9fe7.css…3e5ef812c043434fcf.css…3b1f2083e826e9e54c.css
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 159.3KiB (26% reduction).
Compressing could save 51.1KiB (29% reduction).
Compressing could save 39KiB (26% reduction).
Compressing could save 25.9KiB (33% reduction).
Compressing could save 10.1KiB (22% reduction).
Compressing could save 7.9KiB (20% reduction).
Compressing could save 6.8KiB (19% reduction).
Compressing could save 5.1KiB (27% reduction).
Compressing could save 4KiB (27% reduction).
Compressing could save 2.7KiB (22% reduction).
Compressing could save 1.7KiB (17% reduction).
Compressing could save 1.7KiB (15% reduction).
Compressing could save 1.4KiB (12% reduction).
Compressing could save 1KiB (16% reduction).
Compressing could save 994B (18% reduction).
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.
93KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. Prioritize the above-the-fold content so that it can be rendered with only the first 2 round-trips' worth of HTML.
Only about 12% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.
Reduce server response time

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 8.8KiB (26% reduction).
Minifying…6ed1b6e8567b1b9fe7.css could save 6.1KiB (24% reduction) after compression.
Minifying…1f375ad1c9f2c4dd3d.css could save 2.8KiB (32% reduction) after compression.
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: (2 hours)
Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 3.2KiB (59% reduction).
Compressing could save 3.2KiB (59% reduction). Mobile Resources

Total Resources38
Number of Hosts9
Static Resources33
JavaScript Resources6
CSS Resources4 Mobile Resource Breakdown