Website review, no card needed

apricityfertility.com logo

apricityfertility.com website review

Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 81 checks

This review found 40 issues worth fixing on apricityfertility.com, 20 of them high impact, across 81 checks. The most urgent: improve image delivery. 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 apricityfertility.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apricityfertility.com at 0.8 s0.8 s
  2. apricityfertility.com at 1.6 s1.6 s
  3. apricityfertility.com at 2.4 s2.4 s
  4. apricityfertility.com at 3.2 s3.2 s
  5. apricityfertility.com at 4.0 s4.0 s
  6. apricityfertility.com at 4.8 s4.8 s
  7. apricityfertility.com at 5.6 s5.6 s
  8. apricityfertility.com at 6.4 s6.4 s

Speed

9 to fix37
  • Improve image delivery

    5.3 s · 5.9 MB

    85 images could be 5.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.

  • Use efficient cache lifetimes

    4.0 s · 3.6 MB

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

  • Render-blocking requests

    2.8 s

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

  • Reduce unused JavaScript

    2.3 s · 374 KiB

    About 374 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,181 HTML elements

    The page has 3,181 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, byted-static.com and Unpkg and others), adding 1.7 MB and 412 ms of main-thread time.

  • Google Tag Manager adds 348 ms

    348 ms

    Google Tag Manager costs a phone 348 ms of main-thread work and 533 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.

  • lightshot.app adds 0 ms

    0 ms

    lightshot.app costs a phone 0 ms of main-thread work and 951 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.

  • Legacy JavaScript

    150 ms · 36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 365 ms

    365 ms

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

Core Web Vitals

6 to fix33
  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Giải bóng đá Serie A Italia ĐANG TRỰC TIẾP 11:45 - 24/10 S.…”.

  • Time to Interactive: 19.3 s

    19.3 s

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

  • Cumulative Layout Shift: 0.743

    0.743

    The layout shifts by 0.743 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • 25 images without width and height

    25 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
  • Total Blocking Time: 151 ms

    151 ms

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

Images and page weight

5 to fix18
  • Page weight: 9.4 MB in 233 requests

    9.4 MB

    Your homepage downloads 9.4 MB in 233 requests on a phone: images 8.3 MB (201), scripts 821 KiB (16) and fonts 143 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 18 images far larger than shown

    2.5 MB

    18 images are downloaded at several times the size a phone draws them, for example 1791198524404_9724vy_signal-2026-10-05-18-07-28-266_002.gif at 1,200 px wide, shown at 390 px. Resized copies would save about 2.5 MB.

  • 1 image over 500 KB

    1791198524404_9724vy_signal-2026-10-05-18-07-28-266_002.gif weighs 588 KiB. On a phone connection a single image that size takes seconds.

  • 23 images in older formats

    23 images (6.3 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.

  • 5 images below the first screen load straight away

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

  • About 2.7 g of CO₂ per visit

    2.66 g

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

Accessibility

5 to fixGoogle 8692
  • 49 tap targets too small

    49 tap targets are too small or too close together to hit reliably with a finger.

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

  • 82 links without text

    82 visible links have no text or label, so screen readers cannot say where they go.

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

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 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 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No XML sitemap

    No XML sitemap at https://www.aliv.io/sitemap.xml, so Google discovers your pages only by following links.

  • 23 internal links, 4 external

    The homepage links to 23 pages on apricityfertility.com and 4 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “CakhiaTV trực tiếp bóng đá tất cả giải đấu Full HD, miễn phí, không lag. Cà Khịa TV nhật lịch thi đấu, kết quả, link xe…”.

  • One H1 headline

    Your main headline reads: “CakhiaTV | Trực Tiếp Bóng Đá HD - Link Cà Khịa TV #1 Hôm Nay”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “CakhiaTV | Trực Tiếp Bóng Đá HD - Link Cà Khịa TV #1 Hôm Nay”.

  • Canonical URL set

    The canonical URL is https://www.aliv.io/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

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

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.aliv.io/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 (5,897 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.aliv.io/nhan-dinh, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a meta description

    https://www.aliv.io/author/hoangvanlong has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://www.aliv.io/ban-quyen, https://www.aliv.io/mien-tru-trach-nhiem and https://www.aliv.io/author/hoangvanlong took over 3 s to send their HTML from our server.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • 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 12 pages that loaded have a <title>.

Best practices

4 to fixGoogle 9270
  • 7 broken images

    7 images failed to load on a phone, for example https://cdn.aliv.io/wp-content/wp-content/uploads/2025/06/icon-facebook.webp.

  • 15 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. 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 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.

  • About 7,672 words of copy

    The homepage carries about 7,672 words of visible text.

1 checks passed
  • 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 apricityfertility.com, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on apricityfertility.com, including 15 speed issues, 1 SEO issue and 6 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