ThisIsWhyImBroke :: The Internet's Mall

Mobile Usability



Mobile Speed



Last tested: 2017-08-29

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="/sit-on-my-face-chair/" class="ng-binding">Sit On My Face Chair</a> and 11 others are close to other tap targets. Mobile Speed: 51/100 Mobile Speed Test Quick Overview

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

Your page has 9 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:…%3A400%2C700&ver=4.5.2
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.
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: (expiration not specified) (expiration not specified) (expiration not specified)…_ate.track.config_resp (60 seconds) (2.1 minutes) (10 minutes) (30 minutes) (30 minutes)…ect&session=first+time (30 minutes) (2 hours) (5 days)…ereal-bowl-300x250.jpg (5 days) (5 days) (5 days) (5 days)…-zoom-lens-300x250.jpg (5 days)
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 26% of the final above-the-fold content could be rendered with the full HTML response.
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 69.6KiB (23% reduction).
Compressing…ing-dildos-300x250.jpg could save 14.6KiB (34% reduction).
Compressing…-vape-shot-300x250.jpg could save 7.3KiB (26% reduction).
Compressing…air-femdom-300x250.jpg could save 7.1KiB (35% reduction).
Compressing…p-lego-set-300x250.jpg could save 6.3KiB (26% reduction).
Compressing…er-sticker-300x250.jpg could save 6KiB (23% reduction).
Compressing could save 5.2KiB (18% reduction).
Compressing could save 5.1KiB (16% reduction).
Compressing could save 5KiB (23% reduction).
Compressing could save 4.2KiB (15% reduction).
Compressing…ereal-bowl-300x250.jpg could save 3KiB (16% reduction).
Compressing could save 2.6KiB (14% reduction).
Compressing…-zoom-lens-300x250.jpg could save 2KiB (14% reduction).
Compressing could save 1.3KiB (47% reduction).
Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 2.1KiB (28% reduction).
Minifying could save 1,011B (24% reduction) after compression.
Minifying could save 658B (25% reduction) after compression.
Minifying could save 519B (47% reduction) after compression. Mobile Resources

Total Resources49
Number of Hosts11
Static Resources39
JavaScript Resources20
CSS Resources2 Mobile Resource Breakdown