Website review, no card needed

wyteshop.com logo

wyteshop.com website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 97 checks

This review found 52 issues worth fixing on wyteshop.com, 25 of them high impact, across 97 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
4.2 s3.6 sApr 25Oct 104.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.7 s
May 2, 20263.7 s
May 9, 20263.9 s
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20263.9 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.9 s
Jul 11, 20263.8 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20263.9 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20264.1 s
Sep 12, 20264.1 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
154 ms125 msApr 25Oct 10151 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026136 ms
May 2, 2026135 ms
May 9, 2026135 ms
May 16, 2026134 ms
May 23, 2026131 ms
May 30, 2026130 ms
Jun 6, 2026128 ms
Jun 13, 2026130 ms
Jun 20, 2026133 ms
Jun 27, 2026132 ms
Jul 4, 2026136 ms
Jul 11, 2026132 ms
Jul 18, 2026130 ms
Jul 25, 2026130 ms
Aug 1, 2026131 ms
Aug 8, 2026135 ms
Aug 15, 2026137 ms
Aug 22, 2026137 ms
Aug 29, 2026136 ms
Sep 5, 2026137 ms
Sep 12, 2026139 ms
Sep 19, 2026142 ms
Sep 26, 2026145 ms
Oct 3, 2026143 ms
Oct 10, 2026151 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

Full-page screenshot of wyteshop.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wyteshop.com at 1.7 s1.7 s
  2. wyteshop.com at 3.5 s3.5 s
  3. wyteshop.com at 5.2 s5.2 s
  4. wyteshop.com at 6.9 s6.9 s
  5. wyteshop.com at 8.7 s8.7 s
  6. wyteshop.com at 10.4 s10.4 s
  7. wyteshop.com at 12.1 s12.1 s
  8. wyteshop.com at 13.8 s13.8 s

Speed

15 to fix20
  • Reduce unused JavaScript

    6.9 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.

  • 91app.hk adds 2.0 s

    2.0 s

    91app.hk costs a phone 2.0 s of main-thread work and 18.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 1.7 s

    1.7 s

    Google Tag Manager costs a phone 1.7 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 13.7 s

    A phone's processor spends 13.7 s on main-thread work while loading, 8.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 20

    20/100

    Your mobile performance score is 20 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    150 ms · 15.2 MB

    98 images could be 15.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (91app.hk, Google Tag Manager and Facebook and others), adding 21.3 MB and 5.2 s of main-thread time.

  • Use efficient cache lifetimes

    950 ms · 2.2 MB

    44 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

  • Render-blocking requests

    750 ms

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

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 645 ms. During a long task the page ignores taps.

  • Facebook adds 490 ms

    490 ms

    Facebook costs a phone 490 ms of main-thread work and 404 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.

  • easychat.co adds 444 ms

    444 ms

    easychat.co costs a phone 444 ms of main-thread work and 597 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 CSS

    310 ms · 60 KiB

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

  • awswaf.com adds 265 ms

    265 ms

    awswaf.com costs a phone 265 ms of main-thread work and 304 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.

  • 2,340 HTML elements

    The page has 2,340 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    50 ms · 54 KiB

    Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Phones get a much slower page than desktops

    Desktop scores 46 but mobile only 20. 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.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 17.3 s

    17.3 s

    Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HeaderA-carousel-1”.

  • Speed Index: 16.3 s

    16.3 s

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

  • Time to Interactive: 50.5 s

    50.5 s

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

  • Total Blocking Time: 3.8 s

    3.8 s

    Scripts block taps and scrolling for 3.8 s in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.289

    0.289

    The layout shifts by 0.289 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

7 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: 1.8 s

    1.8 s

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

  • Real-user INP: 161 ms

    161 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 489 ms

    489 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix14
  • Page weight: 21.5 MB in 289 requests

    21.5 MB

    Your homepage downloads 21.5 MB in 289 requests on a phone: images 17.5 MB (126), scripts 3.7 MB (45) and other files 167 KiB (107). Under 2 MB keeps phones on slow connections fast.

  • 19 images far larger than shown

    2.7 MB

    19 images are downloaded at several times the size a phone draws them, for example 639280061589270000 at 1,000 px wide, shown at 181 px. Resized copies would save about 2.7 MB.

  • 2 images over 500 KB

    2 images weigh 1.0 MB together. On a phone connection a single image that size takes seconds.

  • 31 images in older formats

    31 images (5.8 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.

  • An image on the first screen is lazy-loaded

    c2cbe58c-ae1d-4b2f-a02f-75aa2a839f7e-1792138193-dhz4y1moow_m 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 6.1 g of CO₂ per visit

    6.11 g

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

Accessibility

8 to fixGoogle 7686
  • 92 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • 40 tap targets too small

    40 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9278
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (3 characters)

    Your title is only 3 characters: “位元堂”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 12 links crawlers can't follow

    12 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 8 internal links, 0 external

    The homepage links to 8 pages on wyteshop.com and 0 external pages.

5 checks passed
  • Meta description: 87 characters

    Your meta description is 87 characters: “位元堂一百三十年品牌,提供正宗中藥與現代保健品,值得信賴。 登記會員及下載APP即送優惠券,購物滿HK$500免運費,配合送貨上門或順豐智能櫃自提,即可安享家中享受不同優惠。”.

  • Canonical URL set

    The canonical URL is https://www.wyteshop.com/.

  • Structured data in place

    Structured data found: LocalBusiness.

  • 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://www.wyteshop.com/Sitemap/97/Sitemap_Index.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 459 words, but the HTML your server sends has only 2. 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.

  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

Other pages

4 to fix58
  • 3 linked pages are broken

    Your homepage links to https://www.wyteshop.com/V2/TradesOrder/TradesOrderList, https://www.wyteshop.com/V2/VipMember/VIPMemberRelay and https://www.wyteshop.com/v2/ECoupon/MyECoupon, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 pages share a title

    /, https://www.wyteshop.com/page/5202026 and https://www.wyteshop.com/V2/ShoppingCart/Index all use the title “位元堂”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.wyteshop.com/V2/ShoppingCart/Index has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.wyteshop.com/page/5202026, https://www.wyteshop.com/TraceSalePageList/TraceSalePageList, https://www.wyteshop.com/V2/ShoppingCart/Index and https://www.wyteshop.com/v2/official/SalePageCategory/19051 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.wyteshop.com/page/5202026 has 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.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=15002818&Ver=2&mid=7c6ac8a0-3be5-4d88-bac5-c6394f560106&bo=1&sid=bf912f00cb7a11f1888d0327f7f4047e&vid=bf911570cb7a11f1b51411b1e5812cb8&vids=1&msclkid=N&pi=918639831&lg.

  • 28 small tap targets

    28 of 62 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • 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

5 to fix50
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 459 words of visible text.

3 checks passed
  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 1 of them by other companies (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.

  • 46 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on wyteshop.com, including 20 speed issues, 4 SEO issues and 5 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