Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

case-shinjuku.com

CASE Shinjuku | 新宿区高田馬場のシェアオフィス&コワーキングスペース – 新宿区高田馬場駅徒歩1分のシェアオフィスとコワーキングスペースが併設する「シェアするオフィス」。朝9時から夜18時はスタッフが常駐(日祝除く)。高速Wi-Fi・電源、大きな机で仕事や打ち合わせに。一時利用(ドロ...

Page Load Speed

11.1 sec in total

First Response

2.6 sec

Resources Loaded

7.6 sec

Page Rendered

838 ms

case-shinjuku.com screenshot

About Website

Click here to check amazing CASE Shinjuku content for Japan. Otherwise, check out these important facts you probably never knew about case-shinjuku.com

新宿区の高田馬場駅徒歩1分にあるシェアオフィスとコワーキングスペースが併設するシェアするオフィス。窓に囲まれた開放的な約50坪のコワーキングスペースと24時間利用可能な約50坪のシェアオフィス(固定ブース、シェアデスク)、6つの完全に独立し

Visit case-shinjuku.com

Key Findings

We analyzed Case-shinjuku.com page load time and found that the first response time was 2.6 sec and then it took 8.5 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

case-shinjuku.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value38.9 s

0/100

10%

TBT (Total Blocking Time)

Value65,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value88.5 s

0/100

10%

Network Requests Diagram

case-shinjuku.com

2595 ms

153491e0_ai1ec_parsed_css.css

1912 ms

css

26 ms

styles.css

667 ms

icons-font.css

668 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 33% of them (34 requests) were addressed to the original Case-shinjuku.com, 13% (13 requests) were made to Maps.googleapis.com and 13% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Case-shinjuku.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 929.0 kB (29%)

Content Size

3.2 MB

After Optimization

2.3 MB

In fact, the total size of Case-shinjuku.com main page is 3.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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 83.3 kB

  • Original 97.9 kB
  • After minification 83.3 kB
  • After compression 14.6 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 14.6 kB, which is 15% 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 83.3 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 59.8 kB

  • Original 1.9 MB
  • After minification 1.9 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. CASE Shinjuku images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 542.6 kB

  • Original 826.1 kB
  • After minification 823.3 kB
  • After compression 283.5 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 542.6 kB or 66% of the original size.

CSS Optimization

-73%

Potential reduce by 243.4 kB

  • Original 331.1 kB
  • After minification 310.4 kB
  • After compression 87.8 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. Case-shinjuku.com needs all CSS files to be minified and compressed as it can save up to 243.4 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (47%)

Requests Now

99

After Optimization

52

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

Accessibility Review

case-shinjuku.com 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

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

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

Best Practices

case-shinjuku.com 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

case-shinjuku.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Case-shinjuku.com 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 Case-shinjuku.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 CASE Shinjuku. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: