1.5 sec in total
219 ms
1.1 sec
148 ms
Visit nearby.com now to see the best up-to-date Nearby content for India and also check out these interesting facts you probably never knew about nearby.com
Join Nextdoor, an app for neighborhoods where you can get local tips, buy and sell items, and more
Visit nearby.comWe analyzed Nearby.com page load time and found that the first response time was 219 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
nearby.com performance score
name
value
score
weighting
Value13.5 s
0/100
10%
Value22.4 s
0/100
25%
Value19.0 s
0/100
10%
Value18,110 ms
0/100
30%
Value0.025
100/100
15%
Value37.5 s
0/100
10%
219 ms
160 ms
67 ms
113 ms
109 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Nearby.com, 28% (11 requests) were made to Cdnwp.global.ssl.fastly.net and 23% (9 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (364 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.3 MB (71%)
1.8 MB
520.6 kB
In fact, the total size of Nearby.com main page is 1.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 57.2 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 14.4 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.2 kB or 85% of the original size.
Potential reduce by 9.7 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Nearby needs image optimization as it can save up to 9.7 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 998.6 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 998.6 kB or 70% of the original size.
Potential reduce by 185.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Nearby.com needs all CSS files to be minified and compressed as it can save up to 185.1 kB or 82% of the original size.
Number of requests can be reduced by 20 (65%)
31
11
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nearby. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
nearby.com
219 ms
www.whitepages.com
160 ms
css
67 ms
application-d3b0285326fa0ec838fde9c23f2b2d89.css
113 ms
head_scripts-49427d9ffdb26b7227f3e67746e9d34a.js
109 ms
respond-319d44d0e7e8f902a1153c050b638f29.js
109 ms
respond.proxy.js
73 ms
ga.487700.js
183 ms
21319
63 ms
application-c856399bb8517725845ee5aee7dd5d0b.js
182 ms
index-29e1eef74fe595a302af09fa7c39d984.js
179 ms
amplitude-2.5.0-min.gz.js
324 ms
gtm.js
314 ms
ic-cropped-w-45073f9d67ba65c501200b6cb7d90857.svg
289 ms
logo_wp_380x93-5681cec23da2c52efce92e0dfd99e049.png
292 ms
icon_wp_sprite_1x-e666afb02708b2175f0fad02c0f1464b.png
294 ms
button_googlePlay-015030ac3f3e51e7d24ade070828e116.png
292 ms
button_appStore-8bdab7d77f9f254f6216d6a15c40c072.png
295 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
295 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
296 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
364 ms
analytics.js
93 ms
quant.js
172 ms
yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf
80 ms
AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
bk-coretag.js
157 ms
print-cfe44e9faedd392b299dd264362e3c47.css
83 ms
analytics_debug.js
65 ms
collect
146 ms
collect
40 ms
collect
126 ms
collect
41 ms
collect
42 ms
collect
43 ms
collect
42 ms
collect
43 ms
pixel;r=1196821679;a=p-13CZptiqAcX_w;labels=Site.WhitePages.ca%20(10002)%2CChannelhome%2CPage%20Name.home;fpan=1;fpa=P0-965230754-1458444594152;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458444594151;tzo=-180;ref=;url=http%3A%2F%2Fwww.whitepages.com%2F;ogl=
102 ms
19777
34 ms
collect
12 ms
ga-audiences
40 ms
nearby.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
nearby.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
nearby.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nearby.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nearby.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
nearby.com
Open Graph description is not detected on the main page of Nearby. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: