Tools & Wizards About Us
itti.jp screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

itti.jp

新宿のホームページ制作会社 ITTI（イッティ）

Page Load Speed

4.4 sec in total

First Response

533 ms

Resources Loaded

3.7 sec

Page Rendered

183 ms

itti.jp screenshot

About Website

Click here to check amazing ITTI content for Japan. Otherwise, check out these important facts you probably never knew about itti.jp

東京新宿のホームページ制作会社として15年以上の実績。SEOでアクセスを増やし、ホームページの売上や収益をアップするのが得意です。企画から制作、運営まで一貫して担当いたします。ホームページの改善やSEOなどでお困りの方はお気軽にお問い合せください

Visit itti.jp

Key Findings

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

Performance Metrics

itti.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value590 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.276

44/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

itti.jp

533 ms

www.itti.jp

893 ms

www.itti.jp

717 ms

52322553-d2ec-4978-a562-a283e86f2c55.js

137 ms

index.css

173 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 81% of them (30 requests) were addressed to the original Itti.jp, 5% (2 requests) were made to Ajax.googleapis.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (893 ms) belongs to the original domain Itti.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.2 kB (58%)

Content Size

100.3 kB

After Optimization

42.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Itti.jp main page is 100.3 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. 15% of websites need less resources to load. Javascripts take 66.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 6.9 kB

  • Original 9.4 kB
  • After minification 7.2 kB
  • After compression 2.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 2.2 kB, which is 23% 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 6.9 kB or 73% of the original size.

Image Optimization

-6%

Potential reduce by 18 B

  • Original 295 B
  • After minification 277 B

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. ITTI images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 32.6 kB

  • Original 66.8 kB
  • After minification 62.9 kB
  • After compression 34.2 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 32.6 kB or 49% of the original size.

CSS Optimization

-79%

Potential reduce by 18.7 kB

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

Requests Breakdown

Number of requests can be reduced by 28 (88%)

Requests Now

32

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

itti.jp

itti.jp

533 ms

www.itti.jp

www.itti.jp

893 ms

www.itti.jp

www.itti.jp

717 ms

52322553-d2ec-4978-a562-a283e86f2c55.js

52322553-d2ec-4978-a562-a283e86f2c55.js

137 ms

index.css

index.css

173 ms

font-m.css

font-m.css

343 ms

css

css

24 ms

jquery.min.js

jquery.min.js

56 ms

jquery-ui.min.js

jquery-ui.min.js

76 ms

jquery.slidescroll.js

jquery.slidescroll.js

439 ms

function.js

function.js

458 ms

mjl.js

mjl.js

683 ms

run.js

run.js

513 ms

copyright.js

copyright.js

513 ms

global.css

global.css

346 ms

basic.css

basic.css

415 ms

index-page.css

index-page.css

441 ms

analytics.js

analytics.js

53 ms

h-logo.gif

h-logo.gif

173 ms

h-company-btn-mark.gif

h-company-btn-mark.gif

173 ms

h-shadow-line.gif

h-shadow-line.gif

174 ms

h-group-mark-konwlege.gif

h-group-mark-konwlege.gif

154 ms

h-group-mark-support.gif

h-group-mark-support.gif

175 ms

h-g-nav-line.png

h-g-nav-line.png

146 ms

m-local-nav-arrow.gif

m-local-nav-arrow.gif

292 ms

r-banner-support.gif

r-banner-support.gif

306 ms

dot-gray.gif

dot-gray.gif

342 ms

f-nav-list-mark.png

f-nav-list-mark.png

343 ms

f-totop-back.gif

f-totop-back.gif

344 ms

f-btn-totop.gif

f-btn-totop.gif

343 ms

f-banner-itti.gif

f-banner-itti.gif

436 ms

f-logo.gif

f-logo.gif

457 ms

f-btn-totop_o.gif

f-btn-totop_o.gif

479 ms

6FkaXkveXKT6_fNDsDBhAQ.ttf

6FkaXkveXKT6_fNDsDBhAQ.ttf

39 ms

collect

collect

13 ms

font-s.css

font-s.css

173 ms

font-l.css

font-l.css

175 ms

Accessibility Review

itti.jp accessibility score

66

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.

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

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

Image elements do not have [alt] attributes

Best Practices

itti.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

itti.jp SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itti.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Itti.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

itti.jp

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