Website review, no card needed
pplmotorhomes.com website review
Visit site (opens in a new tab)Reviewed 20 October 202636 issues · 89 checks
This review found 36 issues worth fixing on pplmotorhomes.com, 11 of them high impact, across 89 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 995 ms |
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 993 ms |
| Jun 13, 2026 | 965 ms |
| Jun 20, 2026 | 963 ms |
| Jun 27, 2026 | 957 ms |
| Jul 4, 2026 | 967 ms |
| Jul 11, 2026 | 989 ms |
| Jul 18, 2026 | 998 ms |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 999 ms |
| Aug 8, 2026 | 961 ms |
| Aug 15, 2026 | 937 ms |
| Aug 22, 2026 | 899 ms |
| Aug 29, 2026 | 842 ms |
| Sep 5, 2026 | 752 ms |
| Sep 12, 2026 | 675 ms |
| Sep 19, 2026 | 628 ms |
| Sep 26, 2026 | 587 ms |
| Oct 3, 2026 | 593 ms |
| Oct 10, 2026 | 590 ms |
| Oct 17, 2026 | 590 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 74 ms |
| May 9, 2026 | 72 ms |
| May 16, 2026 | 72 ms |
| May 23, 2026 | 72 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 72 ms |
| Jun 20, 2026 | 75 ms |
| Jun 27, 2026 | 76 ms |
| Jul 4, 2026 | 75 ms |
| Jul 11, 2026 | 76 ms |
| Jul 18, 2026 | 75 ms |
| Jul 25, 2026 | 74 ms |
| Aug 1, 2026 | 73 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 72 ms |
| Aug 22, 2026 | 72 ms |
| Aug 29, 2026 | 71 ms |
| Sep 5, 2026 | 69 ms |
| Sep 12, 2026 | 66 ms |
| Sep 19, 2026 | 62 ms |
| Sep 26, 2026 | 62 ms |
| Oct 3, 2026 | 62 ms |
| Oct 10, 2026 | 63 ms |
| Oct 17, 2026 | 63 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
4.9 s · 606 KiBAbout 606 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.9 s faster on a phone.
Improve image delivery
3.5 s · 724 KiB4 images could be 724 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.
Use efficient cache lifetimes
900 ms · 232 KiB39 files are served with short cache lifetimes, so returning visitors download them again (232 KiB).
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 85). 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 CDN, Google Tag Manager and mozu.com and others), adding 3.3 MB and 654 ms of main-thread time.
Minify JavaScript
750 ms · 38 KiB38 KiB could be saved by minifying JavaScript.
Reduce unused CSS
600 ms · 96 KiBAbout 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google CDN adds 288 ms
288 msGoogle CDN costs a phone 288 ms of main-thread work and 774 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.
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
mozu.com adds 91 ms
91 msmozu.com costs a phone 91 ms of main-thread work and 2.0 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.
Google Tag Manager adds 241 ms
241 msGoogle Tag Manager costs a phone 241 ms of main-thread work and 469 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.
Legacy JavaScript
150 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 85 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 776 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.6 s
9.6 sThe first text or image appears after 9.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.4 s
24.4 sYour largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 24.5 s
24.5 sThe page becomes fully interactive after 24.5 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 75 ms
75 msReal visitors wait 75 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 685 ms
685 msReal visitors wait 685 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 74 ms to 63 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 41% faster for real visitors
-41%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 115 ms
115 msScripts block the page for only 115 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 79 requests
4.3 MBYour homepage downloads 4.3 MB in 79 requests on a phone: images 2.0 MB (16), scripts 1.5 MB (35) and other files 406 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (324 KiB) 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.
2 images below the first screen load straight away
2 images further down the page (43 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (61 elements)
All page content should be contained by landmarks: 61 elements on the page fail this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Used RVs, Motorhomes for Sale, and Consigned sales | PPL Motor Homes”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
170 internal links, 11 external
The homepage links to 170 pages on pplmotorhomes.com and 11 external pages.
5 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Used & Consigned RVs for sales in Texas. We are a Full Service RV Dealership & Consignment Leader Since 1972. Find, Buy…”.
One H1 headline
Your main headline reads: “USED MOTORHOMES & RVs FOR SALE”.
Canonical URL set
The canonical URL is https://www.pplmotorhomes.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.pplmotorhomes.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.pplmotorhomes.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,135 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.pplmotorhomes.com/sellyourrv has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 104 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 7 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “ga is not defined”.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 912 words of copy
The homepage carries about 912 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: “Contact Us” and “Login / Register”.
15 calls to action
The homepage has 15 calls to action, for example “Contact an RV Financing Expert”, “Contact Us” and “Login / Register”.
3 short forms
3 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
15 other companies contacted
Loading the homepage contacts 15 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 pplmotorhomes.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
- Bootstrap
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on pplmotorhomes.com, including 16 speed issues, 4 SEO issues and 2 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.