paytm.com Online Recharge - Instant Mobile Recharge for Prepaid, Bill Payment , DTH & Data Card Recharge and Utility Bill Payment & Paytm

Mobile Usability

98/100

Good

Mobile Speed

64/100

Bad

Last tested: 2017-05-08

Rescan
paytm.com Mobile Usability: 98/100
paytm.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 <div class="hQqL _1li"></div> and 9 others are close to other tap targets.
The tap target <a href="/shop/h/summer-special-store" class="_1Bte">SaleSummer Appliances</a> is close to 1 other tap targets.
The tap target <a href="/about-us/">About Us</a> and 2 others are close to other tap targets.
The tap target <a href="/about-us/our-…icies/#privacy">Privacy policy</a> and 2 others are close to other tap targets.
paytm.com Mobile Speed: 64/100
paytm.com Mobile Speed Test Quick Overview

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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
https://fonts.googleapis.com/css?family=Open+Sans:300,400,600
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 57% 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://assetscdn1.paytm.com/react/paytmMobile-ceb…69c7cc9bb2e3ad1b.woff2 (expiration not specified)
https://visitorapi.betaout.com/visitor/register (expiration not specified)
https://cdnconfig.s3-accelerate.amazonaws.com/core…x4fs3hyhg8nhh0.json?v2 (60 seconds)
https://cdnconfig.s3-accelerate.amazonaws.com/core…30268/settings.json?v2 (60 seconds)
https://d22vyp49cxb9py.cloudfront.net/jal-v2.min.js (5 minutes)
https://u.heatmap.it/conf/paytm.com.js (5 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-PTT2P2 (15 minutes)
https://connect.facebook.net/en_US/fbds.js (20 minutes)
https://d22vyp49cxb9py.cloudfront.net/v2/boutapiv2.2-min.css (60 minutes)
https://u.heatmap.it/log.js (60 minutes)
https://www.google-analytics.com/plugins/ua/ec.js (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 19.9KiB (91% reduction).
Compressing https://cdnconfig.s3-accelerate.amazonaws.com/core…x4fs3hyhg8nhh0.json?v2 could save 10.5KiB (90% reduction).
Compressing https://cdnconfig.s3-accelerate.amazonaws.com/ms/l…x4fs3hyhg8nhh0.json?v2 could save 9.4KiB (91% reduction).

paytm.com Mobile Resources


Total Resources49
Number of Hosts23
Static Resources25
JavaScript Resources22
CSS Resources2

paytm.com Mobile Resource Breakdown