Tools & Wizards About Us
has.jp screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

has.jp

長谷川税理士事務所

Page Load Speed

4.4 sec in total

First Response

536 ms

Resources Loaded

3.8 sec

Page Rendered

83 ms

has.jp screenshot

About Website

Welcome to has.jp homepage info - get ready to check Has best content for Japan right away, or after learning these important things about has.jp

中小企業の会計・税金についてお役に立ちます。東京都千代田区の税理士です。

Visit has.jp

Key Findings

We analyzed Has.jp page load time and found that the first response time was 536 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

has.jp performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

has.jp

536 ms

style.css

179 ms

style.min.css

517 ms

jquery.min.js

15 ms

wp-embed.min.js

366 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 65% of them (26 requests) were addressed to the original Has.jp, 28% (11 requests) were made to Platform.twitter.com and 5% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (751 ms) belongs to the original domain Has.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.2 kB (26%)

Content Size

93.9 kB

After Optimization

69.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Has.jp main page is 93.9 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. 30% of websites need less resources to load. Javascripts take 40.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 15.1 kB

  • Original 21.1 kB
  • After minification 20.5 kB
  • After compression 6.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 15.1 kB or 72% of the original size.

Image Optimization

-12%

Potential reduce by 835 B

  • Original 6.9 kB
  • After minification 6.1 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, Has needs image optimization as it can save up to 835 B or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 865 B

  • Original 40.1 kB
  • After minification 40.1 kB
  • After compression 39.2 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

-28%

Potential reduce by 7.4 kB

  • Original 25.9 kB
  • After minification 25.9 kB
  • After compression 18.5 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. Has.jp needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (81%)

Requests Now

37

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

has.jp

has.jp

536 ms

style.css

style.css

179 ms

style.min.css

style.min.css

517 ms

jquery.min.js

jquery.min.js

15 ms

wp-embed.min.js

wp-embed.min.js

366 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

192 ms

back-long2.png

back-long2.png

212 ms

arrow-right-b.gif

arrow-right-b.gif

217 ms

num-874.gif

num-874.gif

213 ms

num-834.gif

num-834.gif

348 ms

lum100-back.png

lum100-back.png

351 ms

lum100-black.png

lum100-black.png

354 ms

lum100-blue.png

lum100-blue.png

389 ms

arrow-bottom.gif

arrow-bottom.gif

386 ms

lum400-blue.jpg

lum400-blue.jpg

398 ms

lum100-red.png

lum100-red.png

527 ms

lum400-red.jpg

lum400-red.jpg

541 ms

lum100-green.png

lum100-green.png

537 ms

lum400-green.jpg

lum400-green.jpg

558 ms

lum100-sky.png

lum100-sky.png

567 ms

lum400-sky.jpg

lum400-sky.jpg

594 ms

lum100-orange.png

lum100-orange.png

699 ms

widgets.js

widgets.js

47 ms

slate30-white.png

slate30-white.png

714 ms

slate7x100-white.png

slate7x100-white.png

718 ms

rss.png

rss.png

751 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

152 ms

settings

settings

72 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

23 ms

hasetax

hasetax

80 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

22 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

48 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

90 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

73 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

83 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

87 ms

_buildManifest.js

_buildManifest.js

91 ms

_ssgManifest.js

_ssgManifest.js

90 ms

osamu.jpg

osamu.jpg

263 ms

toshiki.jpg

toshiki.jpg

253 ms

Accessibility Review

has.jp accessibility score

65

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.

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

Form elements do not have associated labels

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

has.jp 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

SEO Factors

has.jp SEO score

95

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

has.jp

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