Tools & Wizards About Us
hello-pc.net screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

hello-pc.net

ハロー！パソコン教室公式サイト - 個別指導で学べるパソコン教室

Page Load Speed

13.5 sec in total

First Response

765 ms

Resources Loaded

12.4 sec

Page Rendered

408 ms

hello-pc.net screenshot

About Website

Welcome to hello-pc.net homepage info - get ready to check Hello Pc best content for Japan right away, or after learning these important things about hello-pc.net

ハロー！パソコン教室の公式サイトです。ハロー！は「個別指導」で学べるクチコミで人気のパソコン教室。パソコン初心者からマイクロソフトオフィススペシャリスト資格取得、生成AIまで幅広く学べます。このサイトでは全国の教室を検索できます。

Visit hello-pc.net

Key Findings

We analyzed Hello-pc.net page load time and found that the first response time was 765 ms and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

hello-pc.net performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

hello-pc.net

765 ms

www.hello-pc.net

4002 ms

import_index.css

315 ms

slider.css

323 ms

jquery-1.6.1.min.js

1193 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 75% of them (88 requests) were addressed to the original Hello-pc.net, 9% (10 requests) were made to Google.com and 3% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Hello-pc.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.5 kB (23%)

Content Size

1.4 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hello-pc.net main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 945.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 41.1 kB

  • Original 52.6 kB
  • After minification 38.8 kB
  • After compression 11.5 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 13.8 kB, which is 26% 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 41.1 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 70.3 kB

  • Original 945.5 kB
  • After minification 875.2 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. Hello Pc images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 159.8 kB

  • Original 306.9 kB
  • After minification 292.0 kB
  • After compression 147.1 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 159.8 kB or 52% of the original size.

CSS Optimization

-83%

Potential reduce by 38.4 kB

  • Original 46.3 kB
  • After minification 36.2 kB
  • After compression 7.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. Hello-pc.net needs all CSS files to be minified and compressed as it can save up to 38.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (36%)

Requests Now

107

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hello-pc.net

hello-pc.net

765 ms

www.hello-pc.net

www.hello-pc.net

4002 ms

import_index.css

import_index.css

315 ms

slider.css

slider.css

323 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

1193 ms

jquery.cycle.all.js

jquery.cycle.all.js

869 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

712 ms

cmn.css

cmn.css

673 ms

index.css

index.css

492 ms

conversion.js

conversion.js

16 ms

cse.js

cse.js

18 ms

bg.gif

bg.gif

329 ms

bg_wrapper.gif

bg_wrapper.gif

490 ms

campaign_right02.png

campaign_right02.png

836 ms

bg_contents.png

bg_contents.png

681 ms

bnr_taiken_header.jpg

bnr_taiken_header.jpg

721 ms

logo.gif

logo.gif

562 ms

subnavi.gif

subnavi.gif

959 ms

gnavi.jpg

gnavi.jpg

1314 ms

top_btn_search.jpg

top_btn_search.jpg

1229 ms

top_btn_voice.jpg

top_btn_voice.jpg

1312 ms

top_campaign_s.png

top_campaign_s.png

2137 ms

top_campaign_s_mos.png

top_campaign_s_mos.png

2387 ms

cse.js

cse.js

142 ms

top_voice.png

top_voice.png

1685 ms

top_joseikin.png

top_joseikin.png

1690 ms

bunner_campaign.jpg

bunner_campaign.jpg

2257 ms

top_nayami.png

top_nayami.png

1847 ms

bg_navi.gif

bg_navi.gif

2005 ms

top_bg_map.gif

top_bg_map.gif

2019 ms

title01.jpg

title01.jpg

2387 ms

icon_con01.gif

icon_con01.gif

2382 ms

icon_con02.gif

icon_con02.gif

2375 ms

icon_con03.gif

icon_con03.gif

2458 ms

icon_con04.gif

icon_con04.gif

2601 ms

icon_con05.gif

icon_con05.gif

2689 ms

icon_con06.gif

icon_con06.gif

2706 ms

icon_con07.gif

icon_con07.gif

2713 ms

icon_con08.gif

icon_con08.gif

2719 ms

icon_onen.gif

icon_onen.gif

2778 ms

dot_919.gif

dot_919.gif

2942 ms

title02.jpg

title02.jpg

3157 ms

bodynavi_r_title.jpg

bodynavi_r_title.jpg

3333 ms

bodynavi_r_ico01.jpg

bodynavi_r_ico01.jpg

3045 ms

bodynavi_r_ico02.jpg

bodynavi_r_ico02.jpg

3083 ms

bodynavi_r_ico03.jpg

bodynavi_r_ico03.jpg

3095 ms

bodynavi_r_ico04.jpg

bodynavi_r_ico04.jpg

3299 ms

bodynavi_r_ico05.jpg

bodynavi_r_ico05.jpg

3396 ms

widgets.js

widgets.js

17 ms

analytics.js

analytics.js

63 ms

tag.js

tag.js

42 ms

86 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

44 ms

tag

tag

24 ms

syndication

syndication

117 ms

306347403458514945

306347403458514945

209 ms

jsapi

jsapi

59 ms

78 ms

collect

collect

85 ms

default+ja.css

default+ja.css

18 ms

default.css

default.css

25 ms

default+ja.I.js

default+ja.I.js

25 ms

default.css

default.css

61 ms

ga-audiences

ga-audiences

28 ms

async-ads.js

async-ads.js

68 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

27 ms

small-logo.png

small-logo.png

23 ms

search_box_icon.png

search_box_icon.png

28 ms

clear.gif

clear.gif

20 ms

bodynavi_r_mt01.jpg

bodynavi_r_mt01.jpg

4255 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

3 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

5 ms

____normal.gif

____normal.gif

284 ms

banner_mos.jpg

banner_mos.jpg

3167 ms

bodynavi_r_mt02.jpg

bodynavi_r_mt02.jpg

3153 ms

jot

jot

27 ms

icon_course.gif

icon_course.gif

3001 ms

banner_ipad.jpg

banner_ipad.jpg

3130 ms

bodynavi_r_arrow.jpg

bodynavi_r_arrow.jpg

2909 ms

dot_CDC.gif

dot_CDC.gif

3022 ms

title03.gif

title03.gif

2798 ms

top_media.png

top_media.png

2879 ms

banner_antivirus.jpg

banner_antivirus.jpg

3057 ms

banner_kyufu.jpg

banner_kyufu.jpg

2994 ms

banner_hke.jpg

banner_hke.jpg

2941 ms

banner_nod.gif

banner_nod.gif

2680 ms

banner_biz.jpg

banner_biz.jpg

2902 ms

26468.jpg

26468.jpg

2845 ms

264682.jpg

264682.jpg

3030 ms

26468.jpg

26468.jpg

2970 ms

bunner_inst.jpg

bunner_inst.jpg

2975 ms

bnr_mos.jpg

bnr_mos.jpg

2803 ms

footerbt_bg.jpg

footerbt_bg.jpg

2799 ms

footer_bt.jpg

footer_bt.jpg

2851 ms

footerbt01.gif

footerbt01.gif

3047 ms

footerbt02.gif

footerbt02.gif

2917 ms

footerbt04.gif

footerbt04.gif

2838 ms

footerbt06.gif

footerbt06.gif

2852 ms

footerbt10.gif

footerbt10.gif

2867 ms

footerbt11.jpg

footerbt11.jpg

3137 ms

top_r_web.gif

top_r_web.gif

3042 ms

top_r_mm.gif

top_r_mm.gif

2907 ms

top_r_sozai.gif

top_r_sozai.gif

2821 ms

top_r_aa.gif

top_r_aa.gif

2790 ms

top_r_mybook.gif

top_r_mybook.gif

2816 ms

footerbt07.gif

footerbt07.gif

3004 ms

footerbt08.gif

footerbt08.gif

2870 ms

footerbt03.gif

footerbt03.gif

2856 ms

footerbt_nenga2016.gif

footerbt_nenga2016.gif

3102 ms

footerbt_shop.jpg

footerbt_shop.jpg

2568 ms

footerbt_r.gif

footerbt_r.gif

2558 ms

footer_bg01.jpg

footer_bg01.jpg

2802 ms

footer_bg02.jpg

footer_bg02.jpg

2779 ms

foot_logo.gif

foot_logo.gif

2687 ms

slider_arrows.png

slider_arrows.png

2580 ms

bullets.png

bullets.png

2548 ms

ya.js

ya.js

328 ms

Accessibility Review

hello-pc.net accessibility score

93

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

Links do not have a discernible name

Best Practices

hello-pc.net best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hello-pc.net SEO score

99

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hello-pc.net 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 Hello-pc.net 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

hello-pc.net

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