Tools & Wizards About Us
intofree.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

intofree.jp

AUNオフィシャルブログ「小っちゃな世界でいい、ヒーローになろう。」 | 生きたい「自分の人生」を手に入れたい起業家、ビジネスマン、社長、すべてのリーダー志望者のための次世代の成功法則・進化した自己啓発メソッドを公開。

Page Load Speed

8.6 sec in total

First Response

1.4 sec

Resources Loaded

6.9 sec

Page Rendered

334 ms

intofree.jp screenshot

About Website

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

ども、ＡＵＮです。１１月２７日～２９日まで東京出張でした。メインはセミナーです。以前募集していたＨＥＲＯＥＳというクラブのラストセミナーです。

Visit intofree.jp

Key Findings

We analyzed Intofree.jp page load time and found that the first response time was 1.4 sec and then it took 7.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

intofree.jp performance score

0

Network Requests Diagram

intofree.jp

1423 ms

style.css

920 ms

comment-style.css

576 ms

jquery.js

1197 ms

jquery-migrate.min.js

570 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 83% of them (58 requests) were addressed to the original Intofree.jp, 4% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Intofree.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 827.3 kB (30%)

Content Size

2.8 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intofree.jp main page is 2.8 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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 38.4 kB

  • Original 48.7 kB
  • After minification 46.9 kB
  • After compression 10.3 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 38.4 kB or 79% of the original size.

Image Optimization

-14%

Potential reduce by 291.4 kB

  • Original 2.1 MB
  • After minification 1.8 MB

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, Intofree needs image optimization as it can save up to 291.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 237.8 kB

  • Original 359.6 kB
  • After minification 357.4 kB
  • After compression 121.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 237.8 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 259.8 kB

  • Original 313.1 kB
  • After minification 299.3 kB
  • After compression 53.3 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. Intofree.jp needs all CSS files to be minified and compressed as it can save up to 259.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (52%)

Requests Now

67

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intofree.jp

intofree.jp

1423 ms

style.css

style.css

920 ms

comment-style.css

comment-style.css

576 ms

jquery.js

jquery.js

1197 ms

jquery-migrate.min.js

jquery-migrate.min.js

570 ms

modernizr.js

modernizr.js

374 ms

jscript.js

jscript.js

767 ms

scroll.js

scroll.js

587 ms

comment.js

comment.js

602 ms

fixed_ad.js

fixed_ad.js

767 ms

header.js

header.js

776 ms

owl.carousel.css

owl.carousel.css

785 ms

owl.carousel.min.js

owl.carousel.min.js

1281 ms

japanese.css

japanese.css

933 ms

wp-embed.min.js

wp-embed.min.js

529 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

771 ms

background.png

background.png

542 ms

menu_background.gif

menu_background.gif

184 ms

shadow.png

shadow.png

188 ms

icon_home.png

icon_home.png

174 ms

icon_search.png

icon_search.png

185 ms

head-back2.jpg

head-back2.jpg

395 ms

header3.png

header3.png

2337 ms

icon_rss.gif

icon_rss.gif

396 ms

icon_facebook.gif

icon_facebook.gif

396 ms

freebanner.png

freebanner.png

1902 ms

12316621_651082741660799_8426332055447278726_n-181x181.jpg

12316621_651082741660799_8426332055447278726_n-181x181.jpg

852 ms

icon_category.gif

icon_category.gif

551 ms

icon_comment.gif

icon_comment.gif

553 ms

spinsnetwork-181x181.png

spinsnetwork-181x181.png

1440 ms

image1-181x181.jpg

image1-181x181.jpg

950 ms

qa13-181x181.png

qa13-181x181.png

1530 ms

headline_background.gif

headline_background.gif

1024 ms

blogranking.jpg

blogranking.jpg

1715 ms

dot1.gif

dot1.gif

1197 ms

482280_585209494842515_429464554_n-181x181.jpg

482280_585209494842515_429464554_n-181x181.jpg

1535 ms

400754_626185364078261_1159593485_n-181x181.png

400754_626185364078261_1159593485_n-181x181.png

2014 ms

successmind-181x181.png

successmind-181x181.png

1974 ms

1375857_696147693748694_1686425904_n-181x181.png

1375857_696147693748694_1686425904_n-181x181.png

2210 ms

68674_558274727535992_1640561364_n-181x181.png

68674_558274727535992_1640561364_n-181x181.png

2650 ms

bullet1.gif

bullet1.gif

2089 ms

prof.png

prof.png

2875 ms

line_image.png

line_image.png

3092 ms

facebook_image.png

facebook_image.png

3279 ms

officialsite_image.png

officialsite_image.png

2751 ms

400754_626185364078261_1159593485_n-177x104.png

400754_626185364078261_1159593485_n-177x104.png

3412 ms

19421_559202434109888_1941040751_n-177x104.png

19421_559202434109888_1941040751_n-177x104.png

3010 ms

1375857_696147693748694_1686425904_n-177x104.png

1375857_696147693748694_1686425904_n-177x104.png

3425 ms

531076_585856254777839_1677433606_n-177x104.png

531076_585856254777839_1677433606_n-177x104.png

3085 ms

482280_585209494842515_429464554_n-177x104.jpg

482280_585209494842515_429464554_n-177x104.jpg

3200 ms

68674_558274727535992_1640561364_n-177x104.png

68674_558274727535992_1640561364_n-177x104.png

3945 ms

EBDs_6aPA7I

EBDs_6aPA7I

117 ms

all.js

all.js

321 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

26 ms

www-embed-player.js

www-embed-player.js

50 ms

base.js

base.js

139 ms

successmind-177x104.png

successmind-177x104.png

3160 ms

aun-blog2.jpg

aun-blog2.jpg

3236 ms

arrow1.gif

arrow1.gif

3288 ms

return_top.png

return_top.png

3330 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

53 ms

ad_status.js

ad_status.js

68 ms

slider_arrow2.png

slider_arrow2.png

3231 ms

slider_arrow1.png

slider_arrow1.png

3207 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

45 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

46 ms

122 ms

xd_arbiter.php

xd_arbiter.php

164 ms

xd_arbiter.php

xd_arbiter.php

290 ms

mobile.css

mobile.css

542 ms

SEO Factors

intofree.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intofree.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Intofree.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

intofree.jp

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