Tools & Wizards About Us

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

takedacastle.jp

【公式】竹田城 城下町 ホテルEN｜竹田城跡に最も近く歴史の詰まったホテル

Page Load Speed

9.4 sec in total

First Response

1.2 sec

Resources Loaded

7.7 sec

Page Rendered

399 ms

About Website

Click here to check amazing Takedacastle content for Japan. Otherwise, check out these important facts you probably never knew about takedacastle.jp

大阪から約90分。竹田城跡ふもとで400年の歴史を持つ旧酒造場をリノベートした、小規模分散型ホテル。VMG系列のホテルで、まち全体をホテルとして楽しむ、特別なリラックスを。ご予約は公式サイトが一番お得です。

Visit takedacastle.jp

Key Findings

We analyzed Takedacastle.jp page load time and found that the first response time was 1.2 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

takedacastle.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value29.7 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value2,690 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

takedacastle.jp

1211 ms

reset.css

339 ms

top.css

521 ms

wp_style.css

350 ms

modules.css

554 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 54% of them (68 requests) were addressed to the original Takedacastle.jp, 12% (15 requests) were made to Www7.489ban.net and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Takedacastle.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 384.1 kB (23%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Takedacastle.jp 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 22.0 kB

  • Original 30.7 kB
  • After minification 28.7 kB
  • After compression 8.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 22.0 kB or 72% of the original size.

Image Optimization

-8%

Potential reduce by 91.8 kB

  • Original 1.2 MB
  • After minification 1.1 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. Takedacastle images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 245.7 kB

  • Original 386.4 kB
  • After minification 345.6 kB
  • After compression 140.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 245.7 kB or 64% of the original size.

CSS Optimization

-79%

Potential reduce by 24.6 kB

  • Original 31.0 kB
  • After minification 23.2 kB
  • After compression 6.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. Takedacastle.jp needs all CSS files to be minified and compressed as it can save up to 24.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (55%)

Requests Now

120

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

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

Links do not have a discernible name

Best Practices

takedacastle.jp best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

takedacastle.jp SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Takedacastle.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 Takedacastle.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 Takedacastle. 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: