Tools & Wizards About Us
camelotjapan.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

camelotjapan.com

ホテル横浜キャメロットジャパン│トップページ

Page Load Speed

5.1 sec in total

First Response

564 ms

Resources Loaded

4.3 sec

Page Rendered

236 ms

camelotjapan.com screenshot

About Website

Click here to check amazing Camelotjapan content for Japan. Otherwise, check out these important facts you probably never knew about camelotjapan.com

横浜駅前にある婚礼・レストラン・宴会場・宿泊施設を備えた複合宿泊施設です。東京・新宿・新横浜とどこへ行くのも便利なターミナル駅前です。

Visit camelotjapan.com

Key Findings

We analyzed Camelotjapan.com page load time and found that the first response time was 564 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

camelotjapan.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

camelotjapan.com

564 ms

camelot.css

504 ms

bsn.Crossfader.js

348 ms

ga.js

21 ms

top_bg.jpg

1208 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 85% of them (17 requests) were addressed to the original Camelotjapan.com, 10% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Camelotjapan.com.

Page Optimization Overview & Recommendations

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

Content Size

1.6 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-58%

Potential reduce by 2.7 kB

  • Original 4.7 kB
  • After minification 4.2 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 556 B, which is 12% 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 2.7 kB or 58% of the original size.

Image Optimization

-1%

Potential reduce by 14.0 kB

  • Original 1.6 MB
  • After minification 1.6 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. Camelotjapan images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 1.6 kB

  • Original 19.3 kB
  • After minification 18.8 kB
  • After compression 17.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-85%

Potential reduce by 8.1 kB

  • Original 9.5 kB
  • After minification 6.9 kB
  • After compression 1.4 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. Camelotjapan.com needs all CSS files to be minified and compressed as it can save up to 8.1 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Camelotjapan. According to our analytics all requests are already optimized.

Network Requests Diagram

camelotjapan.com

camelotjapan.com

564 ms

camelot.css

camelot.css

504 ms

bsn.Crossfader.js

bsn.Crossfader.js

348 ms

ga.js

ga.js

21 ms

top_bg.jpg

top_bg.jpg

1208 ms

header_back.jpg

header_back.jpg

353 ms

header_logo.jpg

header_logo.jpg

717 ms

top_lang_en.gif

top_lang_en.gif

371 ms

left_back.jpg

left_back.jpg

737 ms

btn_stay.jpg

btn_stay.jpg

957 ms

btn_restaurant.jpg

btn_restaurant.jpg

1403 ms

btn_party.jpg

btn_party.jpg

1409 ms

btn_wedding.jpg

btn_wedding.jpg

1532 ms

top1.jpg

top1.jpg

2367 ms

top2.jpg

top2.jpg

2506 ms

top3.jpg

top3.jpg

3219 ms

top4.jpg

top4.jpg

2836 ms

footer_back.jpg

footer_back.jpg

1765 ms

__utm.gif

__utm.gif

13 ms

collect

collect

63 ms

Accessibility Review

camelotjapan.com accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

camelotjapan.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

camelotjapan.com SEO score

86

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Camelotjapan.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 Camelotjapan.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

camelotjapan.com

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