justdial.com Home Page

Mobile Usability



Mobile Speed



Last tested: 2017-08-27

justdial.com Mobile Usability: 99/100
justdial.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="javascript:void(0)" class="active">Home</a> and 4 others are close to other tap targets.
The tap target <span id="Footer_mic_icon" class="footersprite fvoice_search"> is close to 2 other tap targets.
justdial.com Mobile Speed: 56/100
justdial.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:
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.
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 42% 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 27.1KiB (19% reduction).
Compressing https://akam2.cdn.jdmagicbox.com/intimages/us/hotk….jpg?output-quality=40 could save 9KiB (33% reduction).
Compressing https://akam1.cdn.jdmagicbox.com/intimages/us/hotk….jpg?output-quality=40 could save 5.1KiB (13% reduction).
Compressing https://akam3.cdn.jdmagicbox.com/intimages/us/hotk….jpg?output-quality=40 could save 5KiB (14% reduction).
Compressing https://akam4.cdn.jdmagicbox.com/intimages/us/hotk….jpg?output-quality=40 could save 3.9KiB (18% reduction).
Compressing https://akam.cdn.jdmagicbox.com/intimages/us/hotke….png?output-quality=40 could save 1.5KiB (36% reduction).
Compressing https://akam.cdn.jdmagicbox.com/intimages/us/hotke….png?output-quality=40 could save 972B (36% reduction).
Compressing https://akam.cdn.jdmagicbox.com/intimages/us/wap/voice@2x.png could save 895B (16% reduction).
Compressing https://akam.cdn.jdmagicbox.com/intimages/us/jd_rw…bal_autosuggest_1x.png could save 778B (11% reduction).
Reduce server response time

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://www.google-analytics.com/analytics.js (2 hours)

justdial.com Mobile Resources

Total Resources40
Number of Hosts10
Static Resources36
JavaScript Resources2
CSS Resources1

justdial.com Mobile Resource Breakdown