Tools & Wizards About Us
nearer.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

nearer.com

nearer.com - A fresh way to find the nearest shops, restaurants and other street-fronted businesses: near me all across the whole of the UK.

Page Load Speed

1.9 sec in total

First Response

97 ms

Resources Loaded

1.7 sec

Page Rendered

61 ms

nearer.com screenshot

About Website

Click here to check amazing Near Er content for India. Otherwise, check out these important facts you probably never knew about nearer.com

Business listings and local search are going hyperlocal: find nearby shops, hotels, restaurants, pubs, bars, and useful promotions near me all across the UK, with locations, business hours, and my off...

Visit nearer.com

Key Findings

We analyzed Nearer.com page load time and found that the first response time was 97 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

nearer.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value590 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value12.4 s

14/100

10%

Network Requests Diagram

www.nearer.com

97 ms

minified.js

47 ms

focus-within-polyfill.js

45 ms

polyfill.min.js

877 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

79 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Nearer.com, 49% (17 requests) were made to Static.parastorage.com and 31% (11 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (877 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 554.4 kB (62%)

Content Size

893.4 kB

After Optimization

339.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nearer.com main page is 893.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 573.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 236.7 kB

  • Original 311.9 kB
  • After minification 310.1 kB
  • After compression 75.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 236.7 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 7.9 kB
  • After minification 7.9 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. Near Er images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 317.7 kB

  • Original 573.7 kB
  • After minification 573.7 kB
  • After compression 256.0 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 317.7 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (56%)

Requests Now

18

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Near Er. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.nearer.com

www.nearer.com

97 ms

minified.js

minified.js

47 ms

focus-within-polyfill.js

focus-within-polyfill.js

45 ms

polyfill.min.js

polyfill.min.js

877 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

thunderbolt-commons.c1d8ed1c.bundle.min.js

79 ms

main.4a2d1e74.bundle.min.js

main.4a2d1e74.bundle.min.js

42 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

41 ms

lodash.min.js

lodash.min.js

77 ms

react.production.min.js

react.production.min.js

77 ms

react-dom.production.min.js

react-dom.production.min.js

78 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

79 ms

baed85_6ca3f0c08d484cd684272e1c4be18752~mv2.jpg

baed85_6ca3f0c08d484cd684272e1c4be18752~mv2.jpg

226 ms

baed85_cb2ddf1fe59543198267c053307dde54~mv2.jpg

baed85_cb2ddf1fe59543198267c053307dde54~mv2.jpg

391 ms

Long%20green%20logo.jpg

Long%20green%20logo.jpg

330 ms

bundle.min.js

bundle.min.js

38 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

34 ms

AvenirLTW05-35Light.woff

AvenirLTW05-35Light.woff

35 ms

101 ms

99 ms

96 ms

97 ms

94 ms

94 ms

131 ms

129 ms

130 ms

129 ms

127 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

19 ms

deprecation-style.v5.css

deprecation-style.v5.css

8 ms

right-arrow.svg

right-arrow.svg

16 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

3 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

6 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

6 ms

Accessibility Review

nearer.com accessibility score

100

Accessibility Issues

Best Practices

nearer.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

nearer.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nearer.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Nearer.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nearer.com

Open Graph data is detected on the main page of Near Er. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: