Website review, no card needed
policyme.com website review
Visit site (opens in a new tab)Reviewed 23 October 202632 issues · 89 checks
This review found 32 issues worth fixing on policyme.com, 6 of them high impact, across 89 checks. The most urgent: improve image delivery. 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 178 ms |
| May 9, 2026 | 175 ms |
| May 16, 2026 | 192 ms |
| May 23, 2026 | 196 ms |
| May 30, 2026 | 213 ms |
| Jun 6, 2026 | 220 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 228 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 222 ms |
| Jul 11, 2026 | 209 ms |
| Jul 18, 2026 | 205 ms |
| Jul 25, 2026 | 198 ms |
| Aug 1, 2026 | 202 ms |
| Aug 8, 2026 | 206 ms |
| Aug 15, 2026 | 201 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 182 ms |
| Sep 5, 2026 | 176 ms |
| Sep 12, 2026 | 171 ms |
| Sep 19, 2026 | 173 ms |
| Sep 26, 2026 | 174 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 170 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.7 s
1.4 s
2.1 s
2.9 s
3.6 s
4.3 s
5.0 s
5.7 s
Speed
Improve image delivery
1.4 s · 546 KiB7 images could be 546 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Use efficient cache lifetimes
900 ms · 630 KiB42 files are served with short cache lifetimes, so returning visitors download them again (630 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Segment, Google Tag Manager and website-files.com and others), adding 2.4 MB and 950 ms of main-thread time.
Reduce unused JavaScript
600 ms · 581 KiBAbout 581 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65 (desktop: 90). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Reduce unused CSS
450 ms · 115 KiBAbout 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Segment adds 253 ms
253 msSegment costs a phone 253 ms of main-thread work and 207 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.
Google Tag Manager adds 209 ms
209 msGoogle Tag Manager costs a phone 209 ms of main-thread work and 473 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.
2,400 HTML elements
The page has 2,400 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
website-files.com adds 100 ms
100 mswebsite-files.com costs a phone 100 ms of main-thread work and 978 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 236 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
Minify JavaScript
34 KiB34 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
13 KiB13 KiB JavaScript is shipped twice across bundles.
Phones get a much slower page than desktops
Desktop scores 90 but mobile only 65. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 55 ms
55 msYour server sent the HTML in 55 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.1 s
9.1 sYour largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.4 s
20.4 sThe page becomes fully interactive after 20.4 s. Good is under 3.8 s.
Largest content (LCP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 221 ms
221 msScripts block taps and scrolling for 221 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 178 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 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: 600 ms
600 msReal visitors wait 600 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 122 requests
2.7 MBYour homepage downloads 2.7 MB in 122 requests on a phone: scripts 1.7 MB (58), images 727 KiB (29) and fonts 104 KiB (3). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
206 KiB3 images are downloaded at several times the size a phone draws them, for example 6a0629592362d476639938a8_d48dfee6ecd27bd13e34d57deeadac25_d7 at 2,130 px wide, shown at 146 px. Resized copies would save about 206 KiB.
2 images in older formats
2 images (114 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.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 53 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (72 characters)
Your title is 72 characters, so Google will cut it off around 60: “PolicyMe Insurance: Life, Health & Dental, Home & Auto, Critical Illness”.
Structured data has 1 problem
Structured data found (LocalBusiness, Organization, Product and WebSite) but with 1 problem, for example “Product: no offers (price) block”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
169 internal links, 12 external
The homepage links to 169 pages on policyme.com and 12 external pages.
6 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Quick insurance quotes with easy online applications for life insurance, home and auto insurance, health insurance, and…”.
One H1 headline
Your main headline reads: “Fast, simple, hassle-free insurance. (Really.)”.
Canonical URL set
The canonical URL is https://www.policyme.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://www.policyme.com/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,719 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.policyme.com/llms.txt (5 KiB, 24 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.policyme.com/life/life/family is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.policyme.com/life/life/family has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.policyme.com/life/life/family, https://www.policyme.com/guaranteed-issue-life-insurance and https://www.policyme.com/life-insurance/provinces have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 83 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 995 words of copy
The homepage carries about 995 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get my quote”.
33 calls to action
The homepage has 33 calls to action, for example “Get my quote”, “Get My Quote” and “Life insurance quote”.
Social proof on the page
Social proof on the homepage: 76 testimonial or review blocks, a star rating, 3 trust badges and “1,500+ reviews”.
Analytics in place
Analytics detected: Meta Pixel and Segment.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Tag Manager, HubSpot, Meta Pixel, Microsoft Ads and Segment (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 policyme.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Analytics
- Segment
Hiring
- Hiring
- 10 open roles
- Teams
- Customer Success (5), Engineering (3), Product (1), Still interested in working with us? Explore our open roles (1)
- Job board
- lever
- Careers page
- www.policyme.com/careers (opens in a new tab)
Company
- Founded
- 2018
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on policyme.com, including 19 speed issues and 3 SEO issues. 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.