Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ionex.global

KYMCO 光陽機車官網|全新車款 任您挑選

Page Load Speed

8.5 sec in total

First Response

585 ms

Resources Loaded

7.2 sec

Page Rendered

730 ms

About Website

Visit ionex.global now to see the best up-to-date Ionex content and also check out these interesting facts you probably never knew about ionex.global

KYMCO光陽機車官方網站,探索最新車款:G7、大樂、新K1 特仕版、Laddi、RTS R 165、Yogurt、Like Euro、Xciting X350等熱門機車。提供完整車款資訊、規格與最新促銷優惠,2025/7起光陽全車系噴射電腦元件享4年保固!滿足您的騎乘需求。

Visit ionex.global

Key Findings

We analyzed Ionex.global page load time and found that the first response time was 585 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ionex.global performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value29.3 s

0/100

25%

SI (Speed Index)

Value23.3 s

0/100

10%

TBT (Total Blocking Time)

Value2,920 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.092

92/100

15%

TTI (Time to Interactive)

Value28.9 s

0/100

10%

Network Requests Diagram

ionex.global

585 ms

www.kymco.com.tw

1344 ms

css

56 ms

998846820fdce162417d161300402bb6-1658320339

403 ms

08eee4ce70111ca6b36269ca8502416f-1658320339

1387 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ionex.global, 56% (47 requests) were made to Kymco.com.tw and 11% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Kymco.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 538.0 kB (20%)

Content Size

2.7 MB

After Optimization

2.2 MB

In fact, the total size of Ionex.global main page is 2.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 64.0 kB

  • Original 83.0 kB
  • After minification 80.8 kB
  • After compression 19.0 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 64.0 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 108.8 kB

  • Original 1.4 MB
  • After minification 1.3 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. Ionex images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 36.0 kB

  • Original 860.4 kB
  • After minification 860.4 kB
  • After compression 824.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-80%

Potential reduce by 329.2 kB

  • Original 410.8 kB
  • After minification 410.1 kB
  • After compression 81.6 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. Ionex.global needs all CSS files to be minified and compressed as it can save up to 329.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (46%)

Requests Now

71

After Optimization

38

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

Accessibility Review

ionex.global accessibility score

57

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

ionex.global best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ionex.global SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ionex.global can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Ionex.global 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

Open Graph data is detected on the main page of Ionex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: