Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

jht.idv.tw

痞子蔡的創作園地

Page Load Speed

3.9 sec in total

First Response

535 ms

Resources Loaded

3.2 sec

Page Rendered

145 ms

jht.idv.tw screenshot

About Website

Welcome to jht.idv.tw homepage info - get ready to check Jht best content right away, or after learning these important things about jht.idv.tw

Visit jht.idv.tw

Key Findings

We analyzed Jht.idv.tw page load time and found that the first response time was 535 ms and then it took 3.4 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

jht.idv.tw performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

jht.idv.tw

535 ms

l_top.asp

501 ms

left.htm

721 ms

right.htm

721 ms

hotrank.js

879 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 50% of them (9 requests) were addressed to the original Jht.idv.tw, 22% (4 requests) were made to H05.hotrank.com.tw and 22% (4 requests) were made to 0. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Im1.book.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.0 kB (21%)

Content Size

60.5 kB

After Optimization

47.5 kB

In fact, the total size of Jht.idv.tw main page is 60.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 42.9 kB which makes up the majority of the site volume.

HTML Optimization

-42%

Potential reduce by 363 B

  • Original 856 B
  • After minification 822 B
  • After compression 493 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 363 B or 42% of the original size.

Image Optimization

-1%

Potential reduce by 421 B

  • Original 42.9 kB
  • After minification 42.5 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. Jht images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 12.2 kB

  • Original 16.7 kB
  • After minification 15.1 kB
  • After compression 4.5 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 12.2 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jht. According to our analytics all requests are already optimized.

Accessibility Review

jht.idv.tw accessibility score

33

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

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

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

jht.idv.tw best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

jht.idv.tw SEO score

67

Search Engine Optimization Advices

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 Jht.idv.tw 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 Jht.idv.tw 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 Jht. 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: