Website review, no card needed

orquideaflowers.com logo

orquideaflowers.com website review

Visit site (opens in a new tab)Reviewed 8 November 202618 issues · 70 checks

This review found 18 issues worth fixing on orquideaflowers.com, 6 of them high impact, across 70 checks. The most urgent: font display. 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

Full-page screenshot of orquideaflowers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. orquideaflowers.com at 1.2 s1.2 s
  2. orquideaflowers.com at 2.5 s2.5 s
  3. orquideaflowers.com at 3.7 s3.7 s
  4. orquideaflowers.com at 4.9 s4.9 s
  5. orquideaflowers.com at 6.2 s6.2 s
  6. orquideaflowers.com at 7.4 s7.4 s
  7. orquideaflowers.com at 8.6 s8.6 s
  8. orquideaflowers.com at 9.8 s9.8 s

Speed

4 to fix92
  • Font display

    1.6 s

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

  • Render-blocking requests

    1.0 s

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

  • Use efficient cache lifetimes

    500 ms · 733 KiB

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

  • Reduce unused CSS

    440 ms · 81 KiB

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

  • 1 long task on the main thread

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Baidu Analytics and kysport2.com.cn), adding 53 KiB and 38 ms of main-thread time.

  • Reduce unused JavaScript

    33 KiB

    About 33 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    13 KiB

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

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

2 to fix100
  • Speed Index: 7.2 s

    7.2 s

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

  • 3 images without width and height

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

5 checks passed
  • 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.

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “NBA下注围绕服务入口、内容资讯、访问体验等主题持续更新,结合公司介绍、服务入口、资讯动态等栏目梳理核心内容。NBA下…”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.7 s

    1.7 s

    The page is fully interactive after 1.7 s.

Images and page weight

100
  • 3 images below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.38 g

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

3 checks passed
  • Page weight: 1.3 MB in 27 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 27 requests on a phone: images 1,016 KiB (12), fonts 155 KiB (1) and stylesheets 97 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 8796
  • Frames without titles

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

  • Zoom is disabled

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h5 and h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is short (21 characters)

    Your title is only 21 characters: “NBA下注 - NBA下注(中国)官方网站”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 21 internal links, 0 external

    The homepage links to 21 pages on orquideaflowers.com and 0 external pages.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “NBA下注 - NBA下注(中国)官方网站成立于2004年,专注核异构体电池研发,全球领先的钍-229 γ射线能源转化技术,能量密度超传统电池1000倍,寿命达10年+。官网提供同步辐射光源级材料数据、核电池技术库(20万组衰变模拟数据)…”.

  • One H1 headline

    Your main headline reads: “NBA下注服务入口与网页版入口”.

  • Canonical URL set

    The canonical URL is https://orquideaflowers.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://orquideaflowers.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

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

Other pages

3 to fix86
  • 2 linked pages hidden from search

    https://orquideaflowers.com/privacy and https://orquideaflowers.com/terms are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share a meta description

    https://orquideaflowers.com/app, https://orquideaflowers.com/about, https://orquideaflowers.com/privacy and https://orquideaflowers.com/terms use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://orquideaflowers.com/app, https://orquideaflowers.com/about, https://orquideaflowers.com/privacy and https://orquideaflowers.com/terms have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://orquideaflowers.com/app, https://orquideaflowers.com/about, https://orquideaflowers.com/article/news-20261107-1521ab0f.html, https://orquideaflowers.com/article/news-20261105-6580c468.html and https://orquideaflowers.com/article/news-20261104-c417aa50.html 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.

  • 4 pages slow to respond

    https://orquideaflowers.com/app, https://orquideaflowers.com/about, https://orquideaflowers.com/article/news-20261107-1521ab0f.html and https://orquideaflowers.com/privacy took over 3 s to send their HTML from our server.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

    7 pages of 8 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 70 words

    The homepage has only about 70 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.

1 checks passed
  • Direct contact links

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

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 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 orquideaflowers.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
Tailwind CSS
E-commerce
Shopify;Shopify Plus
Hosting
Owgels As Ap Owgels International Co., Limited

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on orquideaflowers.com, including 6 speed issues, 1 SEO issue 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