Website review, no card needed
capricornlogistics.com website review
Visit site (opens in a new tab)Reviewed 2 November 202650 issues · 84 checks
This review found 50 issues worth fixing on capricornlogistics.com, 22 of them high impact, across 84 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
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 4.0 s |
| Oct 31, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 124 ms |
| May 23, 2026 | 125 ms |
| May 30, 2026 | 130 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 140 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 125 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 134 ms |
| Oct 31, 2026 | 140 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
1.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
Use efficient cache lifetimes
5.4 s · 5.2 MB43 files are served with short cache lifetimes, so returning visitors download them again (5.2 MB).
Render-blocking requests
5.5 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.
amcharts.com adds 3.1 s
3.1 samcharts.com costs a phone 3.1 s of main-thread work and 506 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused JavaScript
2.3 s · 416 KiBAbout 416 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Improve image delivery
1.4 s · 830 KiB15 images could be 830 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Font display
1.4 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).
Mobile performance score: 3
3/100Your mobile performance score is 3. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 4.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 third-party services on the page
4 third-party services load with your homepage (amcharts.com, jQuery CDN and Google Fonts and others), adding 641 KiB and 3.1 s of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.
Reduce unused CSS
600 ms · 95 KiBAbout 95 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.
Minify JavaScript
450 ms · 68 KiB68 KiB could be saved by minifying JavaScript.
Legacy JavaScript
400 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
2,798 HTML elements
The page has 2,798 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 16 KiB16 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 46 ms
46 msYour server sent the HTML in 46 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 LCP: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.91
0.91For real visitors the layout shifts by 0.91 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 22.4 s
22.4 sYour largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 16.2 s
16.2 sVisually, the page fills in at 16.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 23.4 s
23.4 sThe page becomes fully interactive after 23.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.911
0.911The layout shifts by 0.911 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 2.7 s
2.7 sScripts block taps and scrolling for 2.7 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
57 images without width and height
57 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 124 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 157 ms
157 msReal visitors wait 157 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 6.1 MB in 90 requests
6.1 MBYour homepage downloads 6.1 MB in 90 requests on a phone: images 4.7 MB (36), scripts 979 KiB (32) and fonts 235 KiB (4). Under 2 MB keeps phones on slow connections fast.
17 images in older formats
17 images (2.2 MB) 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.
13 images below the first screen load straight away
13 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
277 KiB3 images are downloaded at several times the size a phone draws them, for example How-Capricorn-Logistics-contribute-to-a-Sustainable-Future.p at 1,280 px wide, shown at 360 px. Resized copies would save about 277 KiB.
About 1.7 g of CO₂ per visit
1.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.72 g of CO₂e: 206.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 3 mores need a person to judge. 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.
Title is short (19 characters)
Your title is only 19 characters: “Capricorn Logistics”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (53 characters)
Your meta description is only 53 characters: “Best Integrated Logistics and Supply Chain Solutions.”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://capricornlogistics.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at capricornlogistics.com/robots.txt, the first file search crawlers ask for.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
38 internal links, 1 external
The homepage links to 38 pages on capricornlogistics.com and 1 external page.
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://capricornlogistics.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
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.
Text is in the HTML
Your server sends the page's text in the HTML (660 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages are broken
Your homepage links to https://capricornlogistics.com/simplifying-customs-with-capricorns-expertise, https://capricornlogistics.com/how-capricorn-logistics-contribute-to-a-sustainable-future and https://capricornlogistics.com/the-importance-of-customer-support-in-logistics-how-capricorn-logistics-goes-above-and-beyond, which answer with an error. Visitors hit a dead end and search engines drop them.
11 pages share a title
/, https://capricornlogistics.com/About_us.html, https://capricornlogistics.com/key-projects.html, https://capricornlogistics.com/Global_Freight_Forwarding.html, https://capricornlogistics.com/Integrated_Supply_Chain_Solutions.html and https://capricornlogistics.com/Customs_Brokerage.html and 5 others all use the title “Capricorn Logistics”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://capricornlogistics.com/About_us.html, https://capricornlogistics.com/key-projects.html, https://capricornlogistics.com/Global_Freight_Forwarding.html, https://capricornlogistics.com/Integrated_Supply_Chain_Solutions.html, https://capricornlogistics.com/Customs_Brokerage.html and https://capricornlogistics.com/control-tower-service.html and 4 others use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://capricornlogistics.com/About_us.html, https://capricornlogistics.com/key-projects.html, https://capricornlogistics.com/Global_Freight_Forwarding.html, https://capricornlogistics.com/Integrated_Supply_Chain_Solutions.html, https://capricornlogistics.com/Customs_Brokerage.html and https://capricornlogistics.com/control-tower-service.html and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 11 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 11 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://capricornlogistics.com/wp-content/uploads/2025/04/Great-Place-To-Work-LOGO.png.
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 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
17 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 483 words of copy
The homepage carries about 483 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: “GET A QUOTE”.
7 calls to action
The homepage has 7 calls to action, for example “Contact Us”, “GET A QUOTE” and “Get in touch”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 email links.
Privacy and tracking
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 capricornlogistics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- Public Domain Registry Pdr
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on capricornlogistics.com, including 26 speed issues, 7 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.