Tools & Wizards About Us
360.co.jp screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

360.co.jp

Gallery360

Page Load Speed

3.7 sec in total

First Response

931 ms

Resources Loaded

2.6 sec

Page Rendered

153 ms

360.co.jp screenshot

About Website

Welcome to 360.co.jp homepage info - get ready to check 360 best content right away, or after learning these important things about 360.co.jp

Gallery360゜| Omotesando

Visit 360.co.jp

Key Findings

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

Performance Metrics

360.co.jp performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value4.1 s

78/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value3.3 s

93/100

10%

Network Requests Diagram

360.co.jp

931 ms

style.css

1002 ms

module.css

861 ms

default.css

861 ms

css

25 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 53% of them (8 requests) were addressed to the original 360.co.jp, 13% (2 requests) were made to Fonts.gstatic.com and 13% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain 360.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.0 kB (25%)

Content Size

146.0 kB

After Optimization

109.1 kB

  • HTML
  • Images
  • CSS

In fact, the total size of 360.co.jp main page is 146.0 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. 25% of websites need less resources to load. Images take 119.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.1 kB

  • Original 14.6 kB
  • After minification 14.3 kB
  • After compression 4.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 10.1 kB or 69% of the original size.

Image Optimization

-14%

Potential reduce by 17.2 kB

  • Original 119.0 kB
  • After minification 101.8 kB

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. Obviously, 360 needs image optimization as it can save up to 17.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-78%

Potential reduce by 9.6 kB

  • Original 12.4 kB
  • After minification 10.0 kB
  • After compression 2.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. 360.co.jp needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (25%)

Requests Now

12

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

360.co.jp

360.co.jp

931 ms

style.css

style.css

1002 ms

module.css

module.css

861 ms

default.css

default.css

861 ms

css

css

25 ms

sdk.js

sdk.js

37 ms

logo.png

logo.png

342 ms

noguchi.jpg

noguchi.jpg

681 ms

icon.png

icon.png

175 ms

hp_image.jpg

hp_image.jpg

757 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

20 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

21 ms

126 ms

xd_arbiter.php

xd_arbiter.php

18 ms

xd_arbiter.php

xd_arbiter.php

33 ms

Accessibility Review

360.co.jp accessibility score

89

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

360.co.jp 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

360.co.jp SEO score

98

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

High

Tap targets are not sized appropriately

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 360.co.jp 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 360.co.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

360.co.jp

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