Website review, no card needed

akeena.net logo

akeena.net website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 76 checks

This review found 34 issues worth fixing on akeena.net, 10 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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 akeena.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akeena.net at 0.9 s0.9 s
  2. akeena.net at 1.9 s1.9 s
  3. akeena.net at 2.8 s2.8 s
  4. akeena.net at 3.7 s3.7 s
  5. akeena.net at 4.7 s4.7 s
  6. akeena.net at 5.6 s5.6 s
  7. akeena.net at 6.5 s6.5 s
  8. akeena.net at 7.5 s7.5 s

Speed

5 to fix62
  • Use efficient cache lifetimes

    3.0 s · 1.1 MB

    77 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Render-blocking requests

    2.7 s

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

  • Mobile performance score: 62

    62/100

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

  • Reduce unused CSS

    600 ms · 130 KiB

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

  • Google Fonts adds 5 ms

    5 ms

    Google Fonts costs a phone 5 ms of main-thread work and 332 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.

  • Font display

    100 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Fonts, imagedelivery.net and quoracdn.net and others), adding 775 KiB and 5 ms of main-thread time.

  • Reduce unused JavaScript

    37 KiB

    About 37 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    16 KiB

    2 images could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    15 KiB

    15 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 97 ms

    97 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Live Games The best place to start your journey is casino g…”. Most of its time is resource load delay (5.0 s).

  • Speed Index: 9.1 s

    9.1 s

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

  • Time to Interactive: 8.3 s

    8.3 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 20 images without width and height

    20 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.041

    0.041

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

6 to fix43
  • 1 image over 500 KB

    casino-games.jpg weighs 598 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.6 MB in 102 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 102 requests on a phone: images 1.7 MB (27), fonts 411 KiB (9) and scripts 225 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.1 MB) 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.

  • 9 images below the first screen load straight away

    9 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    akeena-logo.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images far larger than shown

    204 KiB

    4 images are downloaded at several times the size a phone draws them, for example casino-games.jpg at 1,200 px wide, shown at 370 px. Resized copies would save about 204 KiB.

  • About 0.7 g of CO₂ per visit

    0.75 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 89.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8692
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 51 text elements with low contrast

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

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 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.

  • 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 29 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • Title is short (13 characters)

    Your title is only 13 characters: “Home - Akeena”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (296 characters)

    Your meta description is 296 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 43 internal links, 28 external

    The homepage links to 43 pages on akeena.net and 28 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Akeena”.

  • Canonical URL set

    The canonical URL is https://www.akeena.net/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and 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.akeena.net/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.akeena.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 description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.akeena.net/terms-and-conditions 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://www.akeena.net/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages slow to respond

    https://www.akeena.net/privacy-policy, https://www.akeena.net/trusted-online-casino-malaysia-guide, https://www.akeena.net/winbet2u-online-casino-malaysia-review, https://www.akeena.net/jdl688-review, https://www.akeena.net/yes2win-online-casino-review and https://www.akeena.net/terms-and-conditions and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage 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

3 to fixGoogle 9271
  • 2 broken images

    2 images failed to load on a phone, for example https://media.licdn.com/dms/image/D4D12AQHqFznQmlND0A/article-cover_image-shrink_720_1280/0/1689518415792?e=2147483647&v=beta&t=h51gMOfCMALMYlKMl-UMGWxKGhUxTiLrRdjn_rKCsgA.

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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: a star rating. 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.

  • About 10,601 words of copy

    The homepage carries about 10,601 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 akeena.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
Hosting
CloudFront

Company

Headquarters
Fairfield

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on akeena.net, including 10 speed issues, 3 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

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