Website review, no card needed
citihardware.com website review
Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 75 checks
This review found 33 issues worth fixing on citihardware.com, 10 of them high impact, across 75 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.9 s |
| May 16, 2026 | 6.0 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.1 s |
| Jun 27, 2026 | 5.3 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.4 s |
| Jul 18, 2026 | 5.5 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 438 ms |
| May 16, 2026 | 429 ms |
| May 23, 2026 | 421 ms |
| May 30, 2026 | 425 ms |
| Jun 6, 2026 | 435 ms |
| Jun 13, 2026 | 444 ms |
| Jun 20, 2026 | 457 ms |
| Jun 27, 2026 | 461 ms |
| Jul 4, 2026 | 457 ms |
| Jul 11, 2026 | 454 ms |
| Jul 18, 2026 | 439 ms |
| Jul 25, 2026 | 406 ms |
| Aug 1, 2026 | 415 ms |
| Aug 8, 2026 | 410 ms |
| Aug 15, 2026 | 403 ms |
| Aug 22, 2026 | 427 ms |
| Aug 29, 2026 | 417 ms |
| Sep 5, 2026 | 396 ms |
| Sep 12, 2026 | 379 ms |
| Sep 19, 2026 | 366 ms |
| Sep 26, 2026 | 354 ms |
| Oct 3, 2026 | 349 ms |
| Oct 10, 2026 | 350 ms |
| Oct 17, 2026 | 342 ms |
| Oct 24, 2026 | 334 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.7 s
Speed
Render-blocking requests
1.0 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Use efficient cache lifetimes
2.8 MB29 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).
Improve image delivery
1.4 MB4 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
760 ms · 427 KiBAbout 427 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 3.2 MB and 602 ms of main-thread time.
Google Tag Manager adds 408 ms
408 msGoogle Tag Manager costs a phone 408 ms of main-thread work and 326 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.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 358 ms. During a long task the page ignores taps.
aliyuncs.com adds 0 ms
0 msaliyuncs.com costs a phone 0 ms of main-thread work and 2.6 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.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 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: 200 ms
200 msYour server sent the HTML in 200 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.55
0.55For real visitors the layout shifts by 0.55 (75th percentile). Good is under 0.1.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to remember your preferred CitiHardware stor…”. Most of its time is element render delay (3.2 s).
Real-user INP: 362 ms
362 msReal visitors wait 362 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 568 ms
568 msScripts block taps and scrolling for 568 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
5 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.
Tap response (INP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 438 ms to 334 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 49% faster for real visitors
-49%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.9 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.1 MB in 142 requests
4.1 MBYour homepage downloads 4.1 MB in 142 requests on a phone: images 2.7 MB (60), scripts 1.2 MB (41) and fonts 70 KiB (2). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 138.6 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
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 0 failed. 4 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 (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
12 internal links, 0 external
The homepage links to 12 pages on citihardware.com and 0 external pages.
6 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “CitiHardware – Your One-Stop Shop For Home Improvement”.
Canonical URL set
The canonical URL is https://citihardware.com/.
Structured data in place
Structured data found: 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://citihardware.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
1%A phone browser shows 1,122 words, but the HTML your server sends has only 15. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://citihardware.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Other pages
1 linked page hidden from search
https://citihardware.com/comparison-list is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://citihardware.com/shop-n-go, whose canonical is https://citihardware.com/shop-n-go/store-list. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://citihardware.com/comparison-list has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://citihardware.com/products, https://citihardware.com/store-locator and https://citihardware.com/shop-n-go 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.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 6 pages we checked loaded without an error.
Every page has a meta description
All 6 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 41 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 1,122 words of copy
The homepage carries about 1,122 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Open contact menu”.
2 calls to action
The homepage has 2 calls to action, for example “Signup” and “Shop & Go”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
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 citihardware.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
- Hosting
- Alibaba Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on citihardware.com, including 20 speed issues, 2 SEO 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.