Stack Overflow

Mobile Usability



Mobile Speed



Last tested: 2017-08-27

Rescan Mobile Usability: 92/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="/questions/ask">Ask</a> is close to 1 other tap targets.
The tap target <a href="/questions/438…ze-overlapping">CSS - Backgrou…ze overlapping</a> and 76 others are close to other tap targets.
The tap target <a href="/questions/438…g?lastactivity" class="-time">51 secs ago</a> and 191 others are close to other tap targets.
The tap target <a href="/users/5782520/varsha-ghodki" class="author">varsha ghodki</a> and 86 others are close to other tap targets.
The tap target <a href="/questions/tagged/apache-spark" class="post-tag">apache-spark</a> and 8 others are close to other tap targets. Mobile Speed: 71/100 Mobile Speed Test Quick Overview

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

Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
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)
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.9KiB (21% reduction).
Compressing could save 2.9KiB (21% reduction). Mobile Resources

Total Resources17
Number of Hosts9
Static Resources9
JavaScript Resources7
CSS Resources1 Mobile Resource Breakdown