Website review, no card needed

apexorderpickup.com logo

apexorderpickup.com website review

Visit site (opens in a new tab)Reviewed 25 October 202638 issues · 90 checks

This review found 38 issues worth fixing on apexorderpickup.com, 15 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.5 s4.4 sMay 2Oct 175.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.7 s
May 16, 20264.9 s
May 23, 20265.3 s
May 30, 20265.8 s
Jun 6, 20266.2 s
Jun 13, 20266.0 s
Jun 20, 20266.0 s
Jun 27, 20265.9 s
Jul 4, 20265.8 s
Jul 11, 20266.0 s
Jul 18, 20265.9 s
Jul 25, 20266.2 s
Aug 1, 20266.1 s
Aug 8, 20265.9 s
Aug 15, 20266.0 s
Aug 22, 20265.7 s
Aug 29, 20265.9 s
Sep 5, 20265.9 s
Sep 12, 20266.1 s
Sep 19, 20266.1 s
Sep 26, 20266.0 s
Oct 3, 20265.8 s
Oct 10, 20265.5 s
Oct 17, 20265.6 s
Real-visitor tap response (INP)75th percentile, phones
198 ms105 msMay 30Oct 17131 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026122 ms
Jun 6, 2026125 ms
Jun 13, 2026120 ms
Jun 20, 2026123 ms
Jun 27, 2026136 ms
Jul 4, 2026123 ms
Jul 11, 2026136 ms
Jul 18, 2026133 ms
Jul 25, 2026116 ms
Aug 1, 2026153 ms
Aug 8, 2026164 ms
Aug 15, 2026187 ms
Aug 22, 2026163 ms
Aug 29, 2026157 ms
Sep 5, 2026163 ms
Sep 12, 2026145 ms
Sep 19, 2026162 ms
Sep 26, 2026161 ms
Oct 3, 2026143 ms
Oct 10, 2026142 ms
Oct 17, 2026131 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

Full-page screenshot of apexorderpickup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apexorderpickup.com at 0.7 s0.7 s
  2. apexorderpickup.com at 1.3 s1.3 s
  3. apexorderpickup.com at 2.0 s2.0 s
  4. apexorderpickup.com at 2.7 s2.7 s
  5. apexorderpickup.com at 3.4 s3.4 s
  6. apexorderpickup.com at 4.0 s4.0 s
  7. apexorderpickup.com at 4.7 s4.7 s
  8. apexorderpickup.com at 5.4 s5.4 s

Speed

13 to fix43
  • Reduce unused JavaScript

    96.9 s · 5.9 MB

    About 5.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 96.9 s faster on a phone.

  • Render-blocking requests

    4.3 s

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

  • YouTube adds 1.6 s

    1.6 s

    YouTube costs a phone 1.6 s of main-thread work and 22.6 MB 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.

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 9.1 s

    A phone's processor spends 9.1 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google CDN and Google Tag Manager and others), adding 27.0 MB and 3.9 s of main-thread time.

  • Google CDN adds 782 ms

    782 ms

    Google CDN costs a phone 782 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.

  • Reduce unused CSS

    750 ms · 185 KiB

    About 185 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Google Tag Manager adds 630 ms

    630 ms

    Google Tag Manager costs a phone 630 ms of main-thread work and 1.2 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.

  • hsappstatic.net adds 498 ms

    498 ms

    hsappstatic.net costs a phone 498 ms of main-thread work and 697 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.

  • Use efficient cache lifetimes

    150 ms · 368 KiB

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

  • 20 long tasks on the main thread

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

  • 1,607 HTML elements

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

  • Improve image delivery

    200 ms · 30 KiB

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Legacy JavaScript

    31 KiB

    Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

  • 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 65 ms

    65 ms

    Your server sent the HTML in 65 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • 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 s

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

  • Real-user FCP: 5.5 s

    5.5 s

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

  • Real-user TTFB: 4.5 s

    4.5 s

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

  • First Contentful Paint: 128.3 s

    128.3 s

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

  • Largest Contentful Paint: 134.7 s

    134.7 s

    Your largest element takes 134.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 128.3 s

    128.3 s

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

  • Time to Interactive: 162.7 s

    162.7 s

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

  • Real-user CLS: 0.16

    0.16

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

  • Total Blocking Time: 464 ms

    464 ms

    Scripts block taps and scrolling for 464 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

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

2 checks passed
  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Cumulative Layout Shift: 0.024

    0.024

    The layout barely moves while loading (CLS 0.024, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 30.4 MB in 408 requests

    30.4 MB

    Your homepage downloads 30.4 MB in 408 requests on a phone: scripts 23.7 MB (143), stylesheets 2.3 MB (102) and HTML 2.0 MB (37). Under 2 MB keeps phones on slow connections fast.

  • About 8.6 g of CO₂ per visit

    8.61 g

    By the Sustainable Web Design model, a visit to your homepage emits about 8.61 g of CO₂e: 1032.9 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

5 to fixGoogle 9094
  • 21 text elements with low contrast

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

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

    11 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 85 images in the HTML carry an alt attribute.

  • 45 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: 45 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

1 to fixGoogle 10093
  • Title is long (88 characters)

    Your title is 88 characters, so Google will cut it off around 60: “Apex Order Pickup Solutions | Smart Order Pickup Lockers for Faster, Easier Order Pickup”.

  • 58 internal links, 4 external

    The homepage links to 58 pages on apexorderpickup.com and 4 external pages.

7 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Apex smart locker solutions make order pickup fast, accurate, and secure—helping operators boost throughput, cut labor,…”.

  • One H1 headline

    Your main headline reads: “Deliver a fast, easy, and secure pickup experience.”.

  • Canonical URL set

    The canonical URL is https://apexorderpickup.com/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://apexorderpickup.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://apexorderpickup.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 (889 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 3 pages without an H1

    https://apexorderpickup.com/resources, https://apexorderpickup.com/resources/blogs and https://apexorderpickup.com/resources/case-studies have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 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 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 8 small tap targets

    8 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 7 third-party cookies

    7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 12-field form

    Your longest form asks for 12 fields (10 required). Every extra field lowers completion.

  • No opening hours

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

  • No map or directions link

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

  • 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 318 words of copy

    The homepage carries about 318 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET IN TOUCH”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “GET STARTED”, “GET IN TOUCH” and “Subscribe to our newsletter”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, HubSpot, LinkedIn Insight and Umami.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 3 email links.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

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

  • 42 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 apexorderpickup.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
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 38 issues on apexorderpickup.com, including 23 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25