Website review, no card needed
91910324.com website review
Visit site (opens in a new tab)Reviewed 1 November 202628 issues · 70 checks
This review found 28 issues worth fixing on 91910324.com, 8 of them high impact, across 70 checks. The most urgent: render-blocking requests. 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
77C- #67,352 of 120,787 reviewed websitesbeats 39%
- #43,792 of 68,384 online storesbeats 31%
- #390 of 889 BigCommerce storesbeats 49%
Closest competitors among BigCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.9 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Use efficient cache lifetimes
150 ms · 115 KiB18 files are served with short cache lifetimes, so returning visitors download them again (115 KiB).
Reduce unused JavaScript
120 ms · 23 KiBAbout 23 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 120 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (StatCounter, Google CDN and Bootstrap CDN and others), adding 59 KiB and 38 ms of main-thread time.
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. That is in Google's “good” band (90 and up).
Main-thread work: 0.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 70 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
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.
4 checks passed
Cumulative Layout Shift: 0.093
0.093The layout barely moves while loading (CLS 0.093, good is under 0.1).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “掛線後等待的士司機回覆的士車牌及到達時間 ~提示乘客請緊記的士車牌,切勿胡亂登車~ 24小時服務,保證回覆,為提供優質…”.
Time to Interactive: 2.0 s
2.0 sThe page is fully interactive after 2.0 s.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.05 g of CO₂ per visit
0.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.05 g of CO₂e: 5.7 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: 171 KiB in 28 requests
171 KiBYour homepage downloads 171 KiB in 28 requests on a phone: scripts 103 KiB (11), images 41 KiB (8) and stylesheets 21 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
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 (6 elements)
All page content should be contained by landmarks: 6 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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
15 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 15 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (16 characters)
Your title is only 16 characters: “電召的士服務 9191 0324”. 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.
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://91910324.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
9 internal links, 5 external
The homepage links to 9 pages on 91910324.com and 5 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
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://91910324.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
7 pages without a meta description
https://91910324.com/pages/Call-%E8%BB%8A%E6%96%B9%E6%B3%95.html, https://91910324.com/pages/%E7%9A%84%E5%A3%AB%E6%90%AD%E9%9B%BB%E6%9C%8D%E5%8B%99.html, https://91910324.com/pages/%E6%A9%9F%E5%A0%B4%E7%9A%84%E5%A3%AB.html, https://91910324.com/pages/%E8%90%BD%E9%A6%AC%E6%B4%B2%E5%83%B9%E7%9B%AE%E8%A1%A8.html, https://91910324.com/pages/%E5%BE%80%E4%BE%86%E6%9D%B1%E6%B6%8C%E5%83%B9%E7%9B%AE%E8%A1%A8.html and https://91910324.com/pages/%E6%B7%B1%E5%9C%B3%E7%81%A3%E5%8F%A3%E5%B2%B8%E5%83%B9%E9%8C%A2.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://91910324.com/pages/Call-%E8%BB%8A%E6%96%B9%E6%B3%95.html, https://91910324.com/pages/%E7%9A%84%E5%A3%AB%E6%90%AD%E9%9B%BB%E6%9C%8D%E5%8B%99.html, https://91910324.com/pages/%E6%A9%9F%E5%A0%B4%E7%9A%84%E5%A3%AB.html, https://91910324.com/pages/%E8%90%BD%E9%A6%AC%E6%B4%B2%E5%83%B9%E7%9B%AE%E8%A1%A8.html, https://91910324.com/pages/%E5%BE%80%E4%BE%86%E6%9D%B1%E6%B6%8C%E5%83%B9%E7%9B%AE%E8%A1%A8.html and https://91910324.com/pages/%E6%B7%B1%E5%9C%B3%E7%81%A3%E5%8F%A3%E5%B2%B8%E5%83%B9%E9%8C%A2.html and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://91910324.com/pages/Call-%E8%BB%8A%E6%96%B9%E6%B3%95.html, https://91910324.com/pages/%E7%9A%84%E5%A3%AB%E6%90%AD%E9%9B%BB%E6%9C%8D%E5%8B%99.html, https://91910324.com/pages/%E8%90%BD%E9%A6%AC%E6%B4%B2%E5%83%B9%E7%9B%AE%E8%A1%A8.html, https://91910324.com/pages/%E5%BE%80%E4%BE%86%E6%9D%B1%E6%B6%8C%E5%83%B9%E7%9B%AE%E8%A1%A8.html, https://91910324.com/pages/%E6%B7%B1%E5%9C%B3%E7%81%A3%E5%8F%A3%E5%B2%B8%E5%83%B9%E9%8C%A2.html and https://91910324.com/sitemap have 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.
5 checks passed
Linked pages load
All 7 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://taxi977708.globle-un.com/product_images/uploaded_images/ph.png.
11 small tap targets
11 of 11 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: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 16 words
The homepage has only about 16 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “EC Shop City”.
2 calls to action
The homepage has 2 calls to action, for example “Call 車方法” and “EC Shop City”.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
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 91910324.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- BigCommerce
- Hosting
- CITIC Telecom International CPC Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on 91910324.com, including 4 speed issues, 7 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.