Website review, no card needed
invoicehome.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 invoicehome.com, 2 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
90AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 933 ms |
| Apr 25, 2026 | 912 ms |
| May 2, 2026 | 908 ms |
| May 9, 2026 | 915 ms |
| May 16, 2026 | 923 ms |
| May 23, 2026 | 929 ms |
| May 30, 2026 | 934 ms |
| Jun 6, 2026 | 930 ms |
| Jun 13, 2026 | 930 ms |
| Jun 20, 2026 | 922 ms |
| Jun 27, 2026 | 914 ms |
| Jul 4, 2026 | 912 ms |
| Jul 11, 2026 | 908 ms |
| Jul 18, 2026 | 902 ms |
| Jul 25, 2026 | 900 ms |
| Aug 1, 2026 | 899 ms |
| Aug 8, 2026 | 898 ms |
| Aug 15, 2026 | 903 ms |
| Aug 22, 2026 | 904 ms |
| Aug 29, 2026 | 903 ms |
| Sep 5, 2026 | 902 ms |
| Sep 12, 2026 | 896 ms |
| Sep 19, 2026 | 895 ms |
| Sep 26, 2026 | 891 ms |
| Oct 3, 2026 | 890 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 59 ms |
| Apr 25, 2026 | 58 ms |
| May 2, 2026 | 58 ms |
| May 9, 2026 | 59 ms |
| May 16, 2026 | 62 ms |
| May 23, 2026 | 65 ms |
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 73 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 74 ms |
| Jul 11, 2026 | 74 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 74 ms |
| Aug 1, 2026 | 75 ms |
| Aug 8, 2026 | 75 ms |
| Aug 15, 2026 | 76 ms |
| Aug 22, 2026 | 75 ms |
| Aug 29, 2026 | 74 ms |
| Sep 5, 2026 | 74 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 73 ms |
| Sep 26, 2026 | 74 ms |
| Oct 3, 2026 | 73 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
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 88
88/100Your mobile performance score is 88 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 60 KiBAbout 60 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
150 ms · 119 KiB5 images could be 119 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Clarity and Google/Doubleclick Ads and others), adding 229 KiB and 184 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.
Document request latency
27 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
10 KiB1 file is served with short cache lifetimes, so returning visitors download them again (10 KiB).
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 189 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 59 ms to 73 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “create an invoice now”.
Time to Interactive: 5.0 s
5.0 sThe page becomes fully interactive after 5.0 s. Good is under 3.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
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 INP: 53 ms
53 msReal visitors wait 53 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 655 ms
655 msReal visitors wait 655 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.1 s
2.1 sVisually, the page fills in at 2.1 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
4 images below the first screen load straight away
4 images further down the page (146 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.20 g of CO₂e: 24.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 740 KiB in 49 requests
740 KiBYour homepage downloads 740 KiB in 49 requests on a phone: images 419 KiB (32), scripts 245 KiB (7) and HTML 43 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Corporation) but with 1 problem, for example “Corporation: missing name”.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
52 internal links, 12 external
The homepage links to 52 pages on invoicehome.com and 12 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Create and send invoices as a PDF attachment using over 100 professional invoice templates. Email invoices directly, ge…”.
One H1 headline
Your main headline reads: “100 Free Invoice Templates | Print & Email Invoices”.
Title: 51 characters
Your title is a healthy 51 characters: “100 Free Invoice Templates | Print & Email Invoices”.
Canonical URL set
The canonical URL is https://invoicehome.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://invoicehome.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://invoicehome.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives url, logo, sameAs (social profiles) and description; name and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (872 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://invoicehome.com/terms and https://invoicehome.com/privacy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://invoicehome.com/invoice/new, whose canonical is https://invoicehome.com/signin. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://invoicehome.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://invoicehome.com/invoice/new, https://invoicehome.com/signup and https://invoicehome.com/sitemap 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.invoicehome.com/assets/homepage-094084a8364d47cd9764c7028ad9e911a45ae0d52cb…”.
1 checks passed
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 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.
Thin social proof
Social proof on the homepage: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 867 words of copy
The homepage carries about 867 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Sign Up” and “Contact Us”.
Analytics in place
Analytics detected: Google Analytics.
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 Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
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 invoicehome.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 invoicehome.com, including 7 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.