Website review, no card needed

matchwithneighbors.com logo

matchwithneighbors.com website review

Visit site (opens in a new tab)Reviewed 11 October 202645 issues · 88 checks

This review found 45 issues worth fixing on matchwithneighbors.com, 17 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.2 s1.1 sApr 18Oct 31.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.1 s
Apr 25, 20261.1 s
May 2, 20261.1 s
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
87 ms78 msApr 18Oct 383 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202679 ms
Apr 25, 202679 ms
May 2, 202679 ms
May 9, 202679 ms
May 16, 202679 ms
May 23, 202679 ms
May 30, 202680 ms
Jun 6, 202680 ms
Jun 13, 202681 ms
Jun 20, 202683 ms
Jun 27, 202684 ms
Jul 4, 202685 ms
Jul 11, 202686 ms
Jul 18, 202686 ms
Jul 25, 202686 ms
Aug 1, 202686 ms
Aug 8, 202686 ms
Aug 15, 202686 ms
Aug 22, 202686 ms
Aug 29, 202686 ms
Sep 5, 202686 ms
Sep 12, 202686 ms
Sep 19, 202685 ms
Sep 26, 202684 ms
Oct 3, 202683 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of matchwithneighbors.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. matchwithneighbors.com at 0.4 s0.4 s
  2. matchwithneighbors.com at 0.8 s0.8 s
  3. matchwithneighbors.com at 1.1 s1.1 s
  4. matchwithneighbors.com at 1.5 s1.5 s
  5. matchwithneighbors.com at 1.9 s1.9 s
  6. matchwithneighbors.com at 2.3 s2.3 s
  7. matchwithneighbors.com at 2.6 s2.6 s
  8. matchwithneighbors.com at 3.0 s3.0 s

Speed

10 to fix31
  • Reduce unused JavaScript

    5.3 s · 726 KiB

    About 726 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.

  • Use efficient cache lifetimes

    3.8 s · 795 KiB

    24 files are served with short cache lifetimes, so returning visitors download them again (795 KiB).

  • Render-blocking requests

    3.3 s

    20 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

  • Improve image delivery

    1.8 s · 402 KiB

    4 images could be 402 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

  • Reduce unused CSS

    1.7 s · 271 KiB

    About 271 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31 (desktop: 89). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Cloudflare CDN and VWO and others), adding 1.9 MB and 907 ms of main-thread time.

  • Google CDN adds 444 ms

    444 ms

    Google CDN costs a phone 444 ms of main-thread work and 733 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Cloudflare CDN adds 199 ms

    199 ms

    Cloudflare CDN costs a phone 199 ms of main-thread work and 727 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • First Contentful Paint: 13.3 s

    13.3 s

    The first text or image appears after 13.3 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 17.5 s

    17.5 s

    Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MatchWithNeighbors Login Explore freely, discreetly, on you…”.

  • Speed Index: 13.3 s

    13.3 s

    Visually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 18.1 s

    18.1 s

    The page becomes fully interactive after 18.1 s. Good is under 3.8 s.

  • Cumulative Layout Shift: 0.714

    0.714

    The layout shifts by 0.714 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user TTFB: 906 ms

    906 ms

    Real visitors wait 906 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 79 ms to 83 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 151 ms

    151 ms

    Real visitors wait 151 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Total Blocking Time: 125 ms

    125 ms

    Scripts block the page for only 125 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix78
  • Page weight: 3.2 MB in 74 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 74 requests on a phone: scripts 1.6 MB (30), images 570 KiB (15) and other files 347 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

    2 images further down the page (462 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images in older formats

    2 images (462 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.9 g of CO₂ per visit

    0.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8290
  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (11 elements)

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 11 form fields without a label

    11 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3, h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 7562
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (18 characters)

    Your title is only 18 characters: “MatchWithNeighbors”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Explore freely, discreetly, on your terms.” and “It's easy to match”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://matchwithneighbors.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 25 internal links, 1 external

    The homepage links to 25 pages on matchwithneighbors.com and 1 external page.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://matchwithneighbors.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

  • Opted out of AI training for 1 crawler

    robots.txt blocks GPTBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (5,534 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://matchwithneighbors.com/2257 and https://matchwithneighbors.com/anti-trafficking all use the title “CMS Page - MatchWithNeighbors”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://matchwithneighbors.com/agreement, https://matchwithneighbors.com/privacy, https://matchwithneighbors.com/cookies, https://matchwithneighbors.com/pricing, https://matchwithneighbors.com/2257 and https://matchwithneighbors.com/anti-trafficking and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://matchwithneighbors.com/agreement, https://matchwithneighbors.com/privacy, https://matchwithneighbors.com/cookies, https://matchwithneighbors.com/pricing, https://matchwithneighbors.com/2257 and https://matchwithneighbors.com/anti-trafficking and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

    9 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • A 10-field form

    Your longest form asks for 10 fields (8 required). Every extra field lowers completion.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 838 words of copy

    The homepage carries about 838 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start Discreetly”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Start Discreetly”, “Sign Up Now!” and “Pricing”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at matchwithneighbors.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on matchwithneighbors.com, including 18 speed issues, 8 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25