odonatabooks.com website review

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

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

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

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page has 3,539 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 219 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.

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

4 third-party services load with your homepage (Facebook, Google Tag Manager and Google Fonts and others), adding 3.0 MB and 425 ms of main-thread time.

Google Fonts costs a phone 13 ms of main-thread work and 2.7 MB 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.

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

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

24 KiB could be saved by minifying CSS.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Scripts block taps and scrolling for 517 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 27.4 MB in 376 requests on a phone: images 24.0 MB (299), fonts 2.5 MB (54) and scripts 647 KiB (13). Under 2 MB keeps phones on slow connections fast.

25 images are downloaded at several times the size a phone draws them, for example a9882b5094c61baa.jpg at 1,200 px wide, shown at 358 px. Resized copies would save about 988 KiB.

32 images (4.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.

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

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

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

25 buttons have no accessible name, so screen readers announce just “button”.

26 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 5 characters: “红蜻蜓网店”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 58 characters: “红蜻蜓出版社出版简单又有趣的儿童故事书、温馨又引人入胜的少年小说、轻松又感人的长篇漫画以及有气质亦有内容的生活书籍。”. 70 to 160 characters is enough to sell the click.

There are 15 <h1> headlines (“【2026】新书出版”, “【2025】新书出版” and “【配套】全系列”). One clear main headline is easier for people and search engines.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 571 pages on odonatabooks.com and 14 external pages.

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.

There is no https://shop.odonata.com.my/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.

/ and https://shop.odonata.com.my/home all use the title “红蜻蜓网店”. Search engines can't tell which page to show for a search, so each competes with the others.

https://shop.odonata.com.my/home, https://shop.odonata.com.my/categories, https://shop.odonata.com.my/category/1, https://shop.odonata.com.my/category/62, https://shop.odonata.com.my/category/47 and https://shop.odonata.com.my/category/27 and 9 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://shop.odonata.com.my/category/1, whose canonical is https://shop.odonata.com.my/category/Pre-School/1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shop.odonata.com.my/categories has no <h1> headline, so visitors and search engines get no clear main topic.

https://shop.odonata.com.my/categories, https://shop.odonata.com.my/category/62, https://shop.odonata.com.my/category/47, https://shop.odonata.com.my/category/27, https://shop.odonata.com.my/category/37 and https://shop.odonata.com.my/category/75 and 4 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.

We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the 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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,554 words of visible text.

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

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.