Website review, no card needed

conceiveplus.it logo

conceiveplus.it website review

Visit site (opens in a new tab)Reviewed 17 November 202632 issues · 82 checks

This review found 32 issues worth fixing on conceiveplus.it, 9 of them high impact, across 82 checks. The most urgent: page weight: 10.6 MB in 180 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

Real-visitor load time (LCP)75th percentile, phones
3.0 s1.6 sMay 30Nov 142.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.3 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.7 s
Oct 24, 20262.8 s
Oct 31, 20262.8 s
Nov 7, 20262.8 s
Nov 14, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
191 ms140 msMay 30Nov 14170 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026161 ms
Jun 6, 2026169 ms
Jun 13, 2026156 ms
Jun 20, 2026153 ms
Jun 27, 2026149 ms
Jul 4, 2026149 ms
Jul 11, 2026146 ms
Jul 18, 2026146 ms
Jul 25, 2026167 ms
Aug 1, 2026163 ms
Aug 8, 2026159 ms
Aug 15, 2026166 ms
Aug 22, 2026148 ms
Aug 29, 2026158 ms
Sep 5, 2026171 ms
Sep 12, 2026156 ms
Sep 19, 2026173 ms
Sep 26, 2026173 ms
Oct 3, 2026175 ms
Oct 10, 2026184 ms
Oct 17, 2026180 ms
Oct 24, 2026182 ms
Oct 31, 2026185 ms
Nov 7, 2026177 ms
Nov 14, 2026170 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of conceiveplus.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. conceiveplus.it at 0.6 s0.6 s
  2. conceiveplus.it at 1.3 s1.3 s
  3. conceiveplus.it at 1.9 s1.9 s
  4. conceiveplus.it at 2.6 s2.6 s
  5. conceiveplus.it at 3.2 s3.2 s
  6. conceiveplus.it at 3.9 s3.9 s
  7. conceiveplus.it at 4.5 s4.5 s
  8. conceiveplus.it at 5.2 s5.2 s

Speed

8 to fix71
  • Main-thread work: 5.8 s

    A phone's processor spends 5.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 5,374 HTML elements

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

  • Mobile performance score: 71

    71/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (negate.io, Shopify and Google Tag Manager and others), adding 792 KiB and 764 ms of main-thread time.

  • Render-blocking requests

    650 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Reduce unused JavaScript

    270 ms · 297 KiB

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

  • negate.io adds 281 ms

    281 ms

    negate.io costs a phone 281 ms of main-thread work and 40 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.

  • Shopify adds 218 ms

    218 ms

    Shopify costs a phone 218 ms of main-thread work and 312 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.

  • Reduce unused CSS

    270 ms · 24 KiB

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

  • Use efficient cache lifetimes

    200 ms · 85 KiB

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

  • 9 long tasks on the main thread

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

  • Improve image delivery

    50 KiB

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

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

1 checks passed
  • Server response: 101 ms

    101 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 13.9 s

    13.9 s

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Largest content (LCP) got 42% slower for real visitors

    +42%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 4.6 s

    4.6 s

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

  • Total Blocking Time: 381 ms

    381 ms

    Scripts block taps and scrolling for 381 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 161 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 162 ms

    162 ms

    Real visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 761 ms

    761 ms

    Real visitors wait 761 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 10.6 MB in 180 requests

    10.6 MB

    Your homepage downloads 10.6 MB in 180 requests on a phone: media 8.1 MB (2), scripts 1.0 MB (52) and other files 659 KiB (72). Under 2 MB keeps phones on slow connections fast.

  • About 3.0 g of CO₂ per visit

    2.99 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8494
  • 2 text elements with low contrast

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

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 9 links without text

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • Title is long (102 characters)

    Your title is 102 characters, so Google will cut it off around 60: “Conceive Plus® | Il marchio n.1 di integratori per la fertilità e lubrificanti – Conceive…”.

  • Meta description is long (263 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 102 internal links, 20 external

    The homepage links to 102 pages on conceiveplus.it and 20 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://conceiveplus.it/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, Store 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://conceiveplus.it/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://conceiveplus.it/llms.txt (23 KiB, 140 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://conceiveplus.it/pages/faq declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://conceiveplus.it/pages/faq all use the title “Conceive Plus® | Il marchio n.1 di integratori per la fertilità e lub…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://conceiveplus.it/blogs/blog has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://conceiveplus.it/tools/tracking has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=26073823&Ver=2&mid=47da088f-7805-4264-a510-0c2aebfe58eb&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Conceive%20Plus%C2%AE%20%7C%20Il%20marchio%20n.1%20di%2.

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

2 checks passed
  • Tap targets are thumb-sized

    39 of 42 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • 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: 11 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,109 words of copy

    The homepage carries about 1,109 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “TRACK YOUR ORDER”, “CONTACT US” and “Türkiye / Turkey TRY”.

  • 7 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Ads (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.

  • 5 cookies set on arrival

    5

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 conceiveplus.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Okendo · Hreflang Manager · Tinyseo Ai Seo Speed · Seal Subscriptions · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Popsixle · Uppromote Affiliate · Gdpr Cookie Consent · Orbe Geolocation · Section Factory · Affliate By Secomapp · amazonaws.com · cloudfront.net

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on conceiveplus.it, including 13 speed issues, 3 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

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