Tools & Wizards About Us
fi.airwheel.net screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 24

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

fi.airwheel.net

Airwheel Official Site_electric one wheel_1 _one wheel scooter_electric unicycle_electric scooter_2-wheeled electric scooter, electric drift hoverboar...

Page Load Speed

6.7 sec in total

First Response

934 ms

Resources Loaded

5.5 sec

Page Rendered

256 ms

fi.airwheel.net screenshot

About Website

Click here to check amazing Fi Airwheel content for China. Otherwise, check out these important facts you probably never knew about fi.airwheel.net

World's Best Electric Unicycle Manufacturer Airwheel Electric Unicycle Top Quality! Electric Scooter, Unicycle, Self-Balancing Scooter,With 60% global market share, Airwheel has realized the giant...

Visit fi.airwheel.net

Key Findings

We analyzed Fi.airwheel.net page load time and found that the first response time was 934 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

fi.airwheel.net performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value260 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.327

35/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

fi.airwheel.net

934 ms

jquery-2.1.0.js

392 ms

common.js

268 ms

index.js

275 ms

product_shop.css

132 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 86% of them (49 requests) were addressed to the original Fi.airwheel.net, 12% (7 requests) were made to Lr.zoosnet.net and 2% (1 request) were made to Apis.map.qq.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Lr.zoosnet.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 781.4 kB (38%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fi.airwheel.net main page is 2.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 88.4 kB

  • Original 118.9 kB
  • After minification 117.2 kB
  • After compression 30.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 88.4 kB or 74% of the original size.

Image Optimization

-35%

Potential reduce by 618.9 kB

  • Original 1.8 MB
  • After minification 1.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Fi Airwheel needs image optimization as it can save up to 618.9 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-45%

Potential reduce by 73.3 kB

  • Original 163.5 kB
  • After minification 163.5 kB
  • After compression 90.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 73.3 kB or 45% of the original size.

CSS Optimization

-22%

Potential reduce by 841 B

  • Original 3.8 kB
  • After minification 3.8 kB
  • After compression 2.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fi.airwheel.net needs all CSS files to be minified and compressed as it can save up to 841 B or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (13%)

Requests Now

53

After Optimization

46

  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fi Airwheel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

fi.airwheel.net

fi.airwheel.net

934 ms

jquery-2.1.0.js

jquery-2.1.0.js

392 ms

common.js

common.js

268 ms

index.js

index.js

275 ms

product_shop.css

product_shop.css

132 ms

nav.js

nav.js

128 ms

navSearch.css

navSearch.css

128 ms

a02.png

a02.png

66 ms

airwheel_nav_e3.png

airwheel_nav_e3.png

124 ms

airwheel_nav_e6.png

airwheel_nav_e6.png

183 ms

airwheel_nav_z5.png

airwheel_nav_z5.png

188 ms

airwheel_nav_c5.png

airwheel_nav_c5.png

253 ms

airwheel_nav_z3.png

airwheel_nav_z3.png

126 ms

airwheel_nav_m3.png

airwheel_nav_m3.png

132 ms

airwheel_nav_s6.png

airwheel_nav_s6.png

186 ms

airwheel_nav_a3.png

airwheel_nav_a3.png

190 ms

airwheel_nav_s5.png

airwheel_nav_s5.png

196 ms

airwheel_nav_s3.png

airwheel_nav_s3.png

245 ms

airwheel_nav_q6.png

airwheel_nav_q6.png

247 ms

airwheel_nav_q5.png

airwheel_nav_q5.png

253 ms

airwheel_nav_q1.png

airwheel_nav_q1.png

256 ms

airwheel_nav_q3.png

airwheel_nav_q3.png

262 ms

airwheel_nav_x8.png

airwheel_nav_x8.png

310 ms

airwheel_nav_x3.png

airwheel_nav_x3.png

310 ms

world.png

world.png

317 ms

Airwheel-country1.png

Airwheel-country1.png

380 ms

airwheel_z5.jpg

airwheel_z5.jpg

506 ms

c5_helmet_banner.jpg

c5_helmet_banner.jpg

389 ms

airwheel_e6_bike_banner.jpg

airwheel_e6_bike_banner.jpg

435 ms

airwheel_e6_banner.jpg

airwheel_e6_banner.jpg

499 ms

airwheel_itaily_s3.jpg

airwheel_itaily_s3.jpg

571 ms

index_news.png

index_news.png

446 ms

index_Events.png

index_Events.png

452 ms

Airwheel_c5.png

Airwheel_c5.png

499 ms

airwheel_e6.png

airwheel_e6.png

576 ms

airwheel_e3.png

airwheel_e3.png

518 ms

airwheel_z8.png

airwheel_z8.png

563 ms

Airwheel_20150428143655105.png

Airwheel_20150428143655105.png

562 ms

airwheel_z5.png

airwheel_z5.png

569 ms

Airwheel_H3TS__20220924154132572.jpg

Airwheel_H3TS__20220924154132572.jpg

584 ms

Airwheel_H3S_wheelchair_video.jpg

Airwheel_H3S_wheelchair_video.jpg

624 ms

Airwheel_SR5_robot_suitcase.jpg

Airwheel_SR5_robot_suitcase.jpg

624 ms

airwheel_se3mini_scooter_luggage_video.jpg

airwheel_se3mini_scooter_luggage_video.jpg

600 ms

lato-light-webfont.woff

lato-light-webfont.woff

571 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

585 ms

lato-regular-webfont.woff

lato-regular-webfont.woff

526 ms

759ec5ffe298ff68687315ffd06b8aec.png

759ec5ffe298ff68687315ffd06b8aec.png

559 ms

42a2b8c5494842875203742abc91fc7f.png

42a2b8c5494842875203742abc91fc7f.png

506 ms

airwheel_ewm.jpg

airwheel_ewm.jpg

515 ms

lsjs.aspx

lsjs.aspx

1351 ms

JS5_2.css

JS5_2.css

269 ms

JS_Float.aspx

JS_Float.aspx

540 ms

minvite_en.jpg

minvite_en.jpg

2542 ms

mobileonlineimgsrc_en.png

mobileonlineimgsrc_en.png

609 ms

spacer.gif

spacer.gif

718 ms

newsid0.aspx

newsid0.aspx

480 ms

ip

ip

1315 ms

Accessibility Review

fi.airwheel.net accessibility score

24

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fi.airwheel.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fi.airwheel.net SEO score

74

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fi.airwheel.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fi.airwheel.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

fi.airwheel.net

Open Graph description is not detected on the main page of Fi Airwheel. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: