Website review, no card needed
medallion.co website review
Visit site (opens in a new tab)Reviewed 5 November 202635 issues · 86 checks
This review found 35 issues worth fixing on medallion.co, 12 of them high impact, across 86 checks. The most urgent: page weight: 24.9 MB in 172 requests. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 1, 2026 | 270 ms |
| Aug 8, 2026 | 251 ms |
| Aug 15, 2026 | 247 ms |
| Aug 22, 2026 | 252 ms |
| Aug 29, 2026 | 244 ms |
| Sep 5, 2026 | 245 ms |
| Sep 12, 2026 | 249 ms |
| Sep 19, 2026 | 238 ms |
| Sep 26, 2026 | 246 ms |
| Oct 3, 2026 | 256 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 258 ms |
| Oct 24, 2026 | 245 ms |
| Oct 31, 2026 | 267 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Render-blocking requests
1.3 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
350 ms · 9.6 MB101 files are served with short cache lifetimes, so returning visitors download them again (9.6 MB).
Improve image delivery
8.3 MB11 images could be 8.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, posthog.com and Hotjar and others), adding 1.7 MB and 1.4 s of main-thread time.
Mobile performance score: 82
82/100Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
709 KiBAbout 709 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 419 ms
419 msGoogle Tag Manager costs a phone 419 ms of main-thread work and 708 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.
posthog.com adds 334 ms
334 msposthog.com costs a phone 334 ms of main-thread work and 253 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.
Hubspot adds 193 ms
193 msHubspot costs a phone 193 ms of main-thread work and 518 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.
Reduce unused CSS
41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
18 KiB18 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: 4 ms
4 msYour server sent the HTML in 4 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.
Time to Interactive: 19.3 s
19.3 sThe page becomes fully interactive after 19.3 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 300 ms
300 msReal visitors wait 300 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 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.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 346 ms
346 msScripts block taps and scrolling for 346 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 270 ms to 267 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.056
0.056The layout barely moves while loading (CLS 0.056, good is under 0.1).
Largest Contentful Paint: 1.8 s
1.8 sYour largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Better outcomes for credentialing. Faster paths to billable…”.
Images and page weight
Page weight: 24.9 MB in 172 requests
24.9 MBYour homepage downloads 24.9 MB in 172 requests on a phone: media 11.7 MB (1), images 11.2 MB (83) and scripts 1.7 MB (39). Under 2 MB keeps phones on slow connections fast.
8 images over 500 KB
8 images weigh 8.3 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
3.0 MB11 images are downloaded at several times the size a phone draws them, for example aw-dc-photo.png at 1,204 px wide, shown at 324 px. Resized copies would save about 3.0 MB.
11 images in older formats
11 images (8.5 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.
About 7.1 g of CO₂ per visit
7.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.06 g of CO₂e: 847.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
28 tap targets too small
28 tap targets are too small or too close together to hit reliably with a finger.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 130 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. 4 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 (198 characters)
Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.
88 internal links, 13 external
The homepage links to 88 pages on medallion.co and 13 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Better outcomes for credentialing.Faster paths to billable providers.”.
Title: 59 characters
Your title is a healthy 59 characters: “Automated provider credentialing and enrollment | Medallion”.
Canonical URL set
The canonical URL is https://www.medallion.co/.
Structured data in place
Structured data found: FAQPage, Organization 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://www.medallion.co/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,200 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.medallion.co/llms.txt (3 KiB, 23 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 43 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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
18 of 20 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 1,247 words of copy
The homepage carries about 1,247 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: “GET IN TOUCH”.
15 calls to action
The homepage has 15 calls to action, for example “Learn More ↗”, “Pricing” and “Get in touch”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks, 22 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 medallion.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Astro
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare Pages
Company
- Headquarters
- San Francisco
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on medallion.co, including 20 speed issues, 1 SEO issue and 1 conversion gap. 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.