Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

neighborly.com

Find Home Services Experts in Your Town, For Free | Neighborly

Page Load Speed

927 ms in total

First Response

44 ms

Resources Loaded

465 ms

Page Rendered

418 ms

neighborly.com screenshot

About Website

Click here to check amazing Neighborly content for United States. Otherwise, check out these important facts you probably never knew about neighborly.com

Find and hire locally-owned home services experts whose work is trusted by homeowners and business owners in your neighborhood. It’s easy with Neighborly.

Visit neighborly.com

Key Findings

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

Performance Metrics

neighborly.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value3,840 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value31.5 s

0/100

10%

Network Requests Diagram

neighborly.com

44 ms

www.neighborly.com

124 ms

gtm.js

104 ms

neighborly-mark-white.webp

42 ms

nei-icon-sprite-1.png

66 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 96% of them (68 requests) were addressed to the original Neighborly.com, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (224 ms) belongs to the original domain Neighborly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.3 kB (76%)

Content Size

559.6 kB

After Optimization

135.3 kB

In fact, the total size of Neighborly.com main page is 559.6 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. 45% of websites need less resources to load. HTML takes 495.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 421.0 kB

  • Original 495.3 kB
  • After minification 472.1 kB
  • After compression 74.4 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 421.0 kB or 85% of the original size.

Image Optimization

-24%

Potential reduce by 3.3 kB

  • Original 13.5 kB
  • After minification 10.2 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, Neighborly needs image optimization as it can save up to 3.3 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 51 B

  • Original 50.8 kB
  • After minification 50.8 kB
  • After compression 50.7 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 17 (25%)

Requests Now

69

After Optimization

52

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

Accessibility Review

neighborly.com accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

neighborly.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

neighborly.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Neighborly.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 Neighborly.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

Open Graph description is not detected on the main page of Neighborly. 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: