Website review, no card needed
natsulog.com website review
Visit site (opens in a new tab)Reviewed 17 November 202625 issues · 67 checks
This review found 25 issues worth fixing on natsulog.com, 7 of them high impact, across 67 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
2.5 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused CSS
1.4 s · 320 KiBAbout 320 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
750 ms · 277 KiB6 images could be 277 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Google Fonts adds 7 ms
7 msGoogle Fonts costs a phone 7 ms of main-thread work and 690 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.
Use efficient cache lifetimes
150 ms · 91 KiB19 files are served with short cache lifetimes, so returning visitors download them again (91 KiB).
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 690 KiB and 7 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.
Minify CSS
30 KiB30 KiB could be saved by minifying CSS.
Reduce unused JavaScript
20 KiBAbout 20 KiB of JavaScript is downloaded but never used on this page.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 27 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NATSULOG|なつログ”.
Time to Interactive: 8.6 s
8.6 sThe page becomes fully interactive after 8.6 s. Good is under 3.8 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
5 images in older formats
5 images (409 KiB) 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.
About 0.5 g of CO₂ per visit
0.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 54.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.6 MB in 56 requests
1.6 MBYour homepage downloads 1.6 MB in 56 requests on a phone: images 699 KiB (8), fonts 571 KiB (37) and stylesheets 285 KiB (6). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (26 characters)
Your title is only 26 characters: “NATSULOG|なつログ | なつと、家族の暮らし”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (10 characters)
Your meta description is only 10 characters: “なつと、家族の暮らし”. 70 to 160 characters is enough to sell the click.
One H1 headline
Your <h1> is empty.
12 internal links, 3 external
The homepage links to 12 pages on natsulog.com and 3 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://natsulog.com/.
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://natsulog.com/wp-sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://natsulog.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.
1 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.
Other pages
1 linked page hidden from search
https://natsulog.com/author/natsulog0527 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://natsulog.com/author/natsulog0527 has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages with very little text
https://natsulog.com/%e3%80%90%e5%ae%bf%e6%b3%8a%e3%83%ac%e3%83%9d%e3%80%91omo%ef%bc%97%e5%a4%a7%e9%98%aa%e3%81%ab%e6%b3%8a%e3%81%be%e3%81%a3%e3%81%a6%e3%81%bf%e3%81%9f%ef%bc%81%e6%84%9b%e7%8a%ac%e9%80%a3%e3%82%8c, https://natsulog.com/%e3%80%90%e3%83%b4%e3%82%a3%e3%82%bd%e3%83%b3%e7%8a%ac%e9%80%a3%e3%82%8c%e8%bb%8a%e4%b8%ad%e6%b3%8a%e3%80%91%e3%83%86%e3%82%b9%e3%83%a9model-y%e3%81%a7rv%e3%83%91%e3%83%bc%e3%82%af%e3%81%ab%e5%ae%bf, https://natsulog.com/%e3%80%90%e5%ae%bf%e6%b3%8a%e3%83%ac%e3%83%9d%e3%80%91%e9%87%8e%e5%af%9b%e4%bc%8a%e5%8b%a2%e9%b3%a5%e7%be%bd%e3%81%ab%e6%9f%b4%e7%8a%ac%e3%81%a8%e6%b3%8a%e3%81%be%e3%81%a3%e3%81%a6%e3%81%bf%e3%81%9f, https://natsulog.com/%e6%9f%b4%e7%8a%ac%e3%81%ae%e5%bc%95%e3%81%a3%e5%bc%b5%e3%82%8a%e7%99%96%e3%81%ab%e6%82%a9%e3%82%93%e3%81%a7%e3%81%be%e3%81%99%ef%bc%81%ef%bd%9c%e3%81%aa%e3%81%a4%e3%81%a8%e5%a7%8b%e3%82%81%e3%81%9f, https://natsulog.com/%e6%9f%b4%e7%8a%ac%e3%80%8c%e3%81%aa%e3%81%a4%e3%80%8d%f0%9f%90%95%e3%81%ae%e3%83%97%e3%83%ad%e3%83%95%e3%82%a3%e3%83%bc%e3%83%ab%ef%bd%9c%e6%88%91%e3%81%8c%e5%ae%b6%e3%81%ae%e6%84%9b%e7%8a%ac and https://natsulog.com/category/%e3%81%8a%e5%87%ba%e3%81%8b%e3%81%91 and 2 others 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.
2 pages slow to respond
https://natsulog.com/category/%e3%81%97%e3%81%a4%e3%81%91 and https://natsulog.com/category/uncategorized took over 3 s to send their HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
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 an H1
Each page we checked has a main headline.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
10 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 natsulog.com, 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
- Hosting
- Xserver Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on natsulog.com, including 10 speed issues, 4 SEO issues and 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.