Website review, no card needed
amesinternational.com website review
Visit site (opens in a new tab)Reviewed 21 October 202626 issues · 76 checks
This review found 26 issues worth fixing on amesinternational.com, 7 of them high impact, across 76 checks. The most urgent: 10 text elements with low contrast. 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
83B- #27,005 of 117,615 reviewed websitesbeats 72%
- #17,851 of 66,923 online storesbeats 67%
- #17,312 of 61,018 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 915 ms |
| May 16, 2026 | 859 ms |
| May 23, 2026 | 847 ms |
| May 30, 2026 | 821 ms |
| Jun 6, 2026 | 889 ms |
| Jun 13, 2026 | 886 ms |
| Jun 20, 2026 | 934 ms |
| Jun 27, 2026 | 935 ms |
| Jul 4, 2026 | 990 ms |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 990 ms |
| Jul 25, 2026 | 921 ms |
| Aug 1, 2026 | 870 ms |
| Aug 8, 2026 | 875 ms |
| Aug 15, 2026 | 867 ms |
| Aug 22, 2026 | 922 ms |
| Aug 29, 2026 | 936 ms |
| Sep 5, 2026 | 939 ms |
| Sep 12, 2026 | 941 ms |
| Sep 19, 2026 | 901 ms |
| Sep 26, 2026 | 858 ms |
| Oct 3, 2026 | 818 ms |
| Oct 10, 2026 | 821 ms |
| Oct 17, 2026 | 823 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 106 ms |
| May 9, 2026 | 103 ms |
| May 16, 2026 | 101 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 118 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 121 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
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
350 ms · 303 KiB16 images could be 303 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and nfcube.com and others), adding 1.2 MB and 323 ms of main-thread time.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 219 ms
219 msKlaviyo costs a phone 219 ms of main-thread work and 325 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.
Shopify adds 89 ms
89 msShopify costs a phone 89 ms of main-thread work and 748 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.
Reduce unused JavaScript
150 ms · 74 KiBAbout 74 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 144 ms. During a long task the page ignores taps.
Legacy JavaScript
68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
25 KiB12 files are served with short cache lifetimes, so returning visitors download them again (25 KiB).
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 97 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.3 s
13.3 sYour largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 15.6 s
15.6 sThe page becomes fully interactive after 15.6 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 220 ms
220 msScripts block taps and scrolling for 220 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 106 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 402 ms
402 msReal visitors wait 402 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 388 requests
2.8 MBYour homepage downloads 2.8 MB in 388 requests on a phone: scripts 1,002 KiB (200), other files 928 KiB (111) and images 558 KiB (23). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
5-box-cookie-gift-set-1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 95.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has 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. (1 element).
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (313 characters)
Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
54 internal links, 1 external
The homepage links to 54 pages on amesinternational.com and 1 external page.
6 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “Puyallup Chocolates | Premium Chocolate Gifts”.
Canonical URL set
The canonical URL is https://puyallupchocolates.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://puyallupchocolates.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: 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 (493 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://puyallupchocolates.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://puyallupchocolates.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://puyallupchocolates.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
9 pages without a meta description
https://puyallupchocolates.com/collections/all, https://puyallupchocolates.com/customer_authentication/redirect, https://puyallupchocolates.com/collections/shop-all, https://puyallupchocolates.com/policies/shipping-policy, https://puyallupchocolates.com/collections/handcrafted-chocolate-bars and https://puyallupchocolates.com/collections/chocolate-covered-collection and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://puyallupchocolates.com/customer_authentication/redirect and https://puyallupchocolates.com/pages/corporate-gifting 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 29 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 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.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
26 of 32 tappable elements near the top are at least 24 px.
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 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 286 words of copy
The homepage carries about 286 words of visible text.
3 checks passed
9 calls to action
The homepage has 9 calls to action, for example “SHOP”, “Shop All” and “WHERE TO BUY”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks and 1 trust badge.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
31 other companies contacted
Loading the homepage contacts 31 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 amesinternational.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on amesinternational.com, including 12 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.