Tools & Wizards About Us
hoags.jp screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

hoags.jp

農業参入や養液栽培についてお考えなら株式会社ホーグス

Page Load Speed

6.8 sec in total

First Response

557 ms

Resources Loaded

6.1 sec

Page Rendered

108 ms

hoags.jp screenshot

About Website

Click here to check amazing Hoags content. Otherwise, check out these important facts you probably never knew about hoags.jp

農業参入に興味がございましたら株式会社ホーグスにご相談ください。広大なコネクションを生かしてサポートします。

Visit hoags.jp

Key Findings

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

Performance Metrics

hoags.jp performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

hoags.jp

557 ms

www.hoags.jp

619 ms

import.css

409 ms

jquery.min.js

6 ms

rollover.js

410 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 91% of them (39 requests) were addressed to the original Hoags.jp, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Hoags.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.9 kB (17%)

Content Size

839.6 kB

After Optimization

696.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hoags.jp main page is 839.6 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. Images take 597.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 12.0 kB

  • Original 14.7 kB
  • After minification 11.1 kB
  • After compression 2.7 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 3.5 kB, which is 24% 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 12.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 2.2 kB

  • Original 597.4 kB
  • After minification 595.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. Hoags images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 110.2 kB

  • Original 204.1 kB
  • After minification 183.5 kB
  • After compression 93.8 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 110.2 kB or 54% of the original size.

CSS Optimization

-79%

Potential reduce by 18.5 kB

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

Requests Breakdown

Number of requests can be reduced by 20 (49%)

Requests Now

41

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hoags. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hoags.jp

hoags.jp

557 ms

www.hoags.jp

www.hoags.jp

619 ms

import.css

import.css

409 ms

jquery.min.js

jquery.min.js

6 ms

rollover.js

rollover.js

410 ms

scrollsmoothly.js

scrollsmoothly.js

418 ms

scrolltopcontrol.js

scrolltopcontrol.js

419 ms

fancybox.js

fancybox.js

837 ms

function.js

function.js

419 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

779 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

778 ms

fonts-min.css

fonts-min.css

787 ms

treeview.css

treeview.css

829 ms

treeview-menu.css

treeview-menu.css

836 ms

yahoo-dom-event.js

yahoo-dom-event.js

1513 ms

treeview-min.js

treeview-min.js

1510 ms

element-min.js

element-min.js

1206 ms

base.css

base.css

792 ms

common.css

common.css

800 ms

fancybox.css

fancybox.css

851 ms

style.css

style.css

1160 ms

clear.css

clear.css

1205 ms

analytics.js

analytics.js

51 ms

header_bg.jpg

header_bg.jpg

206 ms

home_btn.jpg

home_btn.jpg

368 ms

logo.jpg

logo.jpg

370 ms

header_tel.jpg

header_tel.jpg

370 ms

header_mail.jpg

header_mail.jpg

406 ms

nav01.jpg

nav01.jpg

408 ms

nav02.jpg

nav02.jpg

615 ms

nav03.jpg

nav03.jpg

774 ms

nav04.jpg

nav04.jpg

775 ms

nav05.jpg

nav05.jpg

784 ms

line_bg.jpg

line_bg.jpg

762 ms

main.jpg

main.jpg

3318 ms

top_banner01.jpg

top_banner01.jpg

1451 ms

top_banner02.jpg

top_banner02.jpg

1327 ms

footer_arrow.jpg

footer_arrow.jpg

1167 ms

footer_logo.jpg

footer_logo.jpg

1336 ms

sprite-menu.gif

sprite-menu.gif

1149 ms

pagetop.png

pagetop.png

1540 ms

collect

collect

28 ms

js

js

60 ms

Accessibility Review

hoags.jp accessibility score

94

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

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hoags.jp SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

hoags.jp

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