Website review, no card needed

caratlane.com logo

caratlane.com website review

Visit site (opens in a new tab)Reviewed 27 October 202643 issues · 81 checks

This review found 43 issues worth fixing on caratlane.com, 17 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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.8 s2.3 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20262.6 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.3 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.4 s
Aug 8, 20263.1 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
650 ms468 msMay 9Oct 24607 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026605 ms
May 16, 2026629 ms
May 23, 2026605 ms
May 30, 2026579 ms
Jun 6, 2026577 ms
Jun 13, 2026578 ms
Jun 20, 2026581 ms
Jun 27, 2026591 ms
Jul 4, 2026592 ms
Jul 11, 2026594 ms
Jul 18, 2026597 ms
Jul 25, 2026593 ms
Aug 1, 2026583 ms
Aug 8, 2026560 ms
Aug 15, 2026522 ms
Aug 22, 2026503 ms
Aug 29, 2026491 ms
Sep 5, 2026489 ms
Sep 12, 2026499 ms
Sep 19, 2026510 ms
Sep 26, 2026526 ms
Oct 3, 2026544 ms
Oct 10, 2026567 ms
Oct 17, 2026593 ms
Oct 24, 2026607 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 caratlane.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. caratlane.com at 0.7 s0.7 s
  2. caratlane.com at 1.5 s1.5 s
  3. caratlane.com at 2.2 s2.2 s
  4. caratlane.com at 2.9 s2.9 s
  5. caratlane.com at 3.6 s3.6 s
  6. caratlane.com at 4.4 s4.4 s
  7. caratlane.com at 5.1 s5.1 s
  8. caratlane.com at 5.8 s5.8 s

Speed

9 to fix46
  • Use efficient cache lifetimes

    3.5 s · 666 KiB

    7 files are served with short cache lifetimes, so returning visitors download them again (666 KiB).

  • Reduce unused JavaScript

    2.1 s · 649 KiB

    About 649 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Improve image delivery

    2.1 s · 393 KiB

    3 images could be 393 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46 (desktop: 49). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, cltstatic.com and Google/Doubleclick Ads and others), adding 2.2 MB and 918 ms of main-thread time.

  • cltstatic.com adds 424 ms

    424 ms

    cltstatic.com costs a phone 424 ms of main-thread work and 1.5 MB 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.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 513 ms. During a long task the page ignores taps.

  • Google Tag Manager adds 455 ms

    455 ms

    Google Tag Manager costs a phone 455 ms of main-thread work and 527 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.

  • Main-thread work: 3.0 s

    A phone's processor spends 3.0 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • 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: 590 ms

    590 ms

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

Core Web Vitals

11 to fix0
  • 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.2 s

    4.2 s

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

  • Real-user INP: 1.0 s

    1.0 s

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

  • Real-user CLS: 0.93

    0.93

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

  • Largest Contentful Paint: 12.9 s

    12.9 s

    Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FLAT 20 X 3 BANKS”.

  • Time to Interactive: 16.2 s

    16.2 s

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

  • Total Blocking Time: 767 ms

    767 ms

    Scripts block taps and scrolling for 767 ms in total while the page loads. Good is under 200 ms.

  • Real-user TTFB: 961 ms

    961 ms

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

  • Speed Index: 5.5 s

    5.5 s

    Visually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.8 s

    2.8 s

    The first text or image appears after 2.8 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image 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-24, real Chrome visitors' tap response (inp) went from 605 ms to 607 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +13%

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

2 checks passed
  • 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.

  • Cumulative Layout Shift: 0.068

    0.068

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 132 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 132 requests on a phone: scripts 1.5 MB (53), images 678 KiB (30) and fonts 412 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (162 KiB) is 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.76 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 7489
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 7 text elements with low contrast

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

  • 4 tap targets too small

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

  • 2 images without alt text

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

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9281
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “CaratLane - A TATA Product | Best Store for Online Jewellery Shopping”.

  • Meta description is long (172 characters)

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

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

  • No XML sitemap

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 210 internal links, 10 external

    The homepage links to 210 pages on caratlane.com and 10 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “CaratLane - A TATA Product”.

  • Canonical URL set

    The canonical URL is https://www.caratlane.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no https://www.caratlane.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.

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: 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 (608 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 1 linked page hidden from search

    https://www.caratlane.com/gold-rate 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.caratlane.com/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.caratlane.com/stores, whose canonical is https://www.caratlane.com/www.caratlane.com/stores. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://www.caratlane.com/wishlist, https://www.caratlane.com/diamond-buying-guide, https://www.caratlane.com/jewellery-buying-guide, https://www.caratlane.com/gemstone-buying-guide, https://www.caratlane.com/returns-exchanges and https://www.caratlane.com/customer-service/shipping-policy 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 189 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 to fixGoogle 9677
  • 64 small tap targets

    64 of 68 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • 11 distorted images

    11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 368 words of copy

    The homepage carries about 368 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Sign Up” and “ORDER STATUS”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 4 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Outbrain (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 15 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 caratlane.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
WordPress
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on caratlane.com, including 20 speed issues, 4 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