Website review, no card needed
mocca-bitcoin.com website review
Visit site (opens in a new tab)Reviewed 13 November 202633 issues · 72 checks
This review found 33 issues worth fixing on mocca-bitcoin.com, 8 of them high impact, across 72 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
73CClosest 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.4 s
0.8 s
1.3 s
1.7 s
2.1 s
2.5 s
3.0 s
3.4 s
Speed
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
900 ms · 174 KiB2 images could be 174 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 130 KiBAbout 130 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Use efficient cache lifetimes
300 ms · 53 KiB7 files are served with short cache lifetimes, so returning visitors download them again (53 KiB).
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Analytics), adding 222 KiB and 188 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 149 ms. During a long task the page ignores taps.
Reduce unused CSS
89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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 CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 219 ms of it running JavaScript. That is comfortably low.
Server response: 161 ms
161 msYour server sent the HTML in 161 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ur65”.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.0 s
6.0 sThe page becomes fully interactive after 6.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.149
0.149The layout shifts by 0.149 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 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.
1 checks passed
Total Blocking Time: 99 ms
99 msScripts block the page for only 99 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
10 KiB1 image is downloaded at several times the size a phone draws it, for example ccc862e98db635f8f8f7b47113204b69.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 10 KiB.
2 images in older formats
2 images (263 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.2 g of CO₂ per visit
0.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 24.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 749 KiB in 15 requests
749 KiBYour homepage downloads 749 KiB in 15 requests on a phone: scripts 304 KiB (6), images 263 KiB (2) and HTML 86 KiB (1). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Form elements must have labels (1 element)
Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
81 internal links, 1 external
The homepage links to 81 pages on mocca-bitcoin.com and 1 external page.
4 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “ドローンやそれ以外の事も気ままに書くブログ - 晴れときどき仮想通貨”.
Structured data in place
Structured data found: ImageObject.
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://mocca-bitcoin.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://mocca-bitcoin.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://mocca-bitcoin.com/tag/%e3%83%9e%e3%82%a4%e3%82%af%e3%83%ad%e3%83%89%e3%83%ad%e3%83%bc%e3%83%b3%e3%81%ae%e5%a7%8b%e3%82%81%e6%96%b9 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 pages without a meta description
https://mocca-bitcoin.com/category/drone, https://mocca-bitcoin.com/tag/%e3%83%9e%e3%82%a4%e3%82%af%e3%83%ad%e3%83%89%e3%83%ad%e3%83%bc%e3%83%b3%e3%81%ae%e5%a7%8b%e3%82%81%e6%96%b9, https://mocca-bitcoin.com/about, https://mocca-bitcoin.com/contact, https://mocca-bitcoin.com/blog-2 and https://mocca-bitcoin.com/category/drone/column-drone and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages with very little text
https://mocca-bitcoin.com/about, https://mocca-bitcoin.com/contact, https://mocca-bitcoin.com/blog-2 and https://mocca-bitcoin.com/category/drone/column-drone 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.
3 pages slow to respond
https://mocca-bitcoin.com/tag/%e3%83%9e%e3%82%a4%e3%82%af%e3%83%ad%e3%83%89%e3%83%ad%e3%83%bc%e3%83%b3%e3%81%ae%e5%a7%8b%e3%82%81%e6%96%b9, https://mocca-bitcoin.com/about and https://mocca-bitcoin.com/contact took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 55 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 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 15 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 21 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 “wp is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 135 words
The homepage has only about 135 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
1 call to action
The homepage has 1 call to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
5 other companies contacted
Loading the homepage contacts 5 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 mocca-bitcoin.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
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- 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 33 issues on mocca-bitcoin.com, including 12 speed issues, 5 SEO issues and 3 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.