Website review, no card needed

allforcontent.net logo

allforcontent.net website review

Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 74 checks

This review found 35 issues worth fixing on allforcontent.net, 11 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of allforcontent.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. allforcontent.net at 0.4 s0.4 s
  2. allforcontent.net at 0.8 s0.8 s
  3. allforcontent.net at 1.1 s1.1 s
  4. allforcontent.net at 1.5 s1.5 s
  5. allforcontent.net at 1.9 s1.9 s
  6. allforcontent.net at 2.3 s2.3 s
  7. allforcontent.net at 2.7 s2.7 s
  8. allforcontent.net at 3.0 s3.0 s

Speed

9 to fix64
  • Render-blocking requests

    3.0 s

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

  • Improve image delivery

    1.3 s · 585 KiB

    7 images could be 585 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Reduce unused CSS

    900 ms · 194 KiB

    About 194 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 130 KiB

    About 130 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 76 KiB

    16 files are served with short cache lifetimes, so returning visitors download them again (76 KiB).

  • Font display

    300 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Other Google APIs/SDKs and others), adding 1.1 MB and 86 ms of main-thread time.

  • Other Google APIs/SDKs adds 0 ms

    0 ms

    Other Google APIs/SDKs costs a phone 0 ms of main-thread work and 914 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.

  • Minify CSS

    150 ms · 43 KiB

    43 KiB could be saved by minifying CSS.

  • Document request latency

    82 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

  • Minify JavaScript

    16 KiB

    16 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.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 183 ms of it running JavaScript. That is comfortably low.

  • Server response: 460 ms

    460 ms

    Your server sent the HTML in 460 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix70
  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Macbook Pro で FLUX.1[dev] を使って画像生成”.

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • 11 images without width and height

    11 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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 1 ms

    1 ms

    Scripts block the page for only 1 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix73
  • 8 images in older formats

    8 images (842 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.

  • 7 images below the first screen load straight away

    7 images further down the page (530 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    158 KiB

    1 image is downloaded at several times the size a phone draws it, for example 3b94a63e-allforcolorful-e1535815649583.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 158 KiB.

  • About 0.5 g of CO₂ per visit

    0.49 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.49 g of CO₂e: 58.9 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.7 MB in 33 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 33 requests on a phone: images 914 KiB (11), scripts 399 KiB (11) and stylesheets 225 KiB (6). That is a lean page.

Accessibility

5 to fixGoogle 8791
  • 17 text elements with low contrast

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

  • Links look like plain text

    3 links inside paragraphs rely on colour alone to stand out.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

2 checks passed
  • Every image has alt text

    All 22 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 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9276
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (17 characters)

    Your title is only 17 characters: “All for CONTENT -”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, CollectionPage, Organization and WebSite) but with 1 problem, for example “BreadcrumbList: itemListElement is an empty list”.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 125 internal links, 1 external

    The homepage links to 125 pages on allforcontent.net and 1 external page.

4 checks passed
  • One H1 headline

    Your main headline reads: “All for CONTENT”.

  • Canonical URL set

    The canonical URL is https://allforcontent.net/.

  • 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://allforcontent.net/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://allforcontent.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.

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 sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (247 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 11 pages without a meta description

    https://allforcontent.net/%e8%87%aa%e5%b7%b1%e7%b4%b9%e4%bb%8b%e3%83%bb%e8%81%b7%e5%8b%99%e7%b5%8c%e6%ad%b4, https://allforcontent.net/author/user, https://allforcontent.net/category/ai, https://allforcontent.net/category/%e3%83%8e%e3%83%bc%e3%82%b3%e3%83%bc%e3%83%89%ef%bc%8f%e3%83%ad%e3%83%bc%e3%82%b3%e3%83%bc%e3%83%89, https://allforcontent.net/category/vision and https://allforcontent.net/category/ai%e9%96%8b%e7%99%bapm%e3%81%b8%e3%81%ae%e9%81%93 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 links to non-canonical URLs

    Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://allforcontent.net/%e8%87%aa%e5%b7%b1%e7%b4%b9%e4%bb%8b%e3%83%bb%e8%81%b7%e5%8b%99%e7%b5%8c%e6%ad%b4, whose canonical is https://allforcontent.net/%E8%87%AA%E5%B7%B1%E7%B4%B9%E4%BB%8B%E3%83%BB%E8%81%B7%E5%8B%99%E7%B5%8C%E6%AD%B4. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages with very little text

    https://allforcontent.net/%e8%87%aa%e5%b7%b1%e7%b4%b9%e4%bb%8b%e3%83%bb%e8%81%b7%e5%8b%99%e7%b5%8c%e6%ad%b4 and https://allforcontent.net/category/%e3%83%8e%e3%83%bc%e3%82%b3%e3%83%bc%e3%83%89%ef%bc%8f%e3%83%ad%e3%83%bc%e3%82%b3%e3%83%bc%e3%83%89 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://allforcontent.net/singapore-fintech-festival-2024-%e3%81%8b%e3%82%89%e8%a6%8b%e3%82%8b-fintech%e6%9c%80%e6%96%b0%e3%83%88%e3%83%ac%e3%83%b3%e3%83%89-2024-11-12, https://allforcontent.net/category/vision, https://allforcontent.net/mutable-ai-%e3%82%b3%e3%83%bc%e3%83%89%e3%83%aa%e3%83%bc%e3%83%87%e3%82%a3%e3%83%b3%e3%82%b0%e3%82%92%e5%8a%b9%e7%8e%87%e5%8c%96%e3%81%99%e3%82%8b%e7%94%9f%e6%88%90ai%e6%b4%bb%e7%94%a8-2024-10-01, https://allforcontent.net/category/ai%e9%96%8b%e7%99%bapm%e3%81%b8%e3%81%ae%e9%81%93, https://allforcontent.net/dify-%e7%8f%be%e5%a0%b4%e3%81%8c%e4%bd%9c%e3%82%8c%e3%82%8b%e3%80%81dx%e7%94%9f%e6%88%90ai%e3%83%84%e3%83%bc%e3%83%ab-2024-09-26 and https://allforcontent.net/mutable-ai%e3%81%a8adrenaline%e3%81%a7copilot-chat%e3%81%ae%e9%99%90%e7%95%8c%e3%82%92%e8%b6%85%e3%81%88%e3%82%8b-2024-07-16 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 26 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.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 17 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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 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 186 words

    The homepage has only about 186 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.

2 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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 allforcontent.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
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 35 issues on allforcontent.net, including 14 speed issues, 4 SEO issues and 5 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