Website review, no card needed
sigmamotors.pk website review
Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 90 checks
This review found 41 issues worth fixing on sigmamotors.pk, 19 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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
68D- #111,028 of 126,661 reviewed websitesbeats 10%
- #65,724 of 70,542 online storesbeats 5%
- #2,508 of 2,978 WooCommerce storesbeats 12%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 6.6 s |
| May 9, 2026 | 7.0 s |
| May 16, 2026 | 7.5 s |
| May 23, 2026 | 8.6 s |
| May 30, 2026 | 8.4 s |
| Jun 6, 2026 | 8.4 s |
| Jun 13, 2026 | 7.8 s |
| Jun 20, 2026 | 7.5 s |
| Jun 27, 2026 | 6.7 s |
| Jul 4, 2026 | 6.1 s |
| Jul 11, 2026 | 5.5 s |
| Jul 18, 2026 | 5.5 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.3 s |
| Aug 8, 2026 | 6.7 s |
| Aug 15, 2026 | 6.7 s |
| Aug 22, 2026 | 6.3 s |
| Aug 29, 2026 | 6.3 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 5.7 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.5 s |
| Oct 3, 2026 | 5.4 s |
| Oct 10, 2026 | 5.4 s |
| Oct 17, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 135 ms |
| May 9, 2026 | 131 ms |
| May 16, 2026 | 130 ms |
| May 23, 2026 | 140 ms |
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 133 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 119 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 118 ms |
| Oct 17, 2026 | 116 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
Speed
Render-blocking requests
5.6 s93 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.6 s.
Improve image delivery
2.6 s · 2.7 MB18 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 693 KiB222 files are served with short cache lifetimes, so returning visitors download them again (693 KiB).
Reduce unused JavaScript
1.1 s · 208 KiBAbout 208 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
900 ms · 165 KiBAbout 165 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Minify JavaScript
300 ms · 49 KiB49 KiB could be saved by minifying JavaScript.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 690 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,934 HTML elements
The page has 1,934 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.
3 third-party services on the page
3 third-party services load with your homepage (trustindex.io, hostinger.com and Google Fonts), adding 79 KiB and 13 ms of main-thread time.
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 114 ms
114 msYour server sent the HTML in 114 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 LCP: 9.6 s
9.6 sReal visitors wait 9.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.37
0.37For real visitors the layout shifts by 0.37 (75th percentile). Good is under 0.1.
Real-user FCP: 5.2 s
5.2 sReal visitors see the first content after 5.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.2 s
3.2 sReal visitors wait 3.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 16.9 s
16.9 sYour largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 17.2 s
17.2 sThe page becomes fully interactive after 17.2 s. Good is under 3.8 s.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.404
0.404The layout shifts by 0.404 while loading, so content jumps under the reader's thumb. Good is under 0.1.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 135 ms to 116 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 6.6 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 44 ms
44 msScripts block the page for only 44 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.7 MB in 231 requests
6.7 MBYour homepage downloads 6.7 MB in 231 requests on a phone: images 5.2 MB (39), scripts 744 KiB (94) and stylesheets 377 KiB (87). Under 2 MB keeps phones on slow connections fast.
13 images in older formats
13 images (831 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.
11 images below the first screen load straight away
11 images further down the page (506 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
141 KiB1 image is downloaded at several times the size a phone draws it, for example Untitled-design-2026-01-28T155543.350.png at 512 px wide, shown at 76 px. Resized copies would save about 141 KiB.
About 1.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 226.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA attributes must conform to valid values (3 elements)
ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (79 elements)
All page content should be contained by landmarks: 79 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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
13 form fields without a label
13 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (12 characters)
Your title is only 12 characters: “Sigma Motors”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“SIGMA MOTORS” and “Japanese Car Imports”). One clear main headline is easier for people and search engines.
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.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
40 internal links, 7 external
The homepage links to 40 pages on sigmamotors.pk and 7 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://sigmamotors.pk/.
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://sigmamotors.pk/wp-sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://sigmamotors.pk/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.
Text is in the HTML
Your server sends the page's text in the HTML (515 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://sigmamotors.pk/inventory, https://sigmamotors.pk/our-team, https://sigmamotors.pk/blogs, https://sigmamotors.pk/contact-us and https://sigmamotors.pk/about-us have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages slow to respond
https://sigmamotors.pk/inventory, https://sigmamotors.pk/our-team, https://sigmamotors.pk/blogs and https://sigmamotors.pk/contact-us took over 3 s to send their HTML from our server.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 5 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
14 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 456 words of copy
The homepage carries about 456 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”.
14 calls to action
The homepage has 14 calls to action, for example “Contact Us”, “Get in Touch” and “Call or Whatsapp +92 322 4184218”.
3 short forms
3 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks and 1 customer or partner logo.
Direct contact links
Visitors can reach you directly: 7 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 sigmamotors.pk, 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
- Framework
- React
- E-commerce
- WooCommerce
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on sigmamotors.pk, including 20 speed issues, 6 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.