Website review, no card needed

phoenixsweets.com logo

phoenixsweets.com website review

Visit site (opens in a new tab)Reviewed 11 November 202623 issues · 64 checks

This review found 23 issues worth fixing on phoenixsweets.com, 5 of them high impact, across 64 checks. The most urgent: 16 text elements with low contrast. 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

Full-page screenshot of phoenixsweets.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. phoenixsweets.com at 0.5 s0.5 s
  2. phoenixsweets.com at 1.0 s1.0 s
  3. phoenixsweets.com at 1.4 s1.4 s
  4. phoenixsweets.com at 1.9 s1.9 s
  5. phoenixsweets.com at 2.4 s2.4 s
  6. phoenixsweets.com at 2.9 s2.9 s
  7. phoenixsweets.com at 3.4 s3.4 s
  8. phoenixsweets.com at 3.8 s3.8 s

Speed

1 to fix82
  • Mobile performance score: 82

    82/100

    Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    150 ms · 28 KiB

    About 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Shopify), adding 64 KiB and 23 ms of main-thread time.

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix82
  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 4.7 s

    4.7 s

    Visually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 4.2 s

    4.2 s

    The page becomes fully interactive after 4.2 s. Good is under 3.8 s.

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.39 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.5 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.4 MB in 165 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 165 requests on a phone: other files 838 KiB (116), scripts 173 KiB (35) and images 162 KiB (7). 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

4 to fixGoogle 9794
  • 16 text elements with low contrast

    16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 45 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: 45 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9289
  • Canonical points to another host

    Your canonical URL points to shop.phoenixsweets.com, not phoenixsweets.com, so Google may credit that host instead.

  • Meta description is long (261 characters)

    Your meta description is 261 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 46 internal links, 18 external

    The homepage links to 46 pages on phoenixsweets.com and 18 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Phoenix Sweets”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Phoenix Sweets - Hong Kong Cake Shop 香港蛋糕店 - 精緻生日蛋糕、結婚蛋糕”.

  • 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://phoenixsweets.com/sitemap.xml.

AI search readiness

100
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 (360 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://phoenixsweets.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 1 linked page hidden from search

    https://phoenixsweets.com/collections/standard-butter-cream-cake is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://phoenixsweets.com/pages/project-reference-business-events, https://phoenixsweets.com/blogs/news and https://phoenixsweets.com/blogs/happy-paws have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://phoenixsweets.com/pages/about-us_n and https://phoenixsweets.com/pages/phoenix-sweets-q-a-for-tailor-made-service use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://phoenixsweets.com/pages/about-us_n, https://phoenixsweets.com/pages/project-reference-business-events, https://phoenixsweets.com/pages/phoenix-sweets-q-a-for-tailor-made-service, https://phoenixsweets.com/pages/press, https://phoenixsweets.com/pages/supplier-registration and https://phoenixsweets.com/collections/party-sweets and 5 others 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 27 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Unexpected end of attribute. Expected length, "".”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 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.

  • Only about 167 words

    The homepage has only about 167 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Join Us”, “Learn More” and “Contact Us”.

  • 5 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 10 cookies set on arrival

    10

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

  • 13 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on phoenixsweets.com, including 5 speed issues, 3 SEO issues and 4 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

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