charming.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: 5.7 s

  5.7 s

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

• Real-user FCP: 5.3 s

  5.3 s

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

• Real-user TTFB: 4.2 s

  4.2 s

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

• Real-user INP: 286 ms

  286 ms

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

• Tap response (INP) held steady for real visitors

  -6%

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

• Largest content (LCP) got 12% slower for real visitors

  +12%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.3 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 2.2 MB

  2.2 MB

  Your homepage downloads 2.2 MB on a phone, 151 KiB of it images (7%). Under 2 MB keeps phones on slow connections fast.

• About 0.6 g of CO₂ per visit

  0.62 g

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

• 1 form field without a label

  1 form field has no label, so screen readers announce an empty box and autofill guesses.

  View source

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

• Title is short (26 characters)

  Your title is only 26 characters: “Charming.com | Markmonitor”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No XML sitemap

  No XML sitemap at https://www.markmonitor.com/sitemap_index.xml, so Google discovers your pages only by following links.

• 25 internal links, 9 external

  The homepage links to 25 pages on charming.com and 9 external pages.

• No llms.txt

  There is no /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.

• 5 pages without a meta description

  /category/blog, /category/datasheet, /category/news, /category/report and /category/webinar have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (5)

• 15 internal pages checked

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

• 10 small tap targets

  10 of 20 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 “Failed to load resource: net::ERR_FAILED”.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

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

• DNSSEC is off

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

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• A 13-field form

  Your longest form asks for 13 fields (11 required). Every extra field lowers completion.

  View source

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

• Only about 138 words

  The homepage has only about 138 words of visible text; thin pages give Google and first-time buyers little to go on.

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

• No DMARC policy

  charming.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• No SPF record

  charming.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Domain receives no email

  charming.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

• Email authentication score: 0/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.

• 5 cookies set on arrival

  5

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

• 10 other companies contacted

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