janiceabistro.com website review

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

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

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

21 images could be 985 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

23 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

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

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

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “深圳乐鱼体育科技有限公司（简称"乐鱼体育"）成立于2010年，总部位于深圳，是国家高新技术企业、深圳市专精特新企业及深…”. Most of its time is element render delay (4.3 s).

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.

Your homepage downloads 5.7 MB in 102 requests on a phone: images 4.4 MB (79), media 1.0 MB (1) and scripts 176 KiB (13). Under 2 MB keeps phones on slow connections fast.

19 images are downloaded at several times the size a phone draws them, for example 65a4a318949f7d3654dbd843eea59ff2.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 1.4 MB.

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

24 images further down the page (2.3 MB) 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 1.61 g of CO₂e: 192.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is only 24 characters: “乐鱼体育(中国)官方网站 - 乐鱼 sports”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.

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

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

The homepage links to 920 pages on janiceabistro.com and 0 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://janiceabistro.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.

/, https://janiceabistro.com/prdt_1/21.html, https://janiceabistro.com/prdt/22.html, https://janiceabistro.com/prdt_1/23.html, https://janiceabistro.com/prdt_1/24.html and https://janiceabistro.com/prdt/183.html and 10 others all use the title “乐鱼体育(中国)官方网站 - 乐鱼 sports”. Search engines can't tell which page to show for a search, so each competes with the others.

https://janiceabistro.com/prdt_1/21.html, https://janiceabistro.com/prdt/22.html, https://janiceabistro.com/prdt_1/23.html, https://janiceabistro.com/prdt_1/24.html, https://janiceabistro.com/prdt/183.html and https://janiceabistro.com/prdt_1/214.html and 9 others use the same meta description. A description written for each page earns more clicks.

https://janiceabistro.com/prdt/26.html took over 3 s to send its HTML from our server.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 74 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Opening the homepage sets 3 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.