Tools & Wizards About Us
hzl.im screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

hzl.im

HZLの閉鎖空間 – どれほどの速さで生きれば、きみに会えるのか。

Page Load Speed

3.1 sec in total

First Response

603 ms

Resources Loaded

2 sec

Page Rendered

488 ms

hzl.im screenshot

About Website

Welcome to hzl.im homepage info - get ready to check Hzl best content right away, or after learning these important things about hzl.im

I'm HZL

Visit hzl.im

Key Findings

We analyzed Hzl.im page load time and found that the first response time was 603 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

hzl.im performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value2,430 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.511

15/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

hzl.im

603 ms

wp-emoji-release.min.js

235 ms

crayon.min.css

369 ms

jquery.fancybox-1.3.4.css

447 ms

twitter-feed.css

501 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 88% of them (22 requests) were addressed to the original Hzl.im, 8% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to . The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Hzl.im.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.2 kB (66%)

Content Size

442.5 kB

After Optimization

152.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Hzl.im main page is 442.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. Javascripts take 229.8 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 24.8 kB

  • Original 35.4 kB
  • After minification 33.6 kB
  • After compression 10.6 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 24.8 kB or 70% of the original size.

JavaScript Optimization

-65%

Potential reduce by 149.8 kB

  • Original 229.8 kB
  • After minification 216.1 kB
  • After compression 80.0 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 149.8 kB or 65% of the original size.

CSS Optimization

-65%

Potential reduce by 115.7 kB

  • Original 177.3 kB
  • After minification 159.7 kB
  • After compression 61.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. Hzl.im needs all CSS files to be minified and compressed as it can save up to 115.7 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (78%)

Requests Now

23

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hzl.im

hzl.im

603 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

235 ms

crayon.min.css

crayon.min.css

369 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

447 ms

twitter-feed.css

twitter-feed.css

501 ms

genericons.css

genericons.css

761 ms

style.css

style.css

643 ms

jquery.js

jquery.js

721 ms

jquery-migrate.min.js

jquery-migrate.min.js

606 ms

crayon.min.js

crayon.min.js

636 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

714 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

776 ms

front.js

front.js

795 ms

front.css

front.css

935 ms

dashicons.min.css

dashicons.min.css

1056 ms

wp-auth-check.min.css

wp-auth-check.min.css

934 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

934 ms

functions.js

functions.js

932 ms

wp-embed.min.js

wp-embed.min.js

971 ms

frontend.js

frontend.js

1049 ms

ga.js

ga.js

137 ms

grey.gif

grey.gif

342 ms

Genericons.svg

Genericons.svg

341 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

29 ms

__utm.gif

__utm.gif

82 ms

Accessibility Review

hzl.im accessibility score

91

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

Links do not have a discernible name

Best Practices

hzl.im 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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hzl.im SEO score

93

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

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

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hzl.im can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Hzl.im 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

hzl.im

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