✓
First HeadingiChecks that the page starts with an H1 — a missing or misplaced first heading breaks reading order for screen reader users.
Page starts with H1
✓
Page TitleiChecks that the <title> tag is present and 30–60 chars — titles drive browser tabs, bookmarks, and the main SEO click-through link.
Good length (43 chars)
"FedEx – Zebra FedEx Ground Approved Devices"
⚠
Meta DescriptioniChecks for a meta description between 120–160 chars — search engines use this as the snippet shown under your page title in results.
Too long (190 chars, may truncate)
"Zebra is the FedEx Ground approved manufacturer for hand-held scanning devices. Explore the TC27, TC58, and TC78 rugged mobile computers built for FedEx Ground Independent Service Providers."
✓
H1 TagiChecks for exactly one H1 — multiple H1s dilute SEO signals and confuse assistive technologies.
Single H1: "Welcome FedEx Ground Independent Service Providers"
✓
OG: og:titleiChecks Open Graph tags (og:title, og:description, og:image, etc.) — these control how your page appears when shared on social platforms.
FedEx – Zebra FedEx Ground Approved Devices
✓
OG: og:descriptioniChecks Open Graph tags (og:title, og:description, og:image, etc.) — these control how your page appears when shared on social platforms.
Zebra is the FedEx Ground approved manufacturer for hand-held scanning devices. Explore the TC27, TC58, and TC78 rugged mobile computers built for FedEx Ground Independent Service Providers.
⚠
OG: og:imageiChecks Open Graph tags (og:title, og:description, og:image, etc.) — these control how your page appears when shared on social platforms.
og:image is missing
⚠
Structured DataiChecks for JSON-LD or microdata markup — structured data helps search engines understand your content and can unlock rich search results.
No JSON-LD structured data found
✓
Invalid AnchorsiChecks for links with missing, empty, or placeholder hrefs — broken anchors are inaccessible to keyboard and screen reader users. If the element triggers an action rather than navigating, use a <button> instead of <a>.
No empty, missing, or placeholder hrefs found
✓
Broken Internal LinksiChecks that internal links return a valid HTTP response — broken links hurt SEO crawl budget and frustrate users.
No internal links found
✓
Broken Internal ImagesiChecks that internal image src paths resolve — broken images degrade perceived quality and can trigger accessibility failures.
All 9 internal images OK
⚠
Image Lazy LoadingiChecks that images use loading="lazy" — deferring off-screen images improves initial page load and Core Web Vitals.
15 images, none use lazy loading
✓
Environment Leaks
No environment-pattern URLs found
✓
Tag ManageriChecks that Google Tag Manager or Adobe Launch is present — without a tag manager, analytics and marketing tags cannot fire.
Adobe tag manager detected
✓
Analytics CookiesiChecks for GA4 or Adobe Analytics cookies — confirms that analytics tracking is active on the page.
Adobe Analytics cookies found (2): AMCVS_912302BE532950CA0A490D4C%40AdobeOrg, AMCV_912302BE532950CA0A490D4C%40AdobeOrg
✓
Consent Management (CMP)iChecks for a consent management platform — CMPs are required under GDPR and similar regulations before setting non-essential cookies.
CMP detected: OneTrust (11 request(s))
✓
Canonical URLiChecks for a canonical link tag — canonicals prevent duplicate-content penalties by telling search engines which URL is authoritative.
Canonical set: https://mktg.zebra.com/fedex
✓
Viewport MetaiChecks that the viewport meta tag is set correctly — without it, mobile browsers render the page at desktop width and zoom out.
Viewport: width=device-width, initial-scale=1
✓
Robots MetaiChecks the robots meta tag — a misconfigured robots tag can accidentally block pages from being indexed by search engines.
Robots: index,follow
✓
Landmark StructureiChecks that the page has HTML landmark regions (main, nav, header, footer) — landmarks let screen reader users jump directly to key sections.
3 semantic landmarks found
✓
HTTPS ProtocoliChecks that the page is served over HTTPS — HTTP pages are flagged as insecure by browsers and penalised in search rankings.
Page served over HTTPS
✓
Insecure ResourcesiChecks for mixed content (HTTP resources on an HTTPS page) — browsers block or warn about these, breaking functionality.
No insecure HTTP references found
⚠
Security HeadersiChecks for recommended HTTP security headers (CSP, X-Frame-Options, etc.) — missing headers leave the page open to clickjacking and XSS.
Missing security headers: x-frame-options, x-content-type-options, x-xss-protection