Website review, no card needed

gempundit.com logo

gempundit.com website review

Visit site (opens in a new tab)Reviewed 21 October 202623 issues · 72 checks

This review found 23 issues worth fixing on gempundit.com, 7 of them high impact, across 72 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.2 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
297 ms271 msMay 2Oct 17294 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026277 ms
May 9, 2026278 ms
May 16, 2026275 ms
May 23, 2026274 ms
May 30, 2026277 ms
Jun 6, 2026277 ms
Jun 13, 2026278 ms
Jun 20, 2026274 ms
Jun 27, 2026274 ms
Jul 4, 2026277 ms
Jul 11, 2026278 ms
Jul 18, 2026278 ms
Jul 25, 2026278 ms
Aug 1, 2026278 ms
Aug 8, 2026278 ms
Aug 15, 2026279 ms
Aug 22, 2026279 ms
Aug 29, 2026279 ms
Sep 5, 2026280 ms
Sep 12, 2026282 ms
Sep 19, 2026284 ms
Sep 26, 2026286 ms
Oct 3, 2026292 ms
Oct 10, 2026293 ms
Oct 17, 2026294 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

Full-page screenshot of gempundit.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gempundit.com at 0.5 s0.5 s
  2. gempundit.com at 0.9 s0.9 s
  3. gempundit.com at 1.4 s1.4 s
  4. gempundit.com at 1.8 s1.8 s
  5. gempundit.com at 2.3 s2.3 s
  6. gempundit.com at 2.7 s2.7 s
  7. gempundit.com at 3.2 s3.2 s
  8. gempundit.com at 3.6 s3.6 s

Speed

2 to fix86
  • Mobile performance score: 86

    86/100

    Your mobile performance score is 86 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • 1,937 HTML elements

    The page has 1,937 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    84 KiB

    1 image could be 84 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and imgeng.in), adding 175 KiB and 0 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 26 ms of it running JavaScript. That is comfortably low.

  • Server response: 62 ms

    62 ms

    Your server sent the HTML in 62 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix67
  • 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.

  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Find Your Right Gemstone By Gemstone By Purpose Select Gems…”.

  • Real-user INP: 234 ms

    234 ms

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Time to Interactive: 4.3 s

    4.3 s

    The page becomes fully interactive after 4.3 s. Good is under 3.8 s.

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

7 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.007

    0.007

    The layout barely moves while loading (CLS 0.007, good is under 0.1).

  • Speed Index: 1.3 s

    1.3 s

    Visually, the page fills in at 1.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.15 g

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

1 checks passed
  • Page weight: 560 KiB in 43 requests

    560 KiB

    Your homepage downloads 560 KiB in 43 requests on a phone: images 260 KiB (32), fonts 212 KiB (8) and HTML 87 KiB (1). That is a lean page.

Accessibility

8 to fixGoogle 5863
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 13 text elements with low contrast

    13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

1 checks passed
  • 8 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 11 WCAG 2.2 A/AA and best-practice rules on the phone render: 8 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7780
  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “Buy Gemstones Online: Loose Gemstones for sale - Best Gemstones Prices | GemPundit”.

  • Meta description is long (185 characters)

    Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, LocalBusiness, Organization and WebSite) but with 2 problems, for example “BreadcrumbList: itemListElement is an empty list”.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 475 internal links, 20 external

    The homepage links to 475 pages on gempundit.com and 20 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Buy Gemstones Online”.

  • Canonical URL set

    The canonical URL is https://www.gempundit.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://gempundit.com/sitemapxml/sitemap_index.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • llms.txt published

    The site publishes https://www.gempundit.com/llms.txt (107 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 3 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix85
  • 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.

  • Only about 5 words

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

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

8 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Talk to an Astrologer”, “Shop Pairs” and “SHOP NOW”.

  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks, 2 customer or partner logos and 8 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 17 phone links 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.

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 gempundit.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on gempundit.com, including 7 speed issues, 5 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25