Website review, no card needed
auctane.com website review
Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 80 checks
This review found 34 issues worth fixing on auctane.com, 10 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for ShipStation Global (formerly Auctane)
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 6, 2026 | 69 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 69 ms |
| Jun 27, 2026 | 68 ms |
| Jul 4, 2026 | 69 ms |
| Jul 11, 2026 | 67 ms |
| Jul 18, 2026 | 70 ms |
| Jul 25, 2026 | 75 ms |
| Aug 1, 2026 | 75 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 76 ms |
| Aug 22, 2026 | 73 ms |
| Aug 29, 2026 | 73 ms |
| Sep 5, 2026 | 70 ms |
| Sep 12, 2026 | 69 ms |
| Sep 19, 2026 | 69 ms |
| Sep 26, 2026 | 69 ms |
| Oct 3, 2026 | 71 ms |
| Oct 10, 2026 | 73 ms |
| Oct 17, 2026 | 75 ms |
| Oct 24, 2026 | 77 ms |
| Oct 31, 2026 | 78 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
1.6 s · 228 KiB13 files are served with short cache lifetimes, so returning visitors download them again (228 KiB).
Reduce unused JavaScript
1.2 s · 300 KiBAbout 300 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.1 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 63
63/100Your mobile performance score is 63. 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 Tag Manager, Optanon and Hubspot and others), adding 772 KiB and 638 ms of main-thread time.
Improve image delivery
450 ms · 90 KiB1 image could be 90 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
180 ms · 52 KiBAbout 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 163 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 915 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.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Powerful logistics. Powering your business. Intelligent shi…”.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Real-user TTFB: 938 ms
938 msReal visitors wait 938 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 265 ms
265 msScripts block taps and scrolling for 265 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 69 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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: 74 ms
74 msReal visitors wait 74 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image in older formats
1 image (169 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.
1 image below the first screen load straight away
1 image further down the page (169 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 39.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.2 MB in 61 requests
1.2 MBYour homepage downloads 1.2 MB in 61 requests on a phone: scripts 779 KiB (27), images 231 KiB (8) and stylesheets 56 KiB (7). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (25 characters)
Your title is only 25 characters: “Home - ShipStation Global”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, SoftwareApplication and WebPage) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
34 internal links, 21 external
The homepage links to 34 pages on auctane.com and 21 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Powerful logistics. Powering your business.”.
Canonical URL set
The canonical URL is https://www.shipstationglobal.com/.
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://www.shipstationglobal.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.shipstationglobal.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 (367 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.shipstationglobal.com/patents is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.shipstationglobal.com/news and https://www.shipstationglobal.com/press all use the title “News Archive - ShipStation Global”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://www.shipstationglobal.com/products, https://www.shipstationglobal.com/news, https://www.shipstationglobal.com/company, https://www.shipstationglobal.com/careers, https://www.shipstationglobal.com/press/shipstation-global and https://www.shipstationglobal.com/news/shipstation-integrates-ai-into-the-shipping-workflow-with-intelligent-automation-and-conversational-analytics and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.shipstationglobal.com/news, whose canonical is https://www.shipstationglobal.com/press. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page with very little text
https://www.shipstationglobal.com/legal 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 and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'appendChild')”.
2 checks passed
Tap targets are thumb-sized
12 of 12 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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.
About 395 words of copy
The homepage carries about 395 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 22 customer or partner logos and “3M+ customers”.
Analytics in place
Analytics detected: Segment.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot and Segment (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 6 of them by other companies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 auctane.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Segment
- Hosting
- Cloudflare
Hiring
- Hiring
- 23 open roles
- Teams
- Research & Development (9), IT (2), Sales (2), Account Management (1)
- Job board
- greenhouse
Company
- Employees
- 692
- Headquarters
- Austin
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on auctane.com, including 13 speed issues, 6 SEO issues and 3 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.