files.wordpress.com WordPress.com: Create a free website or blog

Mobile Usability

93/100

Good

Mobile Speed

54/100

Bad

Last tested: 2017-05-08

Rescan
files.wordpress.com Mobile Usability: 93/100
files.wordpress.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="https://wordpr….com/features/">Features</a> and 16 others are close to other tap targets.
files.wordpress.com Mobile Speed: 54/100
files.wordpress.com Mobile Speed Test Quick Overview

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

Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
https://s1.wp.com/home.logged-out/page-domain-only…bundle.js?v=1493216117
https://www.googleadservices.com/pagead/conversion_async.js
Optimize CSS Delivery of the following:
https://fonts.googleapis.com/css?family=Noto+Serif…t,latin-ext,vietnamese
https://fonts.googleapis.com/css?family=Noto+Sans
https://s1.wp.com/home.logged-out/page-domain-only…tyles.css?v=1493216117
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://files.wordpress.com/
https://files.wordpress.com/
https://wordpress.com/
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 8% of the final above-the-fold content could be rendered with the full HTML response.
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:
https://d3ir0rz7vxwgq5.cloudfront.net/mwData.min.js (expiration not specified)
https://getrockerbox.com/assets/xyz.js (expiration not specified)
https://snap.licdn.com/li.lms-analytics/insight.min.js (expiration not specified)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/823166884443641?v=2.7.6 (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://secure.leadback.advertising.com/adcedge/lb…sprlb_1472760452[8760] (60 minutes)
https://secure.leadback.advertising.com/adcedge/lb…sprlb_1487351090[8760] (60 minutes)
https://www.google-analytics.com/analytics.js (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 28KiB (70% reduction).
Compressing https://d3ir0rz7vxwgq5.cloudfront.net/mwData.min.js could save 28KiB (70% reduction).

files.wordpress.com Mobile Resources


Total Resources63
Number of Hosts40
Static Resources23
JavaScript Resources17
CSS Resources3

files.wordpress.com Mobile Resource Breakdown