Website review, no card needed

canton-express.com logo

canton-express.com website review

Visit site (opens in a new tab)Reviewed 30 October 202629 issues · 77 checks

This review found 29 issues worth fixing on canton-express.com, 10 of them high impact, across 77 checks. The most urgent: improve image delivery. 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.1 s2.3 sMay 16Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.9 s
May 23, 20263.8 s
May 30, 20263.7 s
Jun 6, 20263.8 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20263.5 s
Aug 8, 20263.4 s
Aug 15, 20263.1 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20262.7 s
Oct 17, 20262.5 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
85 ms70 msMay 16Oct 2478 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202679 ms
May 30, 202678 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202683 ms
Jul 4, 202680 ms
Jul 11, 202677 ms
Aug 8, 202679 ms
Aug 15, 202672 ms
Aug 22, 202675 ms
Aug 29, 202672 ms
Sep 12, 202675 ms
Sep 19, 202674 ms
Sep 26, 202676 ms
Oct 3, 202676 ms
Oct 10, 202679 ms
Oct 17, 202678 ms
Oct 24, 202678 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 canton-express.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix72
  • Improve image delivery

    1.8 s · 2.2 MB

    10 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 427 KiB

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

  • Render-blocking requests

    1.4 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Reduce unused JavaScript

    1.1 s · 223 KiB

    About 223 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 72

    72/100

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

  • Minify JavaScript

    760 ms · 104 KiB

    104 KiB could be saved by minifying JavaScript.

  • maptiler.com adds 0 ms

    0 ms

    maptiler.com costs a phone 0 ms of main-thread work and 403 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.

  • Duplicated JavaScript

    200 ms · 32 KiB

    32 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Unpkg, Google Fonts and maptiler.com and others), adding 609 KiB and 119 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 ms. During a long task the page ignores taps.

  • 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: 0.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix67
  • 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: 8.0 s

    8.0 s

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

  • Time to Interactive: 8.1 s

    8.1 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Speed Index: 4.4 s

    4.4 s

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

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user INP: 80 ms

    80 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Largest content (LCP) got 30% faster for real visitors

    -30%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 4 ms

    4 ms

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

Images and page weight

4 to fix33
  • Page weight: 21.9 MB in 72 requests

    21.9 MB

    Your homepage downloads 21.9 MB in 72 requests on a phone: media 18.1 MB (2), images 3.4 MB (19) and scripts 311 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    578 KiB

    5 images are downloaded at several times the size a phone draws them, for example canton-logo.png at 3,000 px wide, shown at 148 px. Resized copies would save about 578 KiB.

  • 13 images in older formats

    13 images (1.2 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.

  • 12 images below the first screen load straight away

    12 images further down the page (988 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.2 g of CO₂ per visit

    6.22 g

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

Accessibility

2 to fix87
  • 9 text elements with low contrast

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

  • No page language

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

SEO

3 to fixGoogle 10084
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Canton – The Umami Taste | Chinese Restaurant in Saudi Arabia مطعم صيني”.

  • Meta description is long (227 characters)

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

  • Structured data has 2 problems

    Structured data found (FAQPage, FoodEstablishment, Organization and Restaurant) but with 2 problems, for example “Organization: logo is not an absolute URL ("assets/canton-logo.png")”.

  • 8 internal links, 8 external

    The homepage links to 8 pages on canton-express.com and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Real food, cooked fast”.

  • Canonical URL set

    The canonical URL is https://canton-express.com/.

  • 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://canton-express.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 1 internal page checked

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

7 checks passed
  • Linked pages load

    All 1 page we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 10087
  • 11 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 643 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “ORDER NOW”.

  • 1 call to action

    The homepage has 1 call to action, for example “order.canton-express.com”.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

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

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
GoDaddy

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on canton-express.com, including 16 speed issues, 3 SEO issues 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

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