Website review, no card needed
numlookup.com website review
Visit site (opens in a new tab)Reviewed 11 October 202620 issues · 74 checks
This review found 20 issues worth fixing on numlookup.com, 3 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.1 s |
| Apr 25, 2026 | 1.1 s |
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 995 ms |
| Aug 29, 2026 | 962 ms |
| Sep 5, 2026 | 932 ms |
| Sep 12, 2026 | 933 ms |
| Sep 19, 2026 | 923 ms |
| Sep 26, 2026 | 942 ms |
| Oct 3, 2026 | 962 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 147 ms |
| Apr 25, 2026 | 151 ms |
| May 2, 2026 | 164 ms |
| May 9, 2026 | 170 ms |
| May 16, 2026 | 175 ms |
| May 23, 2026 | 178 ms |
| May 30, 2026 | 176 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 172 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 182 ms |
| Jul 11, 2026 | 181 ms |
| Jul 18, 2026 | 180 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 184 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 182 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 180 ms |
| Sep 26, 2026 | 183 ms |
| Oct 3, 2026 | 187 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
600 ms · 232 KiB3 files are served with short cache lifetimes, so returning visitors download them again (232 KiB).
Reduce unused JavaScript
150 ms · 288 KiBAbout 288 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 218 ms
218 msGoogle Tag Manager costs a phone 218 ms of main-thread work and 474 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 744 KiB and 361 ms of main-thread time.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96 (desktop: 83). That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 349 ms of it running JavaScript. That is comfortably low.
Server response: 36 ms
36 msYour server sent the HTML in 36 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user INP: 238 ms
238 msReal visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 147 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 7.1 s
7.1 sThe page becomes fully interactive after 7.1 s. Good is under 3.8 s.
Largest Contentful Paint: 2.5 s
2.5 sYour largest element takes 2.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NumLookup is one of the internet's most searched and truste…”.
9 checks passed
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 610 ms
610 msReal visitors wait 610 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 143 ms
143 msScripts block the page for only 143 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Speed Index: 1.1 s
1.1 sVisually, the page fills in at 1.1 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
About 0.2 g of CO₂ per visit
0.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.22 g of CO₂e: 26.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 787 KiB in 15 requests
787 KiBYour homepage downloads 787 KiB in 15 requests on a phone: scripts 740 KiB (6), HTML 44 KiB (1) and other files 3 KiB (6). That is a lean page.
Accessibility
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (45 elements)
All page content should be contained by landmarks: 45 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
Open Graph partly set
Open Graph is missing og:title, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
15 internal links, 6 external
The homepage links to 15 pages on numlookup.com and 6 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Reverse Phone Lookup”.
Title: 47 characters
Your title is a healthy 47 characters: “Reverse Phone Lookup | Free Phone Number Lookup”.
Canonical URL set
The canonical URL is https://www.numlookup.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.numlookup.com/sitemap.xml.
AI search readiness
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://www.numlookup.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.
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 (1,299 words), so crawlers that don't run JavaScript still read it.
Other pages
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.numlookup.com/api, whose canonical is https://www.numlookup.com/reverse-phone-lookup-api. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.numlookup.com/about-us, https://www.numlookup.com/people-search, https://www.numlookup.com/reverse-image-search, https://www.numlookup.com/blog, https://www.numlookup.com/numlookup-vs-spokeo and https://www.numlookup.com/numlookup-vs-whitepages and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://www.numlookup.com/about-us, https://www.numlookup.com/people-search, https://www.numlookup.com/reverse-image-search, https://www.numlookup.com/blog, https://www.numlookup.com/numlookup-vs-spokeo and https://www.numlookup.com/numlookup-vs-whitepages and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 10 pages we checked loaded without an error.
Every page has a meta description
All 10 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 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.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,273 words of copy
The homepage carries about 1,273 words of visible text.
6 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Sign Up” and “Try it on a real number”.
2 short forms
2 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
4 cookies set on arrival
4Opening the homepage sets 4 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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 numlookup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on numlookup.com, including 8 speed issues, 2 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.