Website review, no card needed
parchment.com website review
Visit site (opens in a new tab)Reviewed 11 October 202633 issues · 104 checks
This review found 33 issues worth fixing on parchment.com, 13 of them high impact, across 104 checks. The most urgent: render-blocking 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
80BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 3.4 s |
| Apr 25, 2026 | 3.3 s |
| May 2, 2026 | 3.3 s |
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 172 ms |
| Apr 25, 2026 | 186 ms |
| May 2, 2026 | 185 ms |
| May 9, 2026 | 185 ms |
| May 16, 2026 | 186 ms |
| May 23, 2026 | 186 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 186 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 188 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 186 ms |
| Aug 1, 2026 | 185 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 182 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 178 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
parchment.com does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
3.5 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Reduce unused JavaScript
1.6 s · 316 KiBAbout 316 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 49
49/100Your mobile performance score is 49 (desktop: 73). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Google Tag Manager adds 425 ms
425 msGoogle Tag Manager costs a phone 425 ms of main-thread work and 535 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.
Minify JavaScript
300 ms · 29 KiB29 KiB could be saved by minifying JavaScript.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
1,926 HTML elements
The page has 1,926 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and ipstack.com and others), adding 541 KiB and 425 ms of main-thread time.
Improve image delivery
94 KiB3 images could be 94 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 893 ms of it running JavaScript. That is comfortably low.
Server response: 40 ms
40 msYour server sent the HTML in 40 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.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “pfa image”.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 513 ms
513 msScripts block taps and scrolling for 513 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 172 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 72 requests
1.6 MBYour homepage downloads 1.6 MB in 72 requests on a phone: scripts 825 KiB (18), fonts 384 KiB (3) and images 304 KiB (28). That is a lean page.
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
Required ARIA attributes must be provided (5 elements)
Required ARIA attributes must be provided: 5 elements on the page fail this check, rated critical by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
ARIA role should be appropriate for the element (7 elements)
ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 100 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
239 internal links, 15 external
The homepage links to 239 pages on parchment.com and 15 external pages.
7 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Turn more credentials into more opportunities with Parchment's leading credential network and send and receive platform…”.
One H1 headline
Your main headline reads: “Turn every credential into an opportunity”.
Title: 60 characters
Your title is a healthy 60 characters: “Secure & Reliable End-To-End Credentials Support | Parchment”.
Canonical URL set
The canonical URL is https://www.parchment.com/.
Structured data in place
Structured data found: Article, BlogPosting, BreadcrumbList, Organization and Person.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.parchment.com/sitemap.xml.
AI search readiness
No llms.txt
There is no /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.
3 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 (2,025 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without a meta description
/platform/k-12/award-k-12, /platform/k-12/k-12-cumulative-folders, /platform/k-12/k-12-document-management, /platform/k-12/records-digitization, /platform/k-12/diploma-services and /platform/higher-education/certificate-services and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
/platform/k-12/k-12-district-transfer and /platform/higher-education/issuing use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example /platform/k-12/k-12-district-transfer, whose canonical is /platform/higher-education/issuing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages slow to respond
/students/order-status and /students/how-it-works took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
7 small tap targets
7 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
2 links through redirect chains
2 links go through two or more redirects, for example https://exchange.parchment.com/u/auth/login.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
9 checks passed
Served over HTTPS
The homepage is served over HTTPS (parchment.com).
Valid certificate (156 days left)
The certificate from Amazon · Amazon RSA 2048 M01 verifies for parchment.com and is valid for another 156 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://parchment.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 53 links work
All 53 links checked from your homepage (40 internal, 13 external) answered without errors.
security.txt published
A security.txt file tells researchers how to report a problem with your site.
Domain and trust
DNSSEC is off
parchment.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
3 checks passed
Domain is 26 years old
26 yearsparchment.com was registered in Apr 2000 through Amazon Registrar, Inc.. An established domain carries more trust with email providers and search engines.
Certificate issuers are restricted
CAA records allow only amazon.com, comodoca.com, globalsign.org and letsencrypt.org to issue certificates for parchment.com, so a mis-issued certificate from anyone else is refused.
Registered until Apr 2027
parchment.com is registered until Apr 2027.
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.
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 1,445 words of copy
The homepage carries about 1,445 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Order Now”.
47 calls to action
The homepage has 47 calls to action, for example “Skip to order status”, “Order & Status” and “Order Transcript”.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Email authentication
Email authentication score: 100/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:mktomail.com include:spf.mandrillapp.com include:stspg-customer.com include:_spf.google.com include:_spf…”.
DKIM signing found
A DKIM key is published (selector “google”, “k1” and “s1”), so receivers can verify mail really came from you.
Privacy and tracking
3 trackers load before any consent
3Before 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.
5 cookies set on arrival
5Opening 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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Hiring
- Hiring
- 58 open roles
- Teams
- Sales & Marketing (24), Research & Development (17), Client Services (11), General & Administration (5)
- Job board
- ashby
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This free review found 33 issues on parchment.com, including 17 speed issues, 4 SEO issues 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.