partiful.com website review

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

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

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

8 third-party services load with your homepage (framerusercontent.com, Google Tag Manager and Amplitude Mobile Analytics and others), adding 6.5 MB and 1.1 s of main-thread time.

framerusercontent.com costs a phone 589 ms of main-thread work and 5.9 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.

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

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

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

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

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

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

Desktop scores 60 but mobile only 32. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 22.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Abstract gradient with soft pink and blue hues blending tog…”.

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

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

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

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

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

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

Your homepage downloads 6.6 MB in 171 requests on a phone: images 5.1 MB (95), scripts 1,016 KiB (50) and fonts 390 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example qjyX2nMXr6NpnAEMTZIq3f19g2Y.png at 472 px wide, shown at 24 px. Resized copies would save about 52 KiB.

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

17 elements hidden from screen readers can still receive keyboard focus.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

There are 16 <h1> headlines (“Parties are back”, “Fun, modern invites in 1-click” and “Fun, modern invites in 1-click”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://partiful.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 102 pages on partiful.com and 43 external pages.

Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

/housewarming-invitations and /create are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and /download all use the title “Partiful - Free Online Invitations with RSVP Tracking”. Search engines can't tell which page to show for a search, so each competes with the others.

/blog/post/timothee-chalamet-lookalike, /blog/post/griffin-maxwell-brooks-to-be-a-snob-is-to-be-a-good-dj, /blog/post/why-we-need-fuckbois and /blog use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /discover, whose canonical is /explore. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/discover, /create and /blog have no <h1> headline, so visitors and search engines get no clear main topic.

/download has 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.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 9 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 588 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Transcend) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies (measured from a US location before any click).

Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.