Programmable

Website review, no card needed

pacifichoods.com logo

pacifichoods.com website review

Visit site (opens in a new tab)Reviewed 11 November 202614 issues · 71 checks

This review found 14 issues worth fixing on pacifichoods.com, 3 of them high impact, across 71 checks. The most urgent: hidden but focusable. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

94A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.5 s491 msMay 23Nov 7825 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026838 ms
May 30, 2026813 ms
Jun 6, 2026786 ms
Jun 13, 2026812 ms
Jun 20, 2026805 ms
Jun 27, 2026850 ms
Jul 4, 2026803 ms
Jul 11, 2026744 ms
Jul 18, 2026754 ms
Jul 25, 2026792 ms
Aug 1, 2026935 ms
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.3 s
Sep 5, 2026952 ms
Sep 12, 2026837 ms
Sep 19, 2026760 ms
Sep 26, 2026690 ms
Oct 3, 2026630 ms
Oct 10, 2026609 ms
Oct 17, 2026676 ms
Oct 24, 2026757 ms
Oct 31, 2026797 ms
Nov 7, 2026825 ms
Real-visitor tap response (INP)75th percentile, phones
198 ms102 msMay 23Nov 7121 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026126 ms
May 30, 2026127 ms
Jun 6, 2026129 ms
Jun 13, 2026131 ms
Jun 20, 2026140 ms
Jun 27, 2026154 ms
Jul 4, 2026146 ms
Jul 11, 2026145 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026154 ms
Aug 8, 2026173 ms
Aug 15, 2026173 ms
Aug 22, 2026187 ms
Aug 29, 2026165 ms
Sep 5, 2026139 ms
Sep 12, 2026136 ms
Sep 19, 2026123 ms
Sep 26, 2026120 ms
Oct 3, 2026114 ms
Oct 10, 2026113 ms
Oct 17, 2026115 ms
Oct 24, 2026121 ms
Oct 31, 2026121 ms
Nov 7, 2026121 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

pacifichoods.com (opens in a new tab)
Full-page screenshot of pacifichoods.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pacifichoods.com at 0.4 s0.4 s
  2. pacifichoods.com at 0.8 s0.8 s
  3. pacifichoods.com at 1.1 s1.1 s
  4. pacifichoods.com at 1.5 s1.5 s
  5. pacifichoods.com at 1.9 s1.9 s
  6. pacifichoods.com at 2.3 s2.3 s
  7. pacifichoods.com at 2.6 s2.6 s
  8. pacifichoods.com at 3.0 s3.0 s

Speed

3 to fix98

  • Render-blocking requests

    750 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Use efficient cache lifetimes

    433 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (433 KiB).

  • amaicdn.com adds 1 ms

    1 ms

    amaicdn.com costs a phone 1 ms of main-thread work and 504 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, amaicdn.com and Heroku and others), adding 690 KiB and 6 ms of main-thread time.

  • Reduce unused CSS

    34 KiB

    About 34 KiB of CSS is downloaded but never applied on this page.

  • 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.

3 checks passed

  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 27 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 126 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

11 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

    Real visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 116 ms

    116 ms

    Real visitors wait 116 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 451 ms

    451 ms

    Real visitors wait 451 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.8 s

    1.8 s

    The page is fully interactive after 1.8 s.

Images and page weight

100

  • About 0.3 g of CO₂ per visit

    0.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 37.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed

  • Page weight: 1.1 MB in 43 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 43 requests on a phone: scripts 796 KiB (20), images 172 KiB (10) and HTML 72 KiB (1). That is a lean page.

  • 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

3 to fixGoogle 9296

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed

  • Every image has alt text

    All 36 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100

  • 146 internal links, 7 external

    The homepage links to 146 pages on pacifichoods.com and 7 external pages.

8 checks passed

  • Meta description: 148 characters

    Your meta description is 148 characters: “Discover premium kitchen range hoods made in Taiwan. UL certified with powerful suction, perfect for serious home cooks…”.

  • One H1 headline

    Your main headline reads: “Pacific Hoods”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Pacific Kitchen Range Hoods | Powerful Ventilation for Every Home”.

  • Canonical URL set

    The canonical URL is https://pacifichoods.com/.

  • Structured data in place

    Structured data found: 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://pacifichoods.com/sitemap.xml.

AI search readiness

100

  • No llms.txt

    There is no https://pacifichoods.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.

3 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,123 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90

  • 1 page without a meta description

    https://pacifichoods.com/collections/ih-smart-rice-cooker-series has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://pacifichoods.com/collections/ih-smart-rice-cooker-series has 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 54 found) and read each the way a search engine does.

5 checks passed

  • Linked pages load

    1 page of 15 loaded without an error (the rest turned automated requests away).

  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 10078

  • 1 broken image

    1 image failed to load on a phone, for example https://pacifichoods.com/.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

2 checks passed

  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83

  • 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 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 670 words of copy

    The homepage carries about 670 words of visible text.

5 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “SHOP NOW”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 8 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 pacifichoods.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Inbox · Freegifts · Growave Loyalty Wishlist · weglot.com · bogos.io · socialshopwave.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
New York

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 14 issues on pacifichoods.com, including 5 speed issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25