Tools & Wizards About Us
case-shinjuku.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

case-shinjuku.com

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

Page Load Speed

21.9 sec in total

First Response

1.2 sec

Resources Loaded

8.2 sec

Page Rendered

12.5 sec

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

緩やかなつながりのあるオフィスで世界を広げる、深める、変える クリエイター・エンジニア・起業家・経営者がつながる場 創業の街：新宿・高田馬場でシェアするオフィス シェアオフィス・コワーキングスペースを使う人たち クリエイターの仕事場エンジニ

Visit case-shinjuku.com

Key Findings

We analyzed Case-shinjuku.com page load time and found that the first response time was 1.2 sec and then it took 20.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

case-shinjuku.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value4,710 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

case-shinjuku.com

1178 ms

ai1ec_parsed_css.css

350 ms

style.css

517 ms

style.css

518 ms

style.css

519 ms

Our browser made a total of 185 requests to load all elements on the main page. We found that 84% of them (155 requests) were addressed to the original Case-shinjuku.com, 3% (5 requests) were made to Google.com and 3% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Case-shinjuku.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.3 kB (2%)

Content Size

21.2 MB

After Optimization

20.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Case-shinjuku.com main page is 21.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 19.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 160.8 kB

  • Original 192.8 kB
  • After minification 188.0 kB
  • After compression 32.0 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 160.8 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 111.5 kB

  • Original 19.8 MB
  • After minification 19.7 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

-11%

Potential reduce by 113.2 kB

  • Original 990.0 kB
  • After minification 990.0 kB
  • After compression 876.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 113.2 kB or 11% of the original size.

CSS Optimization

-17%

Potential reduce by 39.8 kB

  • Original 238.7 kB
  • After minification 238.3 kB
  • After compression 199.0 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 39.8 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 103 (59%)

Requests Now

176

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 176 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 46 to 1 for JavaScripts and from 59 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

case-shinjuku.com

case-shinjuku.com

1178 ms

ai1ec_parsed_css.css

ai1ec_parsed_css.css

350 ms

style.css

style.css

517 ms

style.css

style.css

518 ms

style.css

style.css

519 ms

style.css

style.css

520 ms

style.css

style.css

521 ms

style.css

style.css

533 ms

style.css

style.css

688 ms

sbi-styles.min.css

sbi-styles.min.css

689 ms

style.min.css

style.min.css

862 ms

wp-share-buttons.css

wp-share-buttons.css

691 ms

wp-like-me-box.css

wp-like-me-box.css

692 ms

app.css

app.css

708 ms

wp-pure-css-gallery.css

wp-pure-css-gallery.css

858 ms

slick.css

slick.css

865 ms

slick-theme.css

slick-theme.css

866 ms

app.css

app.css

865 ms

app.css

app.css

1061 ms

app-theme.css

app-theme.css

1029 ms

app.css

app.css

1032 ms

style.css

style.css

1032 ms

style.css

style.css

1034 ms

style.css

style.css

1034 ms

style.css

style.css

1211 ms

style.css

style.css

1212 ms

style.css

style.css

1213 ms

style.css

style.css

1213 ms

style.css

style.css

1213 ms

spider.css

spider.css

1233 ms

style.css

style.css

1382 ms

style.css

style.css

1385 ms

style.css

style.css

1383 ms

style.css

style.css

1384 ms

style.css

style.css

1385 ms

style.css

style.css

1407 ms

kitchen.juicer.cc

kitchen.juicer.cc

591 ms

7663892.js

7663892.js

75 ms

api.js

api.js

39 ms

blocks.css

blocks.css

1548 ms

app.css

app.css

1209 ms

app-theme.css

app-theme.css

1050 ms

styles.css

styles.css

1050 ms

sb-type-std.css

sb-type-std.css

1050 ms

sb-type-fb.css

sb-type-fb.css

1075 ms

sb-type-fb-flat.css

sb-type-fb-flat.css

1215 ms

sb-type-ln.css

sb-type-ln.css

1206 ms

sb-type-ln-flat.css

sb-type-ln-flat.css

1052 ms

sb-type-pink.css

sb-type-pink.css

1050 ms

sb-type-rtail.css

sb-type-rtail.css

1049 ms

sb-type-drop.css

sb-type-drop.css

1078 ms

sb-type-think.css

sb-type-think.css

1198 ms

sb-no-br.css

sb-no-br.css

1051 ms

background-parallax.css

background-parallax.css

1045 ms

fallback-classic-theme.css

fallback-classic-theme.css

1045 ms

style.css

style.css

1046 ms

style.css

style.css

1079 ms

app.css

app.css

1047 ms

app-theme.css

app-theme.css

1049 ms

app.css

app.css

1049 ms

app-theme.css

app-theme.css

1048 ms

app.css

app.css

1047 ms

app.js

app.js

1054 ms

index.js

index.js

1036 ms

app.js

app.js

1043 ms

wp-share-buttons.js

wp-share-buttons.js

1038 ms

spider.js

spider.js

1038 ms

app.js

app.js

1040 ms

smooth-scroll.js

smooth-scroll.js

1060 ms

drop-nav.js

drop-nav.js

1036 ms

hash-nav.js

hash-nav.js

1039 ms

app.js

app.js

1040 ms

all.min.js

all.min.js

2110 ms

widgets.js

widgets.js

1044 ms

sidebar-sticky-widget-area.js

sidebar-sticky-widget-area.js

1067 ms

page-top.js

page-top.js

1036 ms

jquery.min.js

jquery.min.js

1212 ms

jquery-migrate.min.js

jquery-migrate.min.js

1042 ms

slick.min.js

slick.min.js

1049 ms

slider.js

slider.js

1093 ms

global-nav.js

global-nav.js

1176 ms

app.js

app.js

1244 ms

index.js

index.js

1239 ms

index.js

index.js

1250 ms

cf7-google-analytics.min.js

cf7-google-analytics.min.js

1250 ms

ivent.min.js

ivent.min.js

1248 ms

helper.js

helper.js

1219 ms

event-fallbacks.js

event-fallbacks.js

1084 ms

motion.min.js

motion.min.js

1256 ms

main.js

main.js

1256 ms

frontend.js

frontend.js

1251 ms

frontend.js

frontend.js

1247 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1214 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1254 ms

wp-polyfill.min.js

wp-polyfill.min.js

1251 ms

index.js

index.js

1251 ms

56869b0294

56869b0294

787 ms

gtm.js

gtm.js

258 ms

sdk.js

sdk.js

193 ms

1720751932.jpg

1720751932.jpg

334 ms

logo.gif

logo.gif

429 ms

embed

embed

370 ms

1720684622.jpg

1720684622.jpg

180 ms

1720590779.jpg

1720590779.jpg

865 ms

sbi-sprite.png

sbi-sprite.png

469 ms

cropped-CASE-logo-1-e1458212289530.gif

cropped-CASE-logo-1-e1458212289530.gif

491 ms

main-image-2023.jpeg

main-image-2023.jpeg

1508 ms

CASE-logo-1024x512.png

CASE-logo-1024x512.png

710 ms

bar-counter-new.jpg

bar-counter-new.jpg

1527 ms

people-working.png

people-working.png

1863 ms

feature-shareoffice.jpg

feature-shareoffice.jpg

1360 ms

feature-community.jpg

feature-community.jpg

1061 ms

soudan-scaled.jpeg

soudan-scaled.jpeg

1581 ms

wifi.png

wifi.png

1222 ms

whiteboard-1.png

whiteboard-1.png

1397 ms

monitor.png

monitor.png

1537 ms

jyutenki.png

jyutenki.png

1569 ms

drink.png

drink.png

1703 ms

snack.png

snack.png

1704 ms

stationary.png

stationary.png

1715 ms

books.png

books.png

1742 ms

cable.png

cable.png

1753 ms

microwave.png

microwave.png

1875 ms

white.jpg

white.jpg

1773 ms

copy-machine.png

copy-machine.png

1793 ms

raminator.png

raminator.png

1812 ms

widgets.js

widgets.js

280 ms

coffee.png

coffee.png

1812 ms

event.png

event.png

1919 ms

toki.png

toki.png

1931 ms

yubin.png

yubin.png

1933 ms

locker.png

locker.png

1955 ms

sdk.js

sdk.js

13 ms

73 ms

meeting-room.png

meeting-room.png

1802 ms

floor-coworking.jpg

floor-coworking.jpg

2195 ms

floor-private.jpg

floor-private.jpg

1958 ms

floor-sharedesk.jpg

floor-sharedesk.jpg

2314 ms

floor-event.jpg

floor-event.jpg

2152 ms

recaptcha__en.js

recaptcha__en.js

25 ms

js

js

53 ms

logo.gif

logo.gif

695 ms

map-case-1024x768.gif

map-case-1024x768.gif

1793 ms

DSC07355-scaled.jpg

DSC07355-scaled.jpg

1844 ms

b4b4c64e9ae781cbf8c12887c4cf7578-96x96.png

b4b4c64e9ae781cbf8c12887c4cf7578-96x96.png

1957 ms

DSC07297-scaled.jpg

DSC07297-scaled.jpg

2004 ms

DSC3244-4-96x96.jpg

DSC3244-4-96x96.jpg

1994 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

164 ms

anchor

anchor

31 ms

4b1198c67aeb32473110c663a3b0030b.jpg

4b1198c67aeb32473110c663a3b0030b.jpg

1891 ms

DSC08531-2-1-scaled.jpg

DSC08531-2-1-scaled.jpg

1920 ms

56869b0294

56869b0294

190 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

12 ms

uHwOhFiU9RfT_VdtBfqn8JJh2736_YS1jvyd5cWfFWI.js

uHwOhFiU9RfT_VdtBfqn8JJh2736_YS1jvyd5cWfFWI.js

37 ms

webworker.js

webworker.js

34 ms

logo_48.png

logo_48.png

24 ms

settings

settings

98 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

50 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

53 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

59 ms

recaptcha__en.js

recaptcha__en.js

41 ms

DSC09974-scaled.jpg

DSC09974-scaled.jpg

1770 ms

DSC08041-1-scaled.jpg

DSC08041-1-scaled.jpg

1472 ms

IMG_5101-scaled.jpg

IMG_5101-scaled.jpg

1359 ms

DSC01562-scaled.jpg

DSC01562-scaled.jpg

1399 ms

DSC05003-scaled-e1717726767831.jpg

DSC05003-scaled-e1717726767831.jpg

1288 ms

922f31a01cf9349a3c6cb8521738c836-96x96.png

922f31a01cf9349a3c6cb8521738c836-96x96.png

1273 ms

case2021.jpg

case2021.jpg

1343 ms

community_logo01.jpg

community_logo01.jpg

1328 ms

298737648_581004860469124_880607586460016459_n-1920x641.png

298737648_581004860469124_880607586460016459_n-1920x641.png

1417 ms

coder-dojo.jpg

coder-dojo.jpg

1267 ms

community_logo04.jpg

community_logo04.jpg

1270 ms

community_logo08.jpg

community_logo08.jpg

1321 ms

community_logo09.jpg

community_logo09.jpg

1311 ms

community_logo12.jpg

community_logo12.jpg

1321 ms

community_logo13.jpg

community_logo13.jpg

1279 ms

logo-jimore.jpg

logo-jimore.jpg

1271 ms

kurachic-banner-logo-domain.jpg

kurachic-banner-logo-domain.jpg

1307 ms

community_logo05.jpg

community_logo05.jpg

1313 ms

community_logo06.jpg

community_logo06.jpg

1310 ms

community_logo11.jpg

community_logo11.jpg

1346 ms

community_logo07.jpg

community_logo07.jpg

1280 ms

community_logo10.jpg

community_logo10.jpg

1273 ms

footer_logo.jpg

footer_logo.jpg

1307 ms

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

100

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

case-shinjuku.com

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: