joinptsolutions.com website review

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.

About 226 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.

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

The page has 3,356 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 images could be 313 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

About 186 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

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

4 third-party services load with your homepage (phenompeople.com, Google Tag Manager and talentegy.com and others), adding 2.3 MB and 370 ms of main-thread time.

phenompeople.com costs a phone 256 ms of main-thread work and 2.1 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.

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

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

8 KiB could be saved by minifying CSS.

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.

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.

For real visitors the layout shifts by 0.44 (75th percentile). Good is under 0.1.

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “As part of our team, you’ll join innovators and advocates, …”.

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

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

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

10 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 2.4 MB in 127 requests on a phone: images 833 KiB (23), scripts 550 KiB (22) and other files 546 KiB (66). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example Events-Thumbnail_1000x600-1729866355180.jpg at 1,000 px wide, shown at 298 px. Resized copies would save about 67 KiB.

6 images further down the page (332 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (5 elements).

Your meta description is only 4 characters: “Home”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“Be unstoppable with a career at PT Solutions.”, “Transformative Care.Evidence-Based Practice.Oppor…” and “Be unstoppable with a career at PT Solutions.”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 15 pages on joinptsolutions.com and 4 external pages.

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.

There is no https://www.joinptsolutions.com/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.

https://www.joinptsolutions.com/us/en, https://www.joinptsolutions.com/us/search-results, https://www.joinptsolutions.com/us/en/home and / all use the title “Careers at PT Solutions | PT Solutions jobs”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.joinptsolutions.com/us/search-results, https://www.joinptsolutions.com/us/en/home and / use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.joinptsolutions.com/us/search-results, whose canonical is https://www.joinptsolutions.com/us/en/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.joinptsolutions.com/us/en/search-results, https://www.joinptsolutions.com/us/en/jointalentcommunity and https://www.joinptsolutions.com/us/en/events have 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.

https://www.joinptsolutions.com/us/en/clinical-internship-program took over 3 s to send its HTML from our server.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Requests the geolocation permission on page load.

Chrome logged issues while loading the page (“Content security policy”).

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 798 words of visible text.

Before a visitor clicks anything, the page loads 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.

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

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.

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