Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

hi2100.com

Hi2100

Page Load Speed

2 sec in total

First Response

365 ms

Resources Loaded

1.5 sec

Page Rendered

170 ms

hi2100.com screenshot

About Website

Visit hi2100.com now to see the best up-to-date Hi2100 content for Taiwan and also check out these interesting facts you probably never knew about hi2100.com

Visit hi2100.com

Key Findings

We analyzed Hi2100.com page load time and found that the first response time was 365 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

hi2100.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value260 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

hi2100.com

365 ms

main.htm

326 ms

top.htm

139 ms

left.htm

249 ms

plusone.js

57 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 19% of them (10 requests) were addressed to the original Hi2100.com, 31% (16 requests) were made to Tpc.googlesyndication.com and 15% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (365 ms) belongs to the original domain Hi2100.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.6 kB (40%)

Content Size

439.2 kB

After Optimization

265.5 kB

In fact, the total size of Hi2100.com main page is 439.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 261.6 kB which makes up the majority of the site volume.

HTML Optimization

-52%

Potential reduce by 835 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 781 B

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 835 B or 52% of the original size.

Image Optimization

-2%

Potential reduce by 3.6 kB

  • Original 176.0 kB
  • After minification 172.3 kB

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. Hi2100 images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 169.2 kB

  • Original 261.6 kB
  • After minification 257.6 kB
  • After compression 92.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 169.2 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (42%)

Requests Now

50

After Optimization

29

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

Accessibility Review

hi2100.com accessibility score

45

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

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.

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

hi2100.com 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hi2100.com SEO score

82

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hi2100.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Hi2100.com main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Hi2100. 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: