angel.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 2.7 s

  2.7 s

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

• Real-user INP: 271 ms

  271 ms

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

• Real-user FCP: 2.2 s

  2.2 s

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

• Real-user TTFB: 804 ms

  804 ms

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

• Tap response (INP) held steady for real visitors

  -4%

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

• Page weight: 3.6 MB

  3.6 MB

  Your homepage downloads 3.6 MB on a phone, 514 KiB of it images (14%). Under 2 MB keeps phones on slow connections fast.

• About 1.0 g of CO₂ per visit

  1.01 g

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

• 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.

  Elements (2)

• Headings skip levels

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

  View sourceElements (3)

• 66 internal links, 14 external

  The homepage links to 66 pages on angel.com and 14 external pages.

• 1 page without an H1

  /watch/dry-bar-best-of has no <h1> headline, so visitors and search engines get no clear main topic.

• 5 pages slow to respond

  /category/free, /category/sports, /category/faith-based, /tickets and /guild/impact took over 3 s to send their HTML from our server.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.

• 2 broken images

  2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187014997&Ver=2&mid=0586530a-164e-4513-80a7-e3562c101f96&bo=1&sid=23b440e0c5d611f18d4da372397f03d3&vid=23b4ddc0c5d611f194356d63de861225&vids=1&msclkid=N&pi=918639831&l.

• 4 JavaScript errors while loading

  4 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message …”.

• 2 redirects before the homepage

  Opening https://angel.com goes through 2 redirects before the homepage loads.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• DNSSEC is off

  angel.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• 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 analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• 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.

• About 795 words of copy

  The homepage carries about 795 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• SPF does not block other senders (?all)

  Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:one.zoho.com include:servers.mcsv.net include:shops.…”.

• Email authentication score: 75/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 11 trackers load before any consent

  11

  Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 6 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

• 38 cookies set on arrival

  38

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

• 47 other companies contacted

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