⚠
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 H2, not H1
The first heading on the page should be H1 to establish a clear document outline.
⚠
Page TitleiChecks that the <title> tag is present and 30–60 chars — titles drive browser tabs, bookmarks, and the main SEO click-through link.
Too short (12 chars, aim 30–60)
"Home | RAB2B"
✓
Meta DescriptioniChecks for a meta description between 120–160 chars — search engines use this as the snippet shown under your page title in results.
Good length (136 chars)
"We blend bold ideas and fresh perspectives to activate marketing solutions that stand out—vibrant, strategic and a little extraordinary."
✕
H1 TagiChecks for exactly one H1 — multiple H1s dilute SEO signals and confuse assistive technologies.
No H1 tag found
✓
OG: og:titleiChecks Open Graph tags (og:title, og:description, og:image, etc.) — these control how your page appears when shared on social platforms.
Home | RAB2B
✓
OG: og:descriptioniChecks Open Graph tags (og:title, og:description, og:image, etc.) — these control how your page appears when shared on social platforms.
We blend bold ideas and fresh perspectives to activate marketing solutions that stand out—vibrant, strategic and a little extraordinary.
✓
OG: og:imageiChecks Open Graph tags (og:title, og:description, og:image, etc.) — these control how your page appears when shared on social platforms.
https://www.rab2b.com/hubfs/RAB2B%20Website/Pages%20Preview/home-preview-a.jpg
✓
Structured DataiChecks for JSON-LD or microdata markup — structured data helps search engines understand your content and can unlock rich search results.
2 JSON-LD objects 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.
All 11 internal links OK
✓
Broken Internal ImagesiChecks that internal image src paths resolve — broken images degrade perceived quality and can trigger accessibility failures.
No internal images found
⚠
Image Lazy LoadingiChecks that images use loading="lazy" — deferring off-screen images improves initial page load and Core Web Vitals.
Only 34/35 images 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.
GTM tag manager detected
✓
Analytics CookiesiChecks for GA4 or Adobe Analytics cookies — confirms that analytics tracking is active on the page.
GA4 cookies found (2): _ga_3T0DDWTJ65, _ga
⚠
Consent Management (CMP)iChecks for a consent management platform — CMPs are required under GDPR and similar regulations before setting non-essential cookies.
No CMP network requests detected
✓
Canonical URLiChecks for a canonical link tag — canonicals prevent duplicate-content penalties by telling search engines which URL is authoritative.
Canonical set: https://www.rab2b.com
✓
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 meta not set (defaults to 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