Website review, no card needed
perelson.com website review
Visit site (opens in a new tab)Reviewed 24 October 202614 issues · 74 checks
This review found 14 issues worth fixing on perelson.com, 4 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 6.8 s |
| May 9, 2026 | 6.7 s |
| May 16, 2026 | 6.6 s |
| May 23, 2026 | 6.4 s |
| May 30, 2026 | 6.0 s |
| Jun 6, 2026 | 5.9 s |
| Jun 13, 2026 | 6.1 s |
| Jun 20, 2026 | 6.4 s |
| Jun 27, 2026 | 6.9 s |
| Jul 4, 2026 | 7.1 s |
| Jul 11, 2026 | 7.0 s |
| Jul 18, 2026 | 6.8 s |
| Jul 25, 2026 | 6.6 s |
| Aug 1, 2026 | 6.7 s |
| Aug 8, 2026 | 6.8 s |
| Aug 15, 2026 | 6.9 s |
| Aug 22, 2026 | 6.9 s |
| Aug 29, 2026 | 6.6 s |
| Sep 5, 2026 | 6.5 s |
| Sep 12, 2026 | 6.3 s |
| Sep 19, 2026 | 5.8 s |
| Sep 26, 2026 | 5.9 s |
| Oct 3, 2026 | 5.8 s |
| Oct 10, 2026 | 5.8 s |
| Oct 17, 2026 | 5.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 85 ms |
| May 9, 2026 | 80 ms |
| May 16, 2026 | 86 ms |
| May 23, 2026 | 85 ms |
| May 30, 2026 | 83 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 84 ms |
| Jun 20, 2026 | 83 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 73 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 85 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 82 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 81 ms |
| Oct 17, 2026 | 80 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
Mobile performance score: 74
74/100Your mobile performance score is 74 (desktop: 96). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 159 KiBAbout 159 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 315 ms
315 msGoogle Tag Manager costs a phone 315 ms of main-thread work and 306 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, trustindex.io and herefish.com and others), adding 352 KiB and 342 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 241 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 25 KiB1 file is served with short cache lifetimes, so returning visitors download them again (25 KiB).
Improve image delivery
53 KiB4 images could be 53 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 271 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.5 s
4.5 sReal visitors wait 4.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Time to Interactive: 5.7 s
5.7 sThe page becomes fully interactive after 5.7 s. Good is under 3.8 s.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 85 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 6.8 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 149 ms
149 msScripts block the page for only 149 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.063
0.063The layout barely moves while loading (CLS 0.063, good is under 0.1).
Images and page weight
1 image in older formats
1 image (44 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.
About 0.2 g of CO₂ per visit
0.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 24.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 741 KiB in 30 requests
741 KiBYour homepage downloads 741 KiB in 30 requests on a phone: images 342 KiB (18), scripts 342 KiB (5) and fonts 35 KiB (1). That is a lean page.
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
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “Salt Lake City Staffing Agency & Executive Search Firm | PrincePerelson”.
55 internal links, 4 external
The homepage links to 55 pages on perelson.com and 4 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Utah's premier staffing agency and executive search firm. Since 1992, PrincePerelson has connected Salt Lake City emplo…”.
One H1 headline
Your main headline reads: “Relationship Driven Recruiting”.
Canonical URL set
The canonical URL is https://perelson.com/.
Structured data in place
Structured data found: Organization and ProfessionalService.
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://perelson.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (899 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://perelson.com/llms.txt (2 KiB, 20 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://perelson.com/careers has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://perelson.com/careers 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
6 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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
10 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 856 words of copy
The homepage carries about 856 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Us: 1-801-532-1000”.
3 calls to action
The homepage has 3 calls to action, for example “Call Us: 1-801-532-1000”, “Contact Center & Customer Service” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 11 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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
2Opening 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.
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.
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 perelson.com, 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
- Netlify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 14 issues on perelson.com, including 10 speed issues and 1 SEO issue. 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.