Website review, no card needed
maternitypic.com website review
Visit site (opens in a new tab)Reviewed 16 November 202642 issues · 83 checks
This review found 42 issues worth fixing on maternitypic.com, 17 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
64DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.6 s
3.3 s
3.9 s
4.6 s
5.3 s
Speed
Reduce unused JavaScript
3.1 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Render-blocking requests
1.4 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, strikinglycdn.com and Google Maps and others), adding 5.3 MB and 1.9 s of main-thread time.
strikinglycdn.com adds 806 ms
806 msstrikinglycdn.com costs a phone 806 ms of main-thread work and 3.5 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.
Reduce unused CSS
750 ms · 271 KiBAbout 271 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
hcaptcha.com adds 815 ms
815 mshcaptcha.com costs a phone 815 ms of main-thread work and 1.2 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.
Legacy JavaScript
650 ms · 217 KiBPolyfills for old browsers add 217 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 650 ms faster on a phone.
Improve image delivery
400 ms · 95 KiB4 images could be 95 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 335 ms. During a long task the page ignores taps.
Google Maps adds 174 ms
174 msGoogle Maps costs a phone 174 ms of main-thread work and 435 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 · 145 KiB7 files are served with short cache lifetimes, so returning visitors download them again (145 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Server response: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.3 s
19.3 sYour largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “豊橋 岡崎 浜松 マタニティフォト”.
Time to Interactive: 34.4 s
34.4 sThe page becomes fully interactive after 34.4 s. Good is under 3.8 s.
Speed Index: 12.6 s
12.6 sVisually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 881 ms
881 msScripts block taps and scrolling for 881 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images 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.
1 checks passed
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 195 requests
5.6 MBYour homepage downloads 5.6 MB in 195 requests on a phone: scripts 4.0 MB (130), images 591 KiB (20) and HTML 507 KiB (7). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (80 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 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 190.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (21 characters)
Your title is only 21 characters: “マタニティフォトスタジオライフインデックス”. Between 30 and 65 characters leaves room to say what you do and for whom.
10 internal links, 5 external
The homepage links to 10 pages on maternitypic.com and 5 external pages.
6 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “愛知県豊橋市にあるマタニティ専門のフォトスタジオ。 完全貸切制ですので、他の方の目を着にすることなく撮影に迎えます。 名古屋・岡崎・浜松からも多くのお客様がご来店されています。 口コミサイト「写真館部門」においてお客様満足度全国第一位しま…”.
Canonical URL set
The canonical URL is https://www.maternitypic.com/.
Structured data in place
Structured data found: 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.maternitypic.com/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://www.maternitypic.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
6 pages without a meta description
https://www.maternitypic.com/plan, https://www.maternitypic.com/price, https://www.maternitypic.com/StudioPhotoGallery, https://www.maternitypic.com/location-photo-gallery, https://www.maternitypic.com/contact and https://www.maternitypic.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.maternitypic.com/price, https://www.maternitypic.com/StudioPhotoGallery and https://www.maternitypic.com/location-photo-gallery have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://www.maternitypic.com/plan, https://www.maternitypic.com/price, https://www.maternitypic.com/StudioPhotoGallery, https://www.maternitypic.com/location-photo-gallery, https://www.maternitypic.com/contact and https://www.maternitypic.com/privacy-policy and 1 other 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.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 7 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “done function called after timeout”.
1 checks passed
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
Only about 47 words
The homepage has only about 47 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Analytics (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 1 of them by other companies (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.
20 other companies contacted
Loading the homepage contacts 20 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 maternitypic.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2017.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on maternitypic.com, including 18 speed issues, 2 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.