Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

ohi.org.tw

OHI網路書城 網路防火牆錯誤

Page Load Speed

3.5 sec in total

First Response

407 ms

Resources Loaded

3 sec

Page Rendered

107 ms

ohi.org.tw screenshot

About Website

Visit ohi.org.tw now to see the best up-to-date Ohi Org content and also check out these interesting facts you probably never knew about ohi.org.tw

Visit ohi.org.tw

Key Findings

We analyzed Ohi.org.tw page load time and found that the first response time was 407 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ohi.org.tw performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

index.php

407 ms

jsapi

64 ms

selectmenu_lang.js.php

382 ms

json.php

386 ms

main.css

379 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 50% of them (7 requests) were addressed to the original Ohi.org.tw, 43% (6 requests) were made to Ajax.googleapis.com and 7% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (767 ms) belongs to the original domain Ohi.org.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.7 kB (83%)

Content Size

121.5 kB

After Optimization

20.8 kB

In fact, the total size of Ohi.org.tw main page is 121.5 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. 25% of websites need less resources to load. Images take 59.1 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 2.3 kB

  • Original 3.7 kB
  • After minification 3.1 kB
  • After compression 1.3 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. This page needs HTML code to be minified as it can gain 576 B, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 2.3 kB or 63% of the original size.

Image Optimization

-87%

Potential reduce by 51.2 kB

  • Original 59.1 kB
  • After minification 7.9 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. Obviously, Ohi Org needs image optimization as it can save up to 51.2 kB or 87% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-80%

Potential reduce by 47.2 kB

  • Original 58.8 kB
  • After minification 48.0 kB
  • After compression 11.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. Ohi.org.tw needs all CSS files to be minified and compressed as it can save up to 47.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (23%)

Requests Now

13

After Optimization

10

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

Accessibility Review

ohi.org.tw accessibility score

79

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.

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

Best Practices

ohi.org.tw 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ohi.org.tw SEO score

67

Search Engine Optimization Advices

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 Ohi.org.tw 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 Ohi.org.tw 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 description is not detected on the main page of Ohi Org. 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: