Website review, no card needed

cheryinternational.com logo

cheryinternational.com website review

Visit site (opens in a new tab)Reviewed 1 November 202647 issues · 87 checks

This review found 47 issues worth fixing on cheryinternational.com, 17 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
2.3 s1.7 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
91 ms83 msMay 9Oct 2490 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202689 ms
May 16, 202688 ms
May 23, 202687 ms
May 30, 202686 ms
Jun 6, 202686 ms
Jun 13, 202686 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202686 ms
Aug 1, 202685 ms
Aug 8, 202685 ms
Aug 15, 202685 ms
Aug 22, 202685 ms
Aug 29, 202684 ms
Sep 5, 202685 ms
Sep 12, 202685 ms
Sep 19, 202685 ms
Sep 26, 202685 ms
Oct 3, 202688 ms
Oct 10, 202689 ms
Oct 17, 202689 ms
Oct 24, 202690 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 cheryinternational.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cheryinternational.com at 0.8 s0.8 s
  2. cheryinternational.com at 1.6 s1.6 s
  3. cheryinternational.com at 2.4 s2.4 s
  4. cheryinternational.com at 3.2 s3.2 s
  5. cheryinternational.com at 4.0 s4.0 s
  6. cheryinternational.com at 4.8 s4.8 s
  7. cheryinternational.com at 5.6 s5.6 s
  8. cheryinternational.com at 6.4 s6.4 s

Speed

7 to fix50
  • Use efficient cache lifetimes

    6.9 s · 78.1 MB

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

  • Improve image delivery

    2.4 s · 20.1 MB

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

  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    1.6 s · 345 KiB

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

  • Font display

    1.1 s

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

  • Mobile performance score: 50

    50/100

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

  • Main-thread work: 2.8 s

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Other Google APIs/SDKs), adding 170 KiB and 230 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 32 KiB

    About 32 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.

  • Document request latency

    161 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 5 long tasks on the main thread

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

  • Minify JavaScript

    46 KiB

    46 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 128 ms

    128 ms

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

Core Web Vitals

8 to fix100
  • 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: 116.6 s

    116.6 s

    Your largest element takes 116.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookles to analyze site usage and improve our websit…”.

  • Time to Interactive: 127.3 s

    127.3 s

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

  • Speed Index: 11.4 s

    11.4 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user TTFB: 950 ms

    950 ms

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

  • Cumulative Layout Shift: 0.143

    0.143

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

  • 4 images without width and height

    4 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 89 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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: 1.4 s

    1.4 s

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

  • Total Blocking Time: 195 ms

    195 ms

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

Images and page weight

4 to fix38
  • Page weight: 78.5 MB in 237 requests

    78.5 MB

    Your homepage downloads 78.5 MB in 237 requests on a phone: images 76.8 MB (197), media 605 KiB (3) and scripts 507 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 23 images over 500 KB

    23 images weigh 26.7 MB together. On a phone connection a single image that size takes seconds.

  • 40 images in older formats

    40 images (33.4 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.

  • 3 images below the first screen load straight away

    3 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 22.3 g of CO₂ per visit

    22.26 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 5584
  • 6 text elements with low contrast

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

  • 17 images without alt text

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

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

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

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 19 links without text

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

1 checks passed
  • 21 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 28 WCAG 2.2 A/AA and best-practice rules on the phone render: 21 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

10 to fixGoogle 8257
  • No H1 headline

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

  • Title is short (19 characters)

    Your title is only 19 characters: “Chery international”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (200 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.cheryinternational.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at cheryinternational.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 122 internal links, 7 external

    The homepage links to 122 pages on cheryinternational.com and 7 external pages.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

5 to fix67
  • 1 page without a title

    https://www.cheryinternational.com/pc/models/tiggo/allnewtiggo7/index.shtml has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.cheryinternational.com/pc/models/tiggo/tiggo8proe/index.shtml and https://www.cheryinternational.com/pc/models/tiggo/tiggo8_new/index.shtml all use the title “Chery Tiggo 8 PRO Plug-In Hybrid|PHEV, Endurance, Tech|Chery internat…”. 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.cheryinternational.com/pc/models/tiggo/allnewtiggo7/index.shtml has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.cheryinternational.com/pc/models/tiggo/tiggo8proe/index.shtml and https://www.cheryinternational.com/pc/models/tiggo/tiggo8_new/index.shtml use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.cheryinternational.com/pc/models/tiggo/cheryq/index.shtml, https://www.cheryinternational.com/pc/models/tiggo/tiggov/index.shtml, https://www.cheryinternational.com/pc/models/tiggo/tiggo9csh/index.shtml, https://www.cheryinternational.com/pc/models/tiggo/tiggo9/index.shtml, https://www.cheryinternational.com/pc/models/tiggo/tiggo8proe/index.shtml and https://www.cheryinternational.com/pc/models/tiggo/tiggo8_new/index.shtml and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.cheryinternational.com/pc/models/tiggo/tiggox7/index.shtml, https://www.cheryinternational.com/pc/models/arrizo/arrizo8csh/index.shtml and https://www.cheryinternational.com/pc/models/arrizo/arrizo8/index.shtml took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9693
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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.

  • Thin social proof

    Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

    The homepage carries about 415 words of visible text.

2 checks passed
  • 4 calls to action

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 cheryinternational.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
- Zenlayer Inc

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on cheryinternational.com, including 15 speed issues, 10 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

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