Website review, no card needed
pcjeweller.com website review
Visit site (opens in a new tab)Reviewed 31 October 202648 issues · 91 checks
This review found 48 issues worth fixing on pcjeweller.com, 21 of them high impact, across 91 checks. The most urgent: improve image delivery. 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) |
|---|---|
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 233 ms |
| May 16, 2026 | 237 ms |
| May 23, 2026 | 244 ms |
| May 30, 2026 | 260 ms |
| Jun 6, 2026 | 261 ms |
| Jun 13, 2026 | 250 ms |
| Jun 20, 2026 | 242 ms |
| Jun 27, 2026 | 230 ms |
| Jul 4, 2026 | 226 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 225 ms |
| Jul 25, 2026 | 237 ms |
| Aug 1, 2026 | 253 ms |
| Aug 8, 2026 | 280 ms |
| Aug 15, 2026 | 304 ms |
| Aug 22, 2026 | 301 ms |
| Aug 29, 2026 | 292 ms |
| Sep 5, 2026 | 285 ms |
| Sep 12, 2026 | 286 ms |
| Sep 19, 2026 | 287 ms |
| Sep 26, 2026 | 303 ms |
| Oct 3, 2026 | 316 ms |
| Oct 10, 2026 | 319 ms |
| Oct 17, 2026 | 322 ms |
| Oct 24, 2026 | 319 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
Improve image delivery
9.4 s · 22.6 MB114 images could be 22.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.4 s faster on a phone.
Use efficient cache lifetimes
10.1 s · 20.2 MB137 files are served with short cache lifetimes, so returning visitors download them again (20.2 MB).
Reduce unused JavaScript
1.4 s · 251 KiBAbout 251 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,663 HTML elements
The page has 4,663 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and Google/Doubleclick Ads and others), adding 25.7 MB and 561 ms of main-thread time.
digitaloceanspaces.com adds 0 ms
0 msdigitaloceanspaces.com costs a phone 0 ms of main-thread work and 25.3 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.
Render-blocking requests
600 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Google Tag Manager adds 484 ms
484 msGoogle Tag Manager costs a phone 484 ms of main-thread work and 356 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 418 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 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 CLS: 0.50
0.50For real visitors the layout shifts by 0.50 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 28.6 s
28.6 sYour largest element takes 28.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner”.
Time to Interactive: 29.1 s
29.1 sThe page becomes fully interactive after 29.1 s. Good is under 3.8 s.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user INP: 348 ms
348 msReal visitors wait 348 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 233 ms to 319 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 788 ms
788 msReal visitors wait 788 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 29.8 MB in 338 requests
29.8 MBYour homepage downloads 29.8 MB in 338 requests on a phone: images 28.4 MB (210), scripts 1.0 MB (59) and other files 108 KiB (57). Under 2 MB keeps phones on slow connections fast.
40 images far larger than shown
9.1 MB40 images are downloaded at several times the size a phone draws them, for example GR01506B-3.webp at 4,000 px wide, shown at 177 px. Resized copies would save about 9.1 MB.
1 image over 500 KB
GR01506B-3.webp weighs 1.0 MB. On a phone connection a single image that size takes seconds.
9 images below the first screen load straight away
9 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (412 KiB) are 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 8.4 g of CO₂ per visit
8.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.43 g of CO₂e: 1011.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
28 buttons without a name
28 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (3 elements)
Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.
ARIA role should be appropriate for the element (101 elements)
ARIA role should be appropriate for the element: 101 elements on the page fail this check, rated minor by axe-core.
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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 76 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 10 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.
Meta description is long (182 characters)
Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.
38 internal links, 23 external
The homepage links to 38 pages on pcjeweller.com and 23 external pages.
6 checks passed
Title: 64 characters
Your title is a healthy 64 characters: “PC Jeweller | Gold, Diamond & Silver Jewellery Collection Online”.
Canonical URL set
The canonical URL is https://www.pcjeweller.com/.
Structured data in place
Structured data found: JewelryStore and Organization.
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://www.pcjeweller.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
39%The HTML your server sends has 188 of the 483 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.pcjeweller.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.
2 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.
Other pages
11 pages share a title
https://www.pcjeweller.com/about-Us, https://www.pcjeweller.com/why-choose-us, https://www.pcjeweller.com/contact-us, https://www.pcjeweller.com/faqs, https://www.pcjeweller.com/refund-and-exchange-policy and https://www.pcjeweller.com/cancellation-policy and 5 others all use the title “PCJ Jewellers - Diamond & Gold Jewellery”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages share a meta description
https://www.pcjeweller.com/about-Us, https://www.pcjeweller.com/why-choose-us, https://www.pcjeweller.com/contact-us, https://www.pcjeweller.com/faqs, https://www.pcjeweller.com/refund-and-exchange-policy and https://www.pcjeweller.com/cancellation-policy and 5 others use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.pcjeweller.com/jewellery/diamond, whose canonical is https://www.pcjeweller.com/jewellery. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages without an H1
https://www.pcjeweller.com/about-Us, https://www.pcjeweller.com/why-choose-us, https://www.pcjeweller.com/contact-us, https://www.pcjeweller.com/faqs, https://www.pcjeweller.com/refund-and-exchange-policy and https://www.pcjeweller.com/cancellation-policy and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.pcjeweller.com/jewellery/mangalsutra and https://www.pcjeweller.com/jewellery/diamond have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
103 small tap targets
103 of 328 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 404 ()”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
About 483 words of copy
The homepage carries about 483 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “Book Appointment”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “Buy Back Policy” and “Track Your Order”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
15 other companies contacted
Loading the homepage contacts 15 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 pcjeweller.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- DigitalOcean
Company
- Founded
- 2005
- Headquarters
- New Delhi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on pcjeweller.com, including 20 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.