Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

cocolin.jp

仙台コワーキングスペース&シェアオフィスcocolin(ココリン)|仙台市

Page Load Speed

6.6 sec in total

First Response

95 ms

Resources Loaded

4.7 sec

Page Rendered

1.8 sec

cocolin.jp screenshot

About Website

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

cocolinは仙台市若林区にあるコワーキングスペースです。 仙台駅から徒歩10分、地下鉄五橋駅から徒歩1分の好立地と、法人登記ができるコワーキングスペースとして格安の料金設定が魅力。月額12,000円からあなただけのオフィスをもつことができます。

Visit cocolin.jp

Key Findings

We analyzed Cocolin.jp page load time and found that the first response time was 95 ms and then it took 6.5 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

cocolin.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

cocolin.jp

95 ms

www.cocolin.jp

51 ms

bt

136 ms

require.min.js

61 ms

main-r.min.js

64 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Cocolin.jp, 23% (37 requests) were made to Static.parastorage.com and 20% (33 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.0 MB (59%)

Content Size

6.8 MB

After Optimization

2.8 MB

In fact, the total size of Cocolin.jp main page is 6.8 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. 85% 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. Javascripts take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 143.3 kB

  • Original 170.4 kB
  • After minification 170.2 kB
  • After compression 27.2 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 143.3 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 112.7 kB

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

JavaScript Optimization

-73%

Potential reduce by 3.6 MB

  • Original 5.0 MB
  • After minification 4.9 MB
  • After compression 1.3 MB

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 3.6 MB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 157.1 kB

  • Original 184.2 kB
  • After minification 155.3 kB
  • After compression 27.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. Cocolin.jp needs all CSS files to be minified and compressed as it can save up to 157.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 97 (64%)

Requests Now

151

After Optimization

54

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

Accessibility Review

cocolin.jp accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Best Practices

cocolin.jp best practices score

92

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

Page has valid source maps

SEO Factors

cocolin.jp SEO score

86

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

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

    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 Cocolin.jp 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 Cocolin.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

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