thehover.com website review

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

4 third-party services load with your homepage (gethover.com, aliyuncs.com and Baidu Analytics and others), adding 49.8 MB and 677 ms of main-thread time.

gethover.com costs a phone 566 ms of main-thread work and 49.8 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.

21 images could be 5.3 MB 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.

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

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

72 KiB could be saved by minifying JavaScript.

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

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

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

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

8 KiB could be saved by minifying CSS.

1 file is served with short cache lifetimes, so returning visitors download them again (7 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 15.5 s (Speed Index). Good is under 3.4 s.

Your largest element takes 7.5 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 13.4 s. Good is under 3.8 s.

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

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

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 49.9 MB in 148 requests on a phone: media 41.0 MB (24), images 8.0 MB (62) and fonts 495 KiB (6). Under 2 MB keeps phones on slow connections fast.

7 images (929 KiB) 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.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 9 characters: “哈浮飞行相机 X1”. 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 16 characters: “哈浮 HOVER，飞行相机开创者”. 70 to 160 characters is enough to sell the click.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

3 links have no real href, so search engines can't follow them.

The homepage links to 26 pages on thehover.com and 41 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://thehover.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://thehover.com/hoverx1, https://thehover.com/support, https://thehover.com/terms, https://thehover.com/privacy, https://thehover.com/support/warranty and https://thehover.com/release-notes-firmware-version and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://thehover.com/hoverx1 all use the title “哈浮飞行相机 X1”. Search engines can't tell which page to show for a search, so each competes with the others.

https://thehover.com/hoverx1, https://thehover.com/support, https://thehover.com/terms, https://thehover.com/privacy, https://thehover.com/support/warranty and https://thehover.com/release-notes-firmware-version and 2 others use the same meta description. A description written for each page earns more clicks.

https://thehover.com/hoverx1, https://thehover.com/support, https://thehover.com/terms, https://thehover.com/privacy, https://thehover.com/support/warranty and https://thehover.com/support/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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: 3 trust badges. 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.

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

There is no form on the homepage, so every lead has to click through to another page first.

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