midorihotel.com website review

188 files are served with short cache lifetimes, so returning visitors download them again (6.9 MB).

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.4 s faster on a phone.

20 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.

About 435 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

A phone's processor spends 10.7 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

71 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (YouTube, Google CDN and Google Maps and others), adding 4.5 MB and 1.4 s of main-thread time.

YouTube costs a phone 492 ms of main-thread work and 991 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google CDN costs a phone 442 ms of main-thread work and 751 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

16 long tasks block the main thread while loading, the longest for 303 ms. During a long task the page ignores taps.

The page has 2,759 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Maps costs a phone 217 ms of main-thread work and 467 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Fonts costs a phone 11 ms of main-thread work and 2.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

33 KiB could be saved by minifying JavaScript.

22 KiB could be saved by minifying CSS.

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 3.2 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 42.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 37.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 43.9 s. Good is under 3.8 s.

Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

The layout shifts by 0.106 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.3 MB in 268 requests on a phone: images 7.6 MB (142), scripts 2.7 MB (48) and fonts 2.0 MB (35). Under 2 MB keeps phones on slow connections fast.

image_2022_04_04T08_17_39_868Z-960x480.png weighs 489 KiB. On a phone connection a single image that size takes seconds.

40 images (4.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

12 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example service2.jpg at 525 px wide, shown at 165 px. Resized copies would save about 8 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 3.77 g of CO₂e: 452.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

14 elements hidden from screen readers can still receive keyboard focus.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 frames have no title, so screen-reader users cannot tell what they contain.

2 tap targets are too small or too close together to hit reliably with a finger.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

3 links have no real href, so search engines can't follow them.

The homepage links to 217 pages on midorihotel.com and 33 external pages.

There is no https://www.midorihotel.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.midorihotel.com/%e9%97%9c%e6%96%bc%e6%88%91%e5%80%91, https://www.midorihotel.com/%e6%97%85%e5%ae%bf%e5%85%a5%e4%bd%8f, https://www.midorihotel.com/%e7%be%8e%e9%a5%8c%e7%94%a8%e9%a4%90, https://www.midorihotel.com/%e6%9c%8d%e5%8b%99%e8%a8%ad%e6%96%bd, https://www.midorihotel.com/%e5%ae%b4%e6%9c%83%e6%b4%bb%e5%8b%95 and https://www.midorihotel.com/%e6%9c%80%e6%96%b0%e6%b6%88%e6%81%af have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.midorihotel.com/%e9%97%9c%e6%96%bc%e6%88%91%e5%80%91, whose canonical is https://www.midorihotel.com/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.midorihotel.com/%e6%9c%80%e6%96%b0%e6%b6%88%e6%81%af has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.midorihotel.com/%e9%97%9c%e6%96%bc%e6%88%91%e5%80%91, https://www.midorihotel.com/%e6%97%85%e5%ae%bf%e5%85%a5%e4%bd%8f, https://www.midorihotel.com/%e7%be%8e%e9%a5%8c%e7%94%a8%e9%a4%90, https://www.midorihotel.com/%e6%9c%8d%e5%8b%99%e8%a8%ad%e6%96%bd, https://www.midorihotel.com/%e5%ae%b4%e6%9c%83%e6%b4%bb%e5%8b%95 and https://www.midorihotel.com/%e6%9c%80%e6%96%b0%e6%b6%88%e6%81%af have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.midorihotel.com/%e6%97%85%e5%ae%bf%e5%85%a5%e4%bd%8f, https://www.midorihotel.com/%e7%be%8e%e9%a5%8c%e7%94%a8%e9%a4%90 and https://www.midorihotel.com/%e6%9c%80%e6%96%b0%e6%b6%88%e6%81%af took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage has only about 123 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.