Website review, no card needed
public.com website review
Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 87 checks
This review found 40 issues worth fixing on public.com, 14 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 2.5 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 184 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 203 ms |
| Jun 27, 2026 | 208 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 210 ms |
| Jul 18, 2026 | 209 ms |
| Jul 25, 2026 | 206 ms |
| Aug 1, 2026 | 203 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 196 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 207 ms |
| Sep 12, 2026 | 212 ms |
| Sep 19, 2026 | 219 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 224 ms |
| Oct 10, 2026 | 225 ms |
| Oct 17, 2026 | 224 ms |
| Oct 24, 2026 | 228 ms |
| Oct 31, 2026 | 235 ms |
| Nov 7, 2026 | 226 ms |
| Nov 14, 2026 | 211 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
Speed
Reduce unused JavaScript
2.7 s · 488 KiBAbout 488 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Use efficient cache lifetimes
1.5 s · 240 KiB10 files are served with short cache lifetimes, so returning visitors download them again (240 KiB).
13,427 HTML elements
The page has 13,427 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 53
53/100Your mobile performance score is 53. 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 (Google Tag Manager, Intercom and TikTok and others), adding 1.0 MB and 625 ms of main-thread time.
Legacy JavaScript
550 ms · 75 KiBPolyfills for old browsers add 75 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.
Render-blocking requests
600 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Improve image delivery
511 KiB4 images could be 511 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 272 ms
272 msGoogle Tag Manager costs a phone 272 ms of main-thread work and 374 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 176 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.
1 checks passed
Server response: 54 ms
54 msYour server sent the HTML in 54 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 31.0 s
31.0 sYour largest element takes 31.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The investing platform for the agentic age”.
Time to Interactive: 32.1 s
32.1 sThe page becomes fully interactive after 32.1 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 228 ms
228 msReal visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 437 ms
437 msScripts block taps and scrolling for 437 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 184 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 27.6 MB in 104 requests
27.6 MBYour homepage downloads 27.6 MB in 104 requests on a phone: media 20.6 MB (4), images 3.8 MB (29) and scripts 1.6 MB (26). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.
8 images below the first screen load straight away
8 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (718 KiB) is 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.
1 image far larger than shown
10 KiB1 image is downloaded at several times the size a phone draws it, for example bg-security.webp at 1,290 px wide, shown at 390 px. Resized copies would save about 10 KiB.
About 7.8 g of CO₂ per visit
7.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.81 g of CO₂e: 937.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements must only use permitted ARIA attributes (132 elements)
Elements must only use permitted ARIA attributes: 132 elements on the page fail this check, rated serious by axe-core.
Links look like plain text
37 links inside paragraphs rely on colour alone to stand out.
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.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 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.
33 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: 33 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (196 characters)
Your meta description is 196 characters; Google truncates after about 160, so the end of your pitch is cut.
18 links with vague text
18 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
141 internal links, 35 external
The homepage links to 141 pages on public.com and 35 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Stocks Bonds Treasuries Options Crypto ETFs Bond Account6.35% yield* High-Yield Cash Account3.75% APY* Treasury Account…”.
Title: 61 characters
Your title is a healthy 61 characters: “Stocks, Bonds, Crypto & Options AI Investing App - Public.com”.
Canonical URL set
The canonical URL is https://public.com/.
Structured data in place
Structured data found: Organization.
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://public.com/sitemap_index.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,853 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://public.com/llms.txt (2 KiB, 16 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 71 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
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”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
22 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address 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.
A 15-field form
Your longest form asks for 15 fields (4 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 3,354 words of copy
The homepage carries about 3,354 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: “Sign up” and “Get started”.
33 calls to action
The homepage has 33 calls to action, for example “Sign up”, “Reserve” and “Download the app from google store”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and “10K+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 4 email links.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 3 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 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 public.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 Tag Manager
- Hosting
- CloudFront
Hiring
- Hiring
- 4 open roles
- Teams
- Business Development (1), Data (1), Finance (1), Legal (1)
- Job board
- greenhouse
- Careers page
- public.com/careers (opens in a new tab)
Company
- Employees
- 150
- Founded
- 2019
- Headquarters
- New York
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 public.com, including 20 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.