Website review, no card needed
mypoints.com website review
Visit site (opens in a new tab)Reviewed 11 October 202636 issues · 69 checks
This review found 36 issues worth fixing on mypoints.com, 16 of them high impact, across 69 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.8 s |
| Apr 25, 2026 | 2.8 s |
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 136 ms |
| Apr 25, 2026 | 136 ms |
| May 2, 2026 | 136 ms |
| May 9, 2026 | 135 ms |
| May 16, 2026 | 136 ms |
| May 23, 2026 | 136 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 140 ms |
| Aug 15, 2026 | 141 ms |
| Aug 22, 2026 | 143 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 148 ms |
| Sep 26, 2026 | 152 ms |
| Oct 3, 2026 | 154 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
4.6 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.6 s.
Reduce unused JavaScript
2.4 s · 448 KiBAbout 448 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Use efficient cache lifetimes
950 ms · 188 KiB6 files are served with short cache lifetimes, so returning visitors download them again (188 KiB).
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 59). Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
450 ms · 183 KiBPolyfills for old browsers add 183 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 295 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (prdgsvc.com, equalweb.com and Cloudflare and others), adding 257 KiB and 211 ms of main-thread time.
Reduce unused CSS
150 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
187 KiB5 images could be 187 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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 LCP: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.72
0.72For real visitors the layout shifts by 0.72 (75th percentile). Good is under 0.1.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Earn Points to redeem for Free Gift Card Rewards Join Now F…”.
First Contentful Paint: 6.0 s
6.0 sThe first text or image appears after 6.0 s on a phone. Good is under 1.8 s.
Time to Interactive: 10.6 s
10.6 sThe page becomes fully interactive after 10.6 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 379 ms
379 msScripts block taps and scrolling for 379 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 136 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 722 ms
722 msReal visitors wait 722 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.059
0.059The layout barely moves while loading (CLS 0.059, good is under 0.1).
Images and page weight
Page weight: 2.3 MB in 103 requests
2.3 MBYour homepage downloads 2.3 MB in 103 requests on a phone: scripts 1.2 MB (40), images 680 KiB (24) and other files 310 KiB (23). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
46 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: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 short (36 characters)
Your meta description is only 36 characters: “MyPoints: Your Daily Rewards Program”. 70 to 160 characters is enough to sell the click.
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.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
3 checks passed
Title: 36 characters
Your title is a healthy 36 characters: “MyPoints: Your Daily Rewards Program”.
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.mypoints.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 363 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.mypoints.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.
1 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.
Best practices
2 small tap targets
2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 363 words of copy
The homepage carries about 363 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join Now”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
7 other companies contacted
Loading the homepage contacts 7 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 mypoints.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 36 issues on mypoints.com, including 15 speed issues, 6 SEO issues and 3 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.