Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

incloop.com

インクループ株式会社|神奈川県相模原市 ホームページ制作、WEBマーケティング

Page Load Speed

11.5 sec in total

First Response

2.6 sec

Resources Loaded

8 sec

Page Rendered

859 ms

incloop.com screenshot

About Website

Click here to check amazing Incloop content for Japan. Otherwise, check out these important facts you probably never knew about incloop.com

ホームページを作ったのに期待したほどお問い合わせがないというお悩みはありませんか?弊社は5年前からホームページを活用して集客を行う「コンテンツマーケティング」を実践し、現在では毎月30万ページビューを達成し、広告費を一切かけない集客を達成することができました。そのノウハウをお伝えすることを私達は目的としています。

Visit incloop.com

Key Findings

We analyzed Incloop.com page load time and found that the first response time was 2.6 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

incloop.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

incloop.com

2637 ms

wp-emoji-release.min.js

507 ms

widget.css

344 ms

crayon.min.css

369 ms

classic.css

372 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 94% of them (136 requests) were addressed to the original Incloop.com, 2% (3 requests) were made to S.gravatar.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Incloop.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 544.2 kB (24%)

Content Size

2.2 MB

After Optimization

1.7 MB

In fact, the total size of Incloop.com main page is 2.2 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 102.6 kB

  • Original 126.0 kB
  • After minification 122.3 kB
  • After compression 23.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 102.6 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 22.4 kB

  • Original 1.5 MB
  • After minification 1.5 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. Incloop images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 261.2 kB

  • Original 403.1 kB
  • After minification 372.6 kB
  • After compression 141.9 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 261.2 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 158.1 kB

  • Original 192.2 kB
  • After minification 166.6 kB
  • After compression 34.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. Incloop.com needs all CSS files to be minified and compressed as it can save up to 158.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 90 (63%)

Requests Now

143

After Optimization

53

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

Accessibility Review

incloop.com accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

incloop.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

incloop.com SEO score

92

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

High

Tap targets are not sized appropriately

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 Incloop.com 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 Incloop.com 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

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