Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

plandosee.com

Plan・Do・See Inc.

Page Load Speed

3.6 sec in total

First Response

989 ms

Resources Loaded

2.5 sec

Page Rendered

102 ms

plandosee.com screenshot

About Website

Visit plandosee.com now to see the best up-to-date Plan Do See content for Japan and also check out these interesting facts you probably never knew about plandosee.com

ホテルやレストランを世界中に展開する株式会社Plan・Do・Seeの公式ウェブサイトです。

Visit plandosee.com

Key Findings

We analyzed Plandosee.com page load time and found that the first response time was 989 ms and then it took 2.6 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

plandosee.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

plandosee.com

989 ms

www.plandosee-global.com

240 ms

slide-normalize.css

20 ms

qRubjWN_X3DCeQRX175qYkkTe03fqLdNT60AiWUQ2NCfenS2f4e6pUJ6wRMU5QwXFmvuFA9uZeZyZe9XjRMuZeIUjDwk5eZRZQb-pWiaiko3deB0ZeNDZA9lZhUzjcBCOcFzdPU3deB0ZeNDZA9lZhUzjcBCOcFzdPUCdhFydeyzSabCjAuoOW4TShU8pPuUdco0O1FUiABkZWF3jAF8OcFzdP37OcBlpPuk-WFCZWqlSAo0dKoDSWmyScmDSeBRZPoRdhXKIeZkZA81-YblShB0Sku3ScvKfAZuiYmkjPu3ifG4f4gTIMMjMkMfH6qJqAqbMg6FJMJ7fbRHmsMMeMb6MKG4fJuTIMMj2KMfH6qJqcqbMg6BJMJ7fbKQ-sMMeMv6MKG4f4sTIMMjgKMfH6qJ8AqbMg6bJMJ7fbK5-sMMeMS6MKG4fJNTIMMjIPMfH6qJ8cqbMg64JMJ7fbKW-sMMegw6MKG4fJZmIMIjMkMfH6qJ6u9bMs6FJMJ7fbKImsMgeMb6MKG4fJmmIMIj2KMfH6qJxubbMs6BJMJ7fbKMmsMgeMv6MKG4fJBmIMIjgkMfH6qJ689bMs6sJMJ7fbKYmsMgeM66MKG4fJymIMIjIKMfqMeA8H7Ugb.js

55 ms

d

398 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Plandosee.com, 56% (22 requests) were made to and 15% (6 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (989 ms) belongs to the original domain Plandosee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 257.8 kB (15%)

Content Size

1.7 MB

After Optimization

1.4 MB

In fact, the total size of Plandosee.com main page is 1.7 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 220.5 kB

  • Original 245.3 kB
  • After minification 244.9 kB
  • After compression 24.7 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 220.5 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 5.3 kB

  • Original 1.4 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. Plan Do See images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (27%)

Requests Now

15

After Optimization

11

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

Accessibility Review

plandosee.com accessibility score

97

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.

Best Practices

plandosee.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

plandosee.com SEO score

93

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plandosee.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Plandosee.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 description is not detected on the main page of Plan Do See. 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: