Tools & Wizards About Us
insightlab.jp screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

insightlab.jp

売れるWebデザインの極意 - 広島でWebデザイン制作を手掛けるオフィスハピネス合同会社が運営するブログです

Page Load Speed

6.8 sec in total

First Response

579 ms

Resources Loaded

5.8 sec

Page Rendered

435 ms

insightlab.jp screenshot

About Website

Visit insightlab.jp now to see the best up-to-date Insightlab content for Japan and also check out these interesting facts you probably never knew about insightlab.jp

広島でWebデザイン制作を手掛けるオフィスハピネス合同会社が運営するブログです

Visit insightlab.jp

Key Findings

We analyzed Insightlab.jp page load time and found that the first response time was 579 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

insightlab.jp performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.197

62/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

insightlab.jp

579 ms

992 ms

590 ms

1502_import.css

359 ms

modernizr.js

361 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 19% of them (15 requests) were addressed to the original Insightlab.jp, 40% (32 requests) were made to Cont.insightlab.jp and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Cont.insightlab.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.5 kB (35%)

Content Size

373.7 kB

After Optimization

241.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Insightlab.jp main page is 373.7 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. 50% of websites need less resources to load. Images take 214.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 39.1 kB

  • Original 49.6 kB
  • After minification 44.5 kB
  • After compression 10.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. 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 39.1 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 27.9 kB

  • Original 214.7 kB
  • After minification 186.8 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, Insightlab needs image optimization as it can save up to 27.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-51%

Potential reduce by 38.4 kB

  • Original 75.2 kB
  • After minification 67.0 kB
  • After compression 36.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 38.4 kB or 51% of the original size.

CSS Optimization

-79%

Potential reduce by 27.1 kB

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

Requests Breakdown

Number of requests can be reduced by 25 (33%)

Requests Now

75

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

insightlab.jp

insightlab.jp

579 ms

992 ms

590 ms

1502_import.css

1502_import.css

359 ms

modernizr.js

modernizr.js

361 ms

jquery.min.js

jquery.min.js

5 ms

rollover.js

rollover.js

393 ms

smoothScroll.js

smoothScroll.js

393 ms

loopedslider.js

loopedslider.js

397 ms

flexcroll.js

flexcroll.js

558 ms

unitip.js

unitip.js

718 ms

ranking.js

ranking.js

732 ms

pjs.js

pjs.js

513 ms

reset.css

reset.css

399 ms

common.css

common.css

412 ms

1502_style.css

1502_style.css

622 ms

1502_global.css

1502_global.css

558 ms

bg.gif

bg.gif

576 ms

ga.js

ga.js

12 ms

all.js

all.js

103 ms

bg.png

bg.png

1239 ms

header.gif

header.gif

552 ms

headerLine.gif

headerLine.gif

530 ms

h1.gif

h1.gif

894 ms

widgets.js

widgets.js

77 ms

nav1.gif

nav1.gif

524 ms

nav2.gif

nav2.gif

883 ms

nav3.gif

nav3.gif

888 ms

nav4.gif

nav4.gif

903 ms

h2.gif

h2.gif

1087 ms

sub_tit01.png

sub_tit01.png

1242 ms

btn_01.png

btn_01.png

1246 ms

sub_tit02.png

sub_tit02.png

1249 ms

btn_02.png

btn_02.png

1264 ms

32.jpg

32.jpg

1635 ms

31.jpg

31.jpg

1772 ms

30.jpg

30.jpg

1788 ms

29.jpg

29.jpg

1960 ms

28.jpg

28.jpg

1606 ms

27.jpg

27.jpg

1634 ms

26.jpg

26.jpg

1969 ms

25.jpg

25.jpg

2539 ms

24.jpg

24.jpg

1999 ms

23.jpg

23.jpg

2135 ms

banner01.gif

banner01.gif

2146 ms

banner02.gif

banner02.gif

2323 ms

banner03.gif

banner03.gif

2331 ms

banner04.gif

banner04.gif

2362 ms

banner05.gif

banner05.gif

2517 ms

ranking_tit.png

ranking_tit.png

2514 ms

up.png

up.png

2687 ms

plusone.js

plusone.js

108 ms

__utm.gif

__utm.gif

20 ms

39 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

27 ms

fastbutton

fastbutton

76 ms

xd_arbiter.php

xd_arbiter.php

45 ms

xd_arbiter.php

xd_arbiter.php

87 ms

postmessageRelay

postmessageRelay

51 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

15 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

16 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

26 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

23 ms

rpc:shindig_random.js

rpc:shindig_random.js

36 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

2 ms

js

js

364 ms

201311-womanins.gif

201311-womanins.gif

462 ms

js

js

337 ms

201603-sekaneko_MNbanner160302.gif

201603-sekaneko_MNbanner160302.gif

405 ms

js

js

359 ms

ranking-insight

ranking-insight

471 ms

button.65b4bc8f0d6592fdc51d322b3f197660.js

button.65b4bc8f0d6592fdc51d322b3f197660.js

21 ms

footer.gif

footer.gif

1160 ms

201603-kyojo2_300x80.gif

201603-kyojo2_300x80.gif

1031 ms

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

14 ms

like.php

like.php

74 ms

6kMqU_fzmnN.js

6kMqU_fzmnN.js

63 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

63 ms

jot

jot

85 ms

Accessibility Review

insightlab.jp accessibility score

63

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

<frame> or <iframe> elements do not have a title

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.

Best Practices

insightlab.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

insightlab.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 doesn't use legible font sizes

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 Insightlab.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 Insightlab.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

insightlab.jp

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