Website review, no card needed

onuki.tv logo

onuki.tv website review

Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 81 checks

This review found 45 issues worth fixing on onuki.tv, 22 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
7.3 s5.8 sJun 13Nov 77.0 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20266.0 s
Jun 27, 20266.2 s
Jul 4, 20266.6 s
Sep 5, 20266.8 s
Sep 12, 20266.7 s
Sep 19, 20266.9 s
Sep 26, 20267.2 s
Nov 7, 20267.0 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of onuki.tv (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. onuki.tv at 1.6 s1.6 s
  2. onuki.tv at 3.2 s3.2 s
  3. onuki.tv at 4.8 s4.8 s
  4. onuki.tv at 6.4 s6.4 s
  5. onuki.tv at 8.0 s8.0 s
  6. onuki.tv at 9.6 s9.6 s
  7. onuki.tv at 11.2 s11.2 s
  8. onuki.tv at 12.8 s12.8 s

Speed

16 to fix46
  • Use efficient cache lifetimes

    27.9 s · 11.1 MB

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

  • Render-blocking requests

    16.4 s

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

  • Reduce unused CSS

    10.3 s · 2.0 MB

    About 2.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.3 s faster on a phone.

  • Reduce unused JavaScript

    4.7 s · 1,019 KiB

    About 1,019 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

  • Improve image delivery

    2.5 s · 2.9 MB

    15 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Font display

    1.7 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.7 s).

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 4.5 s

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

  • Document request latency

    800 ms · 154 KiB

    The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    806 ms

    Reduce initial server response time. Google estimates savings of 806 ms on a phone.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and sakura.ne.jp and others), adding 646 KiB and 739 ms of main-thread time.

  • Minify CSS

    600 ms · 139 KiB

    139 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    300 ms · 69 KiB

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

  • Google Tag Manager adds 263 ms

    263 ms

    Google Tag Manager costs a phone 263 ms of main-thread work and 299 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.

  • 20 long tasks on the main thread

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

  • Server response: 906 ms

    906 ms

    Your server takes 906 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

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

Core Web Vitals

5 to fix56
  • First Contentful Paint: 16.0 s

    16.0 s

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

  • Largest Contentful Paint: 41.9 s

    41.9 s

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

  • Speed Index: 23.6 s

    23.6 s

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

  • Time to Interactive: 42.4 s

    42.4 s

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

  • Total Blocking Time: 389 ms

    389 ms

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 6.0 s to 7.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix38
  • Page weight: 11.7 MB in 154 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 154 requests on a phone: images 6.2 MB (28), stylesheets 2.2 MB (46) and scripts 2.1 MB (37). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (2.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.

  • 1 image below the first screen load straight away

    1 image further down the page (537 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.3 g of CO₂ per visit

    3.32 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8689
  • 5 tap targets too small

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

  • 3 text elements with low contrast

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

  • [role="img"] and [role="image"] elements must have alternative text (3 elements)

    [role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (51 elements)

    All page content should be contained by landmarks: 51 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

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

  • 10 links without text

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

  • ARIA role should be appropriate for the element (9 elements)

    ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9290
  • No H1 headline

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

  • 130 internal links, 40 external

    The homepage links to 130 pages on onuki.tv and 40 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “明治25年創業、茨城県水戸市の小貫写真館パセオヌエボ。館内どこでも撮影できるオールロケーションスタジオ。偕楽園・千波湖などでもロケーション撮影が可能です。成人式、七五三、お宮参り、ウエディング、コマーシャルフォトなどあらゆる写真撮影を行っ…”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “茨城県水戸市の写真館 フォトスタジオ|七五三、成人式、家族写真撮影のパセオヌエボ水戸”.

  • Canonical URL set

    The canonical URL is https://www.onuki.tv/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.onuki.tv/sitemap.xml.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • llms.txt published

    The site publishes https://www.onuki.tv/llms.txt (19 KiB, 164 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://www.onuki.tv/archives/4126, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 linked pages hidden from search

    https://www.onuki.tv/archives/category/%e3%83%99%e3%83%93%e3%83%bc%e3%83%95%e3%82%a9%e3%83%88 and https://www.onuki.tv/archives/category/%e3%82%ad%e3%83%83%e3%82%ba are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages without a meta description

    https://www.onuki.tv/access-mito, https://www.onuki.tv/historia, https://www.onuki.tv/reserve, https://www.onuki.tv/cam, https://www.onuki.tv/archives/category/%e3%83%99%e3%83%93%e3%83%bc%e3%83%95%e3%82%a9%e3%83%88 and https://www.onuki.tv/archives/category/%e3%82%ad%e3%83%83%e3%82%ba have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.onuki.tv/cam has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.onuki.tv/access-mito, https://www.onuki.tv/historia, https://www.onuki.tv/reserve and https://www.onuki.tv/sekku 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.

  • 8 pages slow to respond

    https://www.onuki.tv/access-mito, https://www.onuki.tv/historia, https://www.onuki.tv/reserve, https://www.onuki.tv/cam, https://www.onuki.tv/753photo/costume and https://www.onuki.tv/archives/category/%e3%83%99%e3%83%93%e3%83%bc%e3%83%95%e3%82%a9%e3%83%88 and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 11 small tap targets

    11 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • No call to action on the first screen

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

  • No calls to action

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 80 words

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

  • No form on the homepage

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

  • No risk reducer

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

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 12 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at onuki.tv, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
SAKURA Internet Inc.

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on onuki.tv, including 21 speed issues, 1 SEO issue and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25