Website review, no card needed
fusioncook.net website review
Visit site (opens in a new tab)Reviewed 20 November 202624 issues · 56 checks
This review found 24 issues worth fixing on fusioncook.net, 8 of them high impact, across 56 checks. The most urgent: 5 tap targets too small. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
One score from every part of this review. How it works
Speed
Google's speed test didn't respond
Google's speed test didn't respond for this site, so speed and Core Web Vitals are not measured here. Your full playbook measures them.
Core Web Vitals
Not measured in this review.
Images and page weight
1 image over 500 KB
Fusioncook.NetLogo.png weighs 524 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
500 KiB1 image is downloaded at several times the size a phone draws it, for example Fusioncook.NetLogo.png at 600 px wide, shown at 43 px. Resized copies would save about 500 KiB.
2 images in older formats
2 images (579 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.
1 image below the first screen load straight away
1 image further down the page (55 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.41 g of CO₂e: 49.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.5 MB
1.5 MBYour homepage downloads 1.5 MB on a phone, 883 KiB of it images (59%). That is a lean page.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don'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.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
38 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: 38 passed and 8 failed. 2 mores 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 structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Trending Recipes”, “Latest Upload from Fusion Cooking!” and “Testimonials”). One clear main headline is easier for people and search engines.
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.
No XML sitemap
No XML sitemap at https://fusioncook.net/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
23 internal links, 14 external
The homepage links to 23 pages on fusioncook.net and 14 external pages.
3 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Fusion Cooking | Weight Loss Recipes | Baby Foods | Blog”.
Canonical URL set
The canonical URL is https://fusioncook.net/.
robots.txt in place
robots.txt is in place.
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://fusioncook.net/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (437 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://fusioncook.net/5-ways-to-preserve-nutrition-in-food-you-eat and https://fusioncook.net/you-are-what-you-eat have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages slow to respond
https://fusioncook.net/5-ways-to-preserve-nutrition-in-food-you-eat and https://fusioncook.net/you-are-what-you-eat took over 3 s to send their HTML from our server.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
2 pages of 10 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example http://fusioncook.net/wp-content/uploads/WeightLossMealPlan-610x343.jpg.
9 small tap targets
9 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://fusioncook.net/' was loaded over HTTPS, but requested an insecure image 'http://fus…”.
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.
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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.
About 423 words of copy
The homepage carries about 423 words of visible text.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Shop”, “Contact” and “Subscribe to my channel”.
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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
9 other companies contacted
Loading the homepage contacts 9 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 fusioncook.net, 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
- Hosting
- InMotion Hosting, Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on fusioncook.net, including 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.