Website review, no card needed
canonpk.com website review
Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 93 checks
This review found 39 issues worth fixing on canonpk.com, 17 of them high impact, across 93 checks. The most urgent: main-thread work: 13.4 s. 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
75C- #79,069 of 120,386 reviewed websitesbeats 30%
- #50,430 of 68,150 online storesbeats 22%
- #47,651 of 62,105 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 197 ms |
| May 9, 2026 | 202 ms |
| May 16, 2026 | 206 ms |
| May 23, 2026 | 209 ms |
| May 30, 2026 | 212 ms |
| Jun 6, 2026 | 218 ms |
| Jun 13, 2026 | 220 ms |
| Jun 20, 2026 | 224 ms |
| Jun 27, 2026 | 228 ms |
| Jul 4, 2026 | 229 ms |
| Jul 11, 2026 | 233 ms |
| Jul 18, 2026 | 233 ms |
| Jul 25, 2026 | 230 ms |
| Aug 1, 2026 | 231 ms |
| Aug 8, 2026 | 235 ms |
| Aug 15, 2026 | 240 ms |
| Aug 22, 2026 | 248 ms |
| Aug 29, 2026 | 251 ms |
| Sep 5, 2026 | 251 ms |
| Sep 12, 2026 | 254 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 270 ms |
| Oct 3, 2026 | 293 ms |
| Oct 10, 2026 | 310 ms |
| Oct 17, 2026 | 332 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
2.2 s
4.3 s
6.5 s
8.6 s
10.8 s
12.9 s
15.1 s
17.3 s
Speed
Main-thread work: 13.4 s
A phone's processor spends 13.4 s on main-thread work while loading, 7.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,846 HTML elements
The page has 4,846 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 (Shopify, Google Tag Manager and Clarity and others), adding 2.6 MB and 2.1 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Shopify adds 731 ms
731 msShopify costs a phone 731 ms of main-thread work and 1.1 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.
Google Tag Manager adds 554 ms
554 msGoogle Tag Manager costs a phone 554 ms of main-thread work and 1.1 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.
Clarity adds 455 ms
455 msClarity costs a phone 455 ms of main-thread work and 30 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 419 ms. During a long task the page ignores taps.
Facebook adds 393 ms
393 msFacebook costs a phone 393 ms of main-thread work and 228 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.
Use efficient cache lifetimes
213 KiB5 files are served with short cache lifetimes, so returning visitors download them again (213 KiB).
Improve image delivery
125 KiB8 images could be 125 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
100 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.
Reduce unused CSS
80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
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: 11 ms
11 msYour server sent the HTML in 11 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.
Time to Interactive: 24.4 s
24.4 sThe page becomes fully interactive after 24.4 s. Good is under 3.8 s.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 839 ms
839 msScripts block taps and scrolling for 839 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 377 ms
377 msReal visitors wait 377 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 61% slower for real visitors
+61%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 197 ms to 332 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
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.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
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: 686 ms
686 msReal visitors wait 686 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 422 requests
5.1 MBYour homepage downloads 5.1 MB in 422 requests on a phone: scripts 2.6 MB (84), other files 1.2 MB (232) and images 948 KiB (60). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 172.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Hidden but focusable
84 elements hidden from screen readers can still receive keyboard focus.
35 text elements with low contrast
35 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.
Orphan list items
Some list items are not inside a list.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
294 links without text
294 visible links have no text or label, so screen readers cannot say where they go.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 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.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
40 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: 40 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
330 internal links, 6 external
The homepage links to 330 pages on canonpk.com and 6 external pages.
8 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Shop Canon range of premium home appliances in Pakistan—cookers, coolers, heaters & more. Reliable quality since 1972, …”.
One H1 headline
Your main headline reads: “Canon Home Appliances”.
Title: 57 characters
Your title is a healthy 57 characters: “Buy Canon Home Appliances Pakistan – Quality & Innovation”.
Canonical URL set
The canonical URL is https://canonpk.com/.
Structured data in place
Structured data found: HomeGoodsStore, Organization and WebSite.
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://canonpk.com/sitemap.xml.
AI search readiness
4 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 (1,308 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://canonpk.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages share a meta description
https://canonpk.com/collections/new-arrivals, https://canonpk.com/collections/ac, https://canonpk.com/collections/air-fryer/New-Arrivals, https://canonpk.com/collections/electric-pressure-cooker, https://canonpk.com/collections/coffee-maker and https://canonpk.com/collections/electric-cookers and 8 others use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://canonpk.com/collections/air-fryer/New-Arrivals, whose canonical is https://canonpk.com/collections/air-fryer/new-arrivals. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://canonpk.com/collections/new-arrivals, https://canonpk.com/collections/ac, https://canonpk.com/collections/air-fryer/New-Arrivals, https://canonpk.com/collections/electric-pressure-cooker, https://canonpk.com/collections/coffee-maker and https://canonpk.com/collections/electric-cookers and 9 others 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 143 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Unexpected end of input”.
2 checks passed
Tap targets are thumb-sized
55 of 59 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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.
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 671 words of copy
The homepage carries about 671 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop”.
7 calls to action
The homepage has 7 calls to action, for example “Contact Us”, “Shop Now” and “Shop now”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
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.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
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 canonpk.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on canonpk.com, including 18 speed issues and 3 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.