Website review, no card needed

partnerpage.io logo

partnerpage.io website review

Visit site (opens in a new tab)Reviewed 10 November 202625 issues · 70 checks

This review found 25 issues worth fixing on partnerpage.io, 3 of them high impact, across 70 checks. The most urgent: page weight: 5.2 MB in 70 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 partnerpage.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. partnerpage.io at 0.5 s0.5 s
  2. partnerpage.io at 1.0 s1.0 s
  3. partnerpage.io at 1.5 s1.5 s
  4. partnerpage.io at 2.0 s2.0 s
  5. partnerpage.io at 2.4 s2.4 s
  6. partnerpage.io at 2.9 s2.9 s
  7. partnerpage.io at 3.4 s3.4 s
  8. partnerpage.io at 3.9 s3.9 s

Speed

4 to fix85
  • 5 third-party services on the page

    5 third-party services load with your homepage (Framer CDN, Google Tag Manager and Customer.io and others), adding 4.7 MB and 871 ms of main-thread time.

  • Framer CDN adds 738 ms

    738 ms

    Framer CDN costs a phone 738 ms of main-thread work and 4.5 MB 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.

  • Mobile performance score: 85

    85/100

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

  • Document request latency

    313 KiB

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

  • Reduce unused JavaScript

    171 KiB

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

  • Reduce unused CSS

    128 KiB

    About 128 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    85 KiB

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

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    19 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 103 ms

    103 ms

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

Core Web Vitals

3 to fix89
  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Go live in under a week with a Partner Directory fueled by …”.

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

3 checks passed
  • Speed Index: 3.4 s

    3.4 s

    Visually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 78 ms

    78 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix70
  • Page weight: 5.2 MB in 70 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 70 requests on a phone: media 3.9 MB (1), scripts 555 KiB (38) and HTML 471 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.5 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

3 to fixGoogle 9095
  • All page content should be contained by landmarks (27 elements)

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

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 96 images in the HTML carry an alt attribute.

  • 28 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 4 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 6176
  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Canonical points to another host

    Your canonical URL points to centered-knowledge-608284.framer.app, not partnerpage.io, so Google may credit that host instead.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 5 links with vague text

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

  • 63 internal links, 76 external

    The homepage links to 63 pages on partnerpage.io and 76 external pages.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “PartnerPage is a platform to promote and discover partners, simplifying and automating the process of building and main…”.

  • One H1 headline

    Your main headline reads: “Launch your partner directory in days”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “PartnerPage - Partner Directory Software”.

  • 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://centered-knowledge-608284.framer.app/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.partnerpage.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 (1,355 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 14 linked pages hidden from search

    https://www.partnerpage.io/enterprise, https://www.partnerpage.io/customers, https://www.partnerpage.io/pricing, https://www.partnerpage.io/customers/apollo-io-launched-a-partner-directory-in-2-weeks-and-won-more-deals, https://www.partnerpage.io/service-partners-directory and https://www.partnerpage.io/tech-partner-directory and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 14 pages share a title

    /, https://www.partnerpage.io/enterprise, https://www.partnerpage.io/customers, https://www.partnerpage.io/pricing, https://www.partnerpage.io/service-partners-directory and https://www.partnerpage.io/tech-partner-directory and 8 others all use the title “PartnerPage - Partner Directory Software”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    https://www.partnerpage.io/enterprise, https://www.partnerpage.io/customers, https://www.partnerpage.io/pricing, https://www.partnerpage.io/service-partners-directory, https://www.partnerpage.io/tech-partner-directory and https://www.partnerpage.io/partner-teams and 7 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.partnerpage.io/customers/apollo-io-launched-a-partner-directory-in-2-weeks-and-won-more-deals has no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

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

4 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

    3 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 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 8 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 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 609 words of copy

    The homepage carries about 609 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start for free” and “Get a demo”.

  • 28 calls to action

    The homepage has 28 calls to action, for example “Pricing”, “Sign up” and “Start for free”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

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

  • 8 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Framer
Analytics
Google Analytics
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on partnerpage.io, including 7 speed issues, 4 SEO issues and 2 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