Website review, no card needed
higgpublicsector.com website review
Visit site (opens in a new tab)Reviewed 19 October 202645 issues · 86 checks
This review found 45 issues worth fixing on higgpublicsector.com, 21 of them high impact, across 86 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 5.8 s |
| Jul 18, 2026 | 5.9 s |
| Jul 25, 2026 | 5.9 s |
| Aug 1, 2026 | 5.9 s |
| Aug 8, 2026 | 5.6 s |
| Aug 15, 2026 | 5.4 s |
| Aug 22, 2026 | 5.8 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.2 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 677 ms |
| Jul 18, 2026 | 464 ms |
| Jul 25, 2026 | 416 ms |
| Aug 1, 2026 | 419 ms |
| Aug 8, 2026 | 412 ms |
| Aug 15, 2026 | 411 ms |
| Aug 22, 2026 | 361 ms |
| Aug 29, 2026 | 342 ms |
| Sep 5, 2026 | 327 ms |
| Sep 12, 2026 | 324 ms |
| Sep 19, 2026 | 329 ms |
| Sep 26, 2026 | 244 ms |
| Oct 3, 2026 | 228 ms |
| Oct 10, 2026 | 238 ms |
| Oct 17, 2026 | 240 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.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.2 s
3.8 s
4.3 s
Speed
Improve image delivery
29.3 s · 5.5 MB3 images could be 5.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 29.3 s faster on a phone.
Use efficient cache lifetimes
20.7 s · 3.8 MB5 files are served with short cache lifetimes, so returning visitors download them again (3.8 MB).
Reduce unused JavaScript
3.8 s · 662 KiBAbout 662 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Mobile performance score: 72
72/100Your mobile performance score is 72 (desktop: 76). Pages that score under 90 lose visitors before the first paint.
3 third-party services on the page
3 third-party services load with your homepage (redbubble.com, Cloudflare and kerbau28.cloud), adding 6.5 MB and 233 ms of main-thread time.
Render-blocking requests
600 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
kerbau28.cloud adds 0 ms
0 mskerbau28.cloud costs a phone 0 ms of main-thread work and 5.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
300 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
redbubble.com adds 225 ms
225 msredbubble.com costs a phone 225 ms of main-thread work and 865 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.
1,553 HTML elements
The page has 1,553 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
190 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 77 ms of it running JavaScript. That is comfortably low.
Server response: 123 ms
123 msYour server sent the HTML in 123 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.
Largest Contentful Paint: 35.2 s
35.2 sYour largest element takes 35.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Poster, KERBAU28 | Chrome Hearts USA Argentum Nocturne dala…”.
Time to Interactive: 35.2 s
35.2 sThe page becomes fully interactive after 35.2 s. Good is under 3.8 s.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 220 ms
220 msReal visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 91% faster for real visitors
-91%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 2.8 s to 240 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 33 ms
33 msScripts block the page for only 33 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.5 MB in 30 requests
6.5 MBYour homepage downloads 6.5 MB in 30 requests on a phone: images 5.7 MB (5), scripts 797 KiB (21) and stylesheets 69 KiB (2). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 5.4 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
916 KiB1 image is downloaded at several times the size a phone draws it, for example logo28gif.gif at 700 px wide, shown at 180 px. Resized copies would save about 916 KiB.
2 images in older formats
2 images (5.4 MB) 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 1.9 g of CO₂ per visit
1.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.85 g of CO₂e: 222.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
100 text elements with low contrast
100 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
93 tap targets too small
93 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
10 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (5 elements)
Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 14 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “KERBAU28 | Chrome Hearts USA Argentum Nocturne dalam Estetika Gothic Luxury”.
153 internal links, 37 external
The homepage links to 153 pages on higgpublicsector.com and 37 external pages.
7 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “KERBAU28 menelisik pesona Chrome Hearts USA melalui aksen argentum, ornamen gotik, dan nuansa nocturne yang eksentrik s…”.
One H1 headline
Your main headline reads: “KERBAU28 | Chrome Hearts USA Argentum Nocturne dalam Estetika Gothic Luxury”.
Canonical URL set
The canonical URL is https://chromeheartusa.com/.
Structured data in place
Structured data found: Article, BreadcrumbList, FAQPage, Product and WebPage.
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://chromeheartusa.com/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://chromeheartusa.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (1,251 words), so crawlers that don't run JavaScript still read it.
Other pages
15 linked pages are broken
Your homepage links to https://chromeheartusa.com/shop/funny+t-shirts, https://chromeheartusa.com/shop/vintage, https://chromeheartusa.com/shop/music, https://chromeheartusa.com/g/fresh-finds, https://chromeheartusa.com/g/fan-art and https://chromeheartusa.com/g/t-shirts and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 103 found) and read each the way a search engine does.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.redbubble.com/frontend-static/_next/static/media/thumb-up.2469e626.svg.
97 small tap targets
97 of 106 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “missing ) after argument list”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 1,251 words of copy
The homepage carries about 1,251 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
2 short forms
2 short forms (5 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 36 testimonial or review blocks, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
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.
3 other companies contacted
Loading the homepage contacts 3 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 higgpublicsector.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on higgpublicsector.com, including 19 speed issues, 1 SEO issue 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.