Website review, no card needed
28fly.com website review
Visit site (opens in a new tab)Reviewed 14 November 202640 issues · 76 checks
This review found 40 issues worth fixing on 28fly.com, 18 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
64D- #102,931 of 109,350 reviewed websitesbeats 5%
- #60,145 of 61,859 online storesbeats 2%
- #724 of 765 BigCommerce storesbeats 4%
Closest competitors among BigCommerce stores
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
19.7 s · 8.9 MB67 files are served with short cache lifetimes, so returning visitors download them again (8.9 MB).
Improve image delivery
17.1 s · 7.7 MB44 images could be 7.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.1 s faster on a phone.
Render-blocking requests
3.0 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Font display
1.4 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
160 ms · 24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Google CDN and FontAwesome CDN), adding 120 KiB and 35 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 57 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
Largest Contentful Paint: 26.2 s
26.2 sYour largest element takes 26.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “001.jpg”.
Time to Interactive: 26.8 s
26.8 sThe page becomes fully interactive after 26.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.293
0.293The layout shifts by 0.293 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
14 images without width and height
14 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.
1 checks passed
Total Blocking Time: 2 ms
2 msScripts block the page for only 2 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.0 MB in 72 requests
9.0 MBYour homepage downloads 9.0 MB in 72 requests on a phone: images 8.6 MB (49), fonts 220 KiB (3) and scripts 80 KiB (9). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
3.9 MB11 images are downloaded at several times the size a phone draws them, for example a1.png at 1,426 px wide, shown at 350 px. Resized copies would save about 3.9 MB.
40 images in older formats
40 images (8.5 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.
29 images below the first screen load straight away
29 images further down the page (5.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.55 g of CO₂e: 305.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
<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.
All page content should be contained by landmarks (73 elements)
All page content should be contained by landmarks: 73 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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 87 images in the HTML carry an alt attribute.
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 8 failed. 1 more 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.
Title is short (5 characters)
Your title is only 5 characters: “28fly”. 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.
7 H1 headlines
There are 7 <h1> headlines (“Fly cloudless with 28fly.com3大保證”, “優惠價格” and “可靠,方便、快捷”). One clear main headline is easier for people and search engines.
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://28fly.com/sitemap.xml, so Google discovers your pages only by following links.
2 links crawlers can't follow
2 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.
135 internal links, 11 external
The homepage links to 135 pages on 28fly.com and 11 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://28fly.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
14 pages without a meta description
https://28fly.com/pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, https://28fly.com/categories/%E6%88%91%E5%80%91%E7%9A%84%E6%9C%8D%E5%8B%99, https://28fly.com/pages/%E4%BB%A3%E8%BE%A6%E7%B0%BD%E8%AD%89.html, https://28fly.com/pages/%E6%8E%A8%E5%BB%A3%E6%B4%BB%E5%8B%95.html, https://28fly.com/pages/%E6%97%85%E9%81%8A%E8%B3%87%E8%A8%8A.html and https://28fly.com/pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages with very little text
https://28fly.com/pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, https://28fly.com/categories/%E6%88%91%E5%80%91%E7%9A%84%E6%9C%8D%E5%8B%99, https://28fly.com/pages/%E4%BB%A3%E8%BE%A6%E7%B0%BD%E8%AD%89.html, https://28fly.com/pages/%E6%8E%A8%E5%BB%A3%E6%B4%BB%E5%8B%95.html, https://28fly.com/pages/%E6%97%85%E9%81%8A%E8%B3%87%E8%A8%8A.html and https://28fly.com/pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html and 8 others 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.
2 pages slow to respond
https://28fly.com/products/%E6%A5%B5%E5%85%89%E4%B9%8B%E6%97%85-Aurora-Travel-Package-.html and https://28fly.com/products/%E4%BB%A3%E8%A8%82%E6%97%85%E8%A1%8C%E5%9C%98%E6%8A%98%E6%89%A3%E9%AB%98%E9%81%94%24800-Tour-%7B47%7DPackage-rebate--.html 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.
6 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 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 14 pages that loaded have a <title>.
Best practices
26 small tap targets
26 of 50 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 “Unexpected token '%'”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 118 words
The homepage has only about 118 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
1 call to action
The homepage has 1 call to action, for example “EC Shop City”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 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 28fly.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 40 issues on 28fly.com, including 11 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.