Website review, no card needed
24petconnect.com website review
Visit site (opens in a new tab)Reviewed 12 October 202646 issues · 89 checks
This review found 46 issues worth fixing on 24petconnect.com, 17 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 884 ms |
| Apr 25, 2026 | 884 ms |
| May 2, 2026 | 888 ms |
| May 9, 2026 | 893 ms |
| May 16, 2026 | 894 ms |
| May 23, 2026 | 894 ms |
| May 30, 2026 | 897 ms |
| Jun 6, 2026 | 900 ms |
| Jun 13, 2026 | 912 ms |
| Jun 20, 2026 | 925 ms |
| Jun 27, 2026 | 933 ms |
| Jul 4, 2026 | 940 ms |
| Jul 11, 2026 | 936 ms |
| Jul 18, 2026 | 931 ms |
| Jul 25, 2026 | 929 ms |
| Aug 1, 2026 | 927 ms |
| Aug 8, 2026 | 926 ms |
| Aug 15, 2026 | 931 ms |
| Aug 22, 2026 | 937 ms |
| Aug 29, 2026 | 943 ms |
| Sep 5, 2026 | 952 ms |
| Sep 12, 2026 | 954 ms |
| Sep 19, 2026 | 961 ms |
| Sep 26, 2026 | 972 ms |
| Oct 3, 2026 | 976 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 54 ms |
| Apr 25, 2026 | 54 ms |
| May 2, 2026 | 54 ms |
| May 9, 2026 | 53 ms |
| May 16, 2026 | 53 ms |
| May 23, 2026 | 53 ms |
| May 30, 2026 | 54 ms |
| Jun 6, 2026 | 54 ms |
| Jun 13, 2026 | 54 ms |
| Jun 20, 2026 | 54 ms |
| Jun 27, 2026 | 54 ms |
| Jul 4, 2026 | 54 ms |
| Jul 11, 2026 | 54 ms |
| Jul 18, 2026 | 54 ms |
| Jul 25, 2026 | 54 ms |
| Aug 1, 2026 | 53 ms |
| Aug 8, 2026 | 53 ms |
| Aug 15, 2026 | 53 ms |
| Aug 22, 2026 | 53 ms |
| Aug 29, 2026 | 53 ms |
| Sep 5, 2026 | 53 ms |
| Sep 12, 2026 | 53 ms |
| Sep 19, 2026 | 53 ms |
| Sep 26, 2026 | 53 ms |
| Oct 3, 2026 | 53 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
Use efficient cache lifetimes
9.2 s · 1.9 MB16 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Render-blocking requests
9.3 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.3 s.
Reduce unused JavaScript
1.4 s · 257 KiBAbout 257 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 66). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
610 ms · 98 KiBAbout 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 265 ms. During a long task the page ignores taps.
2,297 HTML elements
The page has 2,297 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
200 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify JavaScript
150 ms · 17 KiB17 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 8 KiB8 KiB could be saved by minifying CSS.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, getbootstrap.com and FontAwesome CDN and others), adding 181 KiB and 107 ms of main-thread time.
Improve image delivery
10 KiB1 image could be 10 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.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 459 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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 CLS: 0.37
0.37For real visitors the layout shifts by 0.37 (75th percentile). Good is under 0.1.
First Contentful Paint: 12.5 s
12.5 sThe first text or image appears after 12.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Main Logo”.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.1 s
14.1 sThe page becomes fully interactive after 14.1 s. Good is under 3.8 s.
Real-user INP: 296 ms
296 msReal visitors wait 296 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 54 ms to 53 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 467 ms
467 msReal visitors wait 467 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 112 ms
112 msScripts block the page for only 112 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 25 requests
2.2 MBYour homepage downloads 2.2 MB in 25 requests on a phone: scripts 1.2 MB (9), fonts 762 KiB (4) and stylesheets 103 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
Certain ARIA roles must be contained by particular parents (4 elements)
Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail 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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
No XML sitemap
No XML sitemap at https://24petconnect.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at 24petconnect.com/robots.txt, the first file search crawlers ask for.
Only 4 internal links
The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
Meta description: 106 characters
Your meta description is 106 characters: “24Petconnect.com provides lost, found, and adoptable postings for animal welfare organizations nationwide.”.
Title: 48 characters
Your title is a healthy 48 characters: “24Petconnect: Lost, Found, and Adoptable Animals”.
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://24petconnect.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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
3 pages share a title
/, https://24petconnect.com/Ex/PrivacyPolicy and https://24petconnect.com/Ex/Accessibility all use the title “24Petconnect: Lost, Found, and Adoptable Animals”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://24petconnect.com/Ex/PrivacyPolicy and https://24petconnect.com/Ex/Accessibility use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://24petconnect.com/Ex/PrivacyPolicy and https://24petconnect.com/Ex/Accessibility have no <h1> headline, so visitors and search engines get no clear main topic.
2 internal pages checked
We fetched 2 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 2 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 2 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
15 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 95 words
The homepage has only about 95 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
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 24petconnect.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on 24petconnect.com, including 16 speed issues, 8 SEO issues and 5 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.