https://sterlingbay.com·Sep 30, 2026, 12:48 PM·12 technologies·AI

sterlingbay.com

Built with Google Analytics, Google Recaptcha, Google Tag Manager, Gravity Forms, Php and 7 more

https://sterlingbay.com
Screenshot of sterlingbay.com

Performance

TTFB

215ms

DOM Ready

430ms

Load Complete

696ms

Requests

85

Total Size

4943KB

Domains

7

Errors

0

Technologies

Other

Google Analytics
AIhigh
Google Recaptcha
AIhigh
Google Tag Manager
AIhigh
Gravity Forms
AIhigh
Php
Script + AIhigh
Wordpressv3.7.1
Script + AIhigh
Wordpress Custom Theme
AIhigh
Yoast Seov28.2
AIhigh
Html5shiv
AImedium
Mysql
AImedium
Respond Js
AImedium
Apache Or Nginx
AIlow

Company estimate

Company

Sterling Bay

Real estate development and investment

Estimated annual tech spend

$15K

Founded

2008

HQ

Chicago, Illinois, USA

Page title 'Sterling Bay - Space to be bold' and the meta description ('developing real estate... one of the best real estate firms in Chicago') clearly identify the company as Sterling Bay, the well-known privately held Chicago-based commercial real estate development firm, and the page itself states it is a Chicago firm. No valuation figure is reported/was known, so valuation is null; techSpendUsd is a rough estimate based on the visible simple WordPress marketing stack (custom theme, Gravity Forms, Yoast SEO, Google Analytics/Tag Manager).

SEO recommendations

64

SEO health score

Solid foundational SEO is in place - a descriptive title, self-referencing canonical, and a strong meta description - but the head is bloated with render-blocking third-party scripts, schema markup is minimal, and internal linking/sitemap health could not be confirmed, all of which drag the page below its potential.

  • Improve page speedVery High

    The head loads synchronous Google Tag Manager (gtm.js and gtag.js), Google reCAPTCHA, and a large inline Gravity Forms bootstrap script before the title, plus ~20 favicon variants and a commented-out Typekit stylesheet.

    → Add defer/async to the GTM and reCAPTCHA scripts, strip legacy IE shims and unused favicon links, remove the dead Typekit comment, and preconnect to googletagmanager.com and gstatic.com.

    80%

    impact

  • Add structured data to your websiteHigh

    Only a basic Yoast WebPage schema graph was visible; no Organization, LocalBusiness/RealEstateAgent, or ContactPage entity exposes the firm's NAP (name, address, phone) and geo data.

    → Extend the Yoast schema with an Organization + RealEstateAgent entity (address, geo, opening hours, socialProfile) and add BreadcrumbList markup on interior property pages.

    55%

    impact

  • Improve internal linkingHigh

    The body and navigation HTML were not included in the sample, so internal link depth and anchor quality toward portfolio and leasing pages could not be verified.

    → Ensure every property and leasing page is reachable within 2-3 clicks of the homepage using keyword-specific anchors such as 'Lincoln Yards office space' instead of generic 'Learn more' links.

    50%

    impact

  • Optimize your sitemapHigh

    No sitemap URL or robots.txt reference appears in the head; the site likely has a Yoast sitemap_index.xml, but it is unverified and unreferenced in the evidence provided.

    → Confirm /sitemap_index.xml is enabled in Yoast, list it in robots.txt, and keep every sitemap entry URL identical to the canonical trailing-slash form.

    50%

    impact

  • Content to-do listMedium

    No body content was provided, but the lightweight head (short description, embedded forms) suggests the homepage may lack a substantial H1-led content block.

    → Add a semantic H1 plus a 500+ word block covering markets served, differentiators, and recent projects, interlinked to the portfolio pages.

    40%

    impact

  • Review similar contentMedium

    Only the head was sampled and it reads like a form-driven landing page, so overlap between the homepage copy and /about, /portfolio, or /news pages could not be verified.

    → Compare the homepage text against inner pages for thin or duplicated boilerplate, and check for cannibalizing pages all targeting the 'Chicago real estate developer' query.

    35%

    impact

  • Add OpenGraph tagsLow

    og:title/description/url/site_name and twitter:card are present, but no og:image or twitter:image is set, so social shares will render without a preview image.

    → Add an og:image (1200x630) of a flagship Chicago property plus the matching twitter:image so previews on Facebook, X, and LinkedIn display correctly.

    25%

    impact

  • Avoid internal redirectsLow

    HTML alone cannot reveal redirect chains, and all references consistently use clean https://sterlingbay.com/ URLs, but no crawl evidence confirms the canonical URL returns a 200 directly.

    → Crawl the site to confirm https://sterlingbay.com/ resolves with a 200 with no http->https, www->non-www, or trailing-slash hop in the chain.

    20%

    impact

  • Improve page titlesLow

    The title tag 'Sterling Bay - Space to be bold' is present at ~35 characters and leads with the brand, well within the 60-character limit.

    → Keep the brand-first format but consider appending a high-value keyword such as 'Chicago Commercial Real Estate Development' to capture non-brand queries.

    15%

    impact

  • Trailing slashes may cause duplicate contentLow

    A self-referencing canonical (https://sterlingbay.com/) matches the og:url and the preferred domain, clearly signaling the trailing-slash URL as canonical.

    → Keep the self-referencing canonical and ensure Yoast sitemap URLs and all internal hrefs use the same trailing-slash form to prevent mixed-version signals.

    10%

    impact

  • Improve meta descriptionsLow

    The 153-character description reads naturally, embeds the 'Chicago' local keyword, and communicates a clear value proposition ('one of the best real estate firms in Chicago').

    → Keep it, and consider adding a CTR hook such as 'View available office spaces now' while staying under 160 characters that truncate in the SERP.

    10%

    impact

AI-generated SEO assessment · impact = estimated priority for this page

Specification compliance (13 shortcomings)

75

Specification compliance score

21/28 required and 22/36 recommended practices implemented. 13 shortcomings to address.

21/28

Required

22/36

Recommended

13

Shortcomings

75%

Overall

  • The HTML doctypeRequired

    Standards-mode <!doctype html> present.

    100%

    Implemented

  • The lang attribute on <html>Required

    <html> declares a language.

    100%

    Implemented

  • <meta charset>Required

    Character encoding declared.

    100%

    Implemented

  • <meta viewport>Required

    Responsive viewport meta present.

    100%

    Implemented

  • The <title> elementRequired

    Page has a non-empty <title>.

    100%

    Implemented

  • <meta name="description">Recommended

    Meta description present.

    100%

    Implemented

  • Canonical URL (rel="canonical")Recommended

    Canonical link present.

    100%

    Implemented

  • Favicons and app iconsRecommended

    Icon link(s) declared.

    100%

    Implemented

  • <meta name="theme-color">Recommended

    theme-color declared.

    100%

    Implemented

  • <meta name="color-scheme">Recommended

    No color-scheme — form controls and scrollbars will not adapt to dark mode.

    0%

    Not implemented

  • Open Graph protocolRecommended

    Open Graph tags present.

    100%

    Implemented

  • Feed discovery with rel="alternate"Recommended

    Feed auto-discovery link present.

    100%

    Implemented

  • Feed content hygieneRecommended

    Feed content quality cannot be assessed from a page scan.

    —

    Needs review

  • Popover APIRecommended

    No popover attributes — only applies if the page has popovers/menus.

    —

    Needs review

  • robots.txtRecommended

    robots.txt is served.

    100%

    Implemented

  • XML sitemapsRecommended

    An XML sitemap is present or referenced.

    100%

    Implemented

  • Sitemap index filesRecommended

    Sitemap index in use.

    100%

    Implemented

  • Image and video sitemap extensionsOptional

    No image/video sitemap extensions detected.

    —

    Needs review

  • URL structureRecommended

    URL path is clean and readable.

    100%

    Implemented

  • Redirects (301/302/308)Required

    http:// redirects to https with a 3xx status.

    100%

    Implemented

  • Soft 404sAvoid

    Nonexistent paths return a real 404/410.

    100%

    Implemented

  • Meta robots and X-Robots-TagRequired

    Indexing is not being blocked by robots meta / X-Robots-Tag.

    100%

    Implemented

  • Heading hierarchyRequired

    No <h1> on the page — every page needs one top-level heading.

    0%

    Not implemented

  • Internal linkingRecommended

    39 internal links found.

    100%

    Implemented

  • Structured data (JSON-LD)Recommended

    JSON-LD structured data present.

    100%

    Implemented

  • BreadcrumbsRecommended

    Breadcrumb markup present.

    100%

    Implemented

  • IndexNowOptional

    IndexNow integration cannot be detected from a page scan.

    —

    Needs review

  • Colour contrastRequired

    Colour contrast requires rendering analysis — review with an automated contrast checker.

    —

    Needs review

  • Image alt textRequired

    All 13 images declare alt text.

    100%

    Implemented

  • Form labelsRequired

    4 form fields but only 2 label/aria-label associations — label every input.

    50%

    Partial

  • Keyboard navigationRequired

    Keyboard operability needs interactive testing.

    —

    Needs review

  • Visible focus indicatorsRequired

    Focus-indicator visibility needs rendering review.

    —

    Needs review

  • Skip linksRecommended

    Skip-to-content link present.

    100%

    Implemented

  • Semantic HTML and landmarksRequired

    Semantic landmark elements in use.

    100%

    Implemented

  • ARIA — first rule of ARIARecommended

    No obvious ARIA misuse, but full review needs assistive-tech testing.

    —

    Needs review

  • Descriptive link textRequired

    Generic link text like "click here"/"read more" found — describe the destination.

    50%

    Partial

  • Empty links and buttonsAvoid

    No empty links or buttons detected.

    100%

    Implemented

  • Accessible form errorsRequired

    Form-error accessibility needs interactive testing.

    —

    Needs review

  • Document and parts languageRequired

    Document language is declared.

    100%

    Implemented

  • Reduced motionRequired

    No inline prefers-reduced-motion rule — verify external CSS respects reduced motion.

    —

    Needs review

  • Accessibility overlaysAvoid

    No accessibility-overlay widget detected.

    100%

    Implemented

  • Captions and transcriptsRequired

    No audio/video requiring captions.

    100%

    Implemented

  • Accessible data tablesRequired

    No data tables on the page.

    100%

    Implemented

  • Touch target sizeRequired

    Touch-target sizing needs rendering measurement.

    —

    Needs review

  • Hidden until foundRecommended

    Not used — only relevant for collapsible/accordion content.

    —

    Needs review

  • Native interactive elementsRecommended

    Could not confirm use of native interactive elements.

    —

    Needs review

  • CSS state and relational selectorsRecommended

    CSS selector strategy needs source review.

    —

    Needs review

  • HTTPS and TLSRequired

    Page is served over HTTPS.

    100%

    Implemented

  • HSTS (Strict-Transport-Security)Required

    HSTS header present.

    100%

    Implemented

  • Content Security Policy (CSP)Recommended

    No CSP header — the page has no defence-in-depth against injected scripts.

    0%

    Not implemented

  • /.well-known/security.txtRecommended

    No /.well-known/security.txt — researchers have no disclosure contact.

    0%

    Not implemented

  • X-Content-Type-Options: nosniffRequired

    No X-Content-Type-Options: nosniff — browsers may MIME-sniff responses.

    0%

    Not implemented

  • Clickjacking protectionRequired

    No frame-ancestors or X-Frame-Options — the page can be framed for clickjacking.

    0%

    Not implemented

  • Referrer-PolicyRecommended

    No Referrer-Policy — full URLs may leak to third parties.

    0%

    Not implemented

  • Permissions-PolicyRecommended

    No Permissions-Policy — powerful browser features are not locked down.

    0%

    Not implemented

  • Subresource Integrity (SRI)Recommended

    1/7 cross-origin scripts use SRI — add integrity hashes to the rest.

    14%

    Partial

  • Cookie attributes — Secure, HttpOnly, SameSiteRequired

    No cookies set on the document response.

    100%

    Implemented

  • DNS CAA recordsRecommended

    CAA records are not collected by the scanner — check your DNS provider.

    —

    Needs review

  • DNSSECOptional

    DNSSEC status is not collected by the scanner.

    —

    Needs review

  • Well-known URIsRecommended

    No /.well-known/ resources found.

    0%

    Not implemented

  • /.well-known/change-passwordOptional

    No change-password redirect — recommended if the site has accounts.

    —

    Needs review

  • /.well-known/openid-configurationOptional

    Not present — only relevant for OIDC identity providers.

    —

    Needs review

  • /.well-known/api-catalogRecommended

    Not present — recommended if the site exposes public APIs.

    —

    Needs review

  • /.well-known/webfingerOptional

    Not present — only relevant for federated identity.

    —

    Needs review

  • /.well-known/apple-app-site-associationOptional

    Not present — only needed for iOS Universal Links.

    —

    Needs review

  • /.well-known/assetlinks.jsonOptional

    Not present — only needed for Android App Links.

    —

    Needs review

  • /.well-known/nodeinfoOptional

    Not present — only relevant for Fediverse servers.

    —

    Needs review

  • /.well-known/traffic-adviceOptional

    Not present — optional prefetch-proxy control file.

    —

    Needs review

  • Agent readinessRecommended

    Some agent-readiness signals present (llms.txt and/or structured data).

    100%

    Implemented

  • /llms.txtRecommended

    No /llms.txt — agents have no curated map of your key content.

    0%

    Not implemented

  • /llms-full.txtOptional

    No /llms-full.txt — optional full-content variant.

    —

    Needs review

  • Per-page Markdown source endpointsRecommended

    No Markdown source endpoint detected — recommended for content/doc sites.

    —

    Needs review

  • robots.txt for AI crawlersRecommended

    robots.txt has no explicit AI-crawler rules — state your stance on GPTBot/ClaudeBot/etc.

    0%

    Not implemented

  • Content Signals in robots.txtOptional

    No Content-Signal directives — optional usage-preference signalling.

    —

    Needs review

  • Web Bot Auth — verifiable bot identityOptional

    Web Bot Auth support cannot be detected from a scan.

    —

    Needs review

  • Stable URLsRequired

    URL has no obvious session/volatile parameters.

    100%

    Implemented

  • Structured data for agentsRecommended

    JSON-LD structured data present for agents.

    100%

    Implemented

  • Machine-readable formatsRecommended

    Machine-readable alternate (feed) declared.

    100%

    Implemented

  • HTTP Link headers for discoveryRecommended

    HTTP Link header present for discovery.

    100%

    Implemented

  • MCP and tool discoveryOptional

    No MCP/tool discovery endpoint — optional.

    —

    Needs review

  • A2A agent cardsOptional

    No A2A agent card — optional.

    —

    Needs review

  • Agent Skills discoveryRecommended

    Agent Skills discovery cannot be detected automatically.

    —

    Needs review

  • DNS for AI Discovery (DNS-AID)Optional

    DNS-AID records are not collected by the scanner.

    —

    Needs review

  • NLWeb — conversational interface discoveryOptional

    NLWeb support cannot be detected automatically.

    —

    Needs review

  • WebMCP — browser-native tools for agentsOptional

    WebMCP support cannot be detected automatically.

    —

    Needs review

  • Schemamap — discoverable JSON-LD endpointsOptional

    Schemamap support cannot be detected automatically.

    —

    Needs review

  • Core Web Vitals (LCP, INP, CLS)Required

    Lab load completed in 696ms (a proxy). Confirm LCP/INP/CLS with field data.

    85%

    Partial

  • Image optimisationRequired

    None of 7 raster images use WebP/AVIF — convert from PNG/JPEG.

    0%

    Not implemented

  • Lazy loading images, iframes, and videoRecommended

    loading="lazy" is used.

    100%

    Implemented

  • Preload, prefetch, preconnectRecommended

    Resource hints (preload/preconnect/…) present.

    100%

    Implemented

  • Cache-Control headersRequired

    Cache-Control set on the document (public, max-age=600).

    100%

    Implemented

  • No-Vary-Search response headerRecommended

    Not set — optional; helps cache/prefetch URLs that differ only by tracking params.

    —

    Needs review

  • Compression (gzip, brotli, zstd)Required

    Document is compressed (gzip).

    100%

    Implemented

  • Web font loadingRecommended

    No inline font-display/preload — ensure web fonts use font-display: swap to avoid invisible text.

    —

    Needs review

  • Critical CSS and render-blocking resourcesRecommended

    13 render-blocking stylesheets in <head> — inline critical CSS and defer the rest.

    20%

    Partial

  • Script loading — defer, async, moduleRecommended

    13/37 external scripts use defer/async/module — add defer to the rest.

    35%

    Partial

  • HTTP/2 and HTTP/3Recommended

    Protocol version not captured — verify HTTP/2/3 is enabled at your edge/CDN.

    —

    Needs review

  • Speculation RulesRecommended

    Speculation Rules present for instant navigations.

    100%

    Implemented

  • Resource hints overviewRecommended

    Resource hints are in use.

    100%

    Implemented

  • View TransitionsRecommended

    No View Transitions detected — optional polish for navigations.

    —

    Needs review

  • Back/forward cache (BFCache)Recommended

    BFCache eligibility needs runtime testing.

    —

    Needs review

  • Visibility-aware renderingRecommended

    No content-visibility detected — optional offscreen-render optimisation.

    —

    Needs review

  • CSS containmentOptional

    No CSS containment detected — optional.

    —

    Needs review

  • Scroll-driven animationsOptional

    Not detected — optional.

    —

    Needs review

  • Scrollbar gutterRecommended

    No scrollbar-gutter — optional; prevents layout shift when scrollbars toggle.

    —

    Needs review

  • Privacy policyRequired

    A privacy policy link/reference is present.

    100%

    Implemented

  • Cookie consentRequired

    No consent manager detected (and no document cookies) — required if you set non-essential cookies.

    —

    Needs review

  • Global Privacy Control (GPC)Recommended

    GPC handling is server-side and cannot be confirmed from a scan.

    —

    Needs review

  • Third-party scripts and privacyRecommended

    5 third-party script origin(s) — audit each for data collection.

    70%

    Partial

  • Privacy-respecting analyticsRecommended

    Tracking-based analytics (Google Analytics) detected — consider a cookieless alternative.

    40%

    Partial

  • Data minimisationRecommended

    Data-minimisation practices need a manual review of forms and backend.

    —

    Needs review

  • Custom error pages (404, 500)Required

    Missing pages return 404 with a substantial (likely custom) error page.

    100%

    Implemented

  • Maintenance pages and 503Recommended

    Maintenance behaviour can only be observed during downtime.

    —

    Needs review

  • Offline support and service workersOptional

    No service worker detected — optional offline/PWA support.

    —

    Needs review

  • Web app manifestRecommended

    No <link rel="manifest"> — add a web app manifest for installability.

    0%

    Not implemented

  • Monitoring and uptimeRecommended

    Monitoring is operational and cannot be detected from the page.

    —

    Needs review

Deterministic audit against the website specification checklist. “Needs review” items can't be confirmed from a headless scan and are excluded from the score.

DNS & Infrastructure

DNSDomainDiscover
EmailBarracuda Networks (Barracuda Email Security)
HostingPantheon (via Fastly/AS54113)

IP Addresses

23.185.0.253
Pantheon
🇺🇸San Francisco, United States
2620:12a:8000::253IPv6
2620:12a:8001::253IPv6

Nameservers

ns2.domaindiscover.com
ns1.domaindiscover.com

Mail Servers (MX)

0d129714a.ess.barracudanetworks.com
5d129714b.ess.barracudanetworks.com

AI Analysis Notes

  • ·DNS hosted by DomainDiscover (ns1/ns2.domaindiscover.com)
  • ·Email handled by Barracuda Email Security gateway (ess.barracudanetworks.com)
  • ·SPF includes Microsoft 365 (spf.protection.outlook.com), SendGrid, Yardi (asp-spf1/2.yardi.com), and Autotask
  • ·Domain verification records for Google, Microsoft, and Anthropic present
  • ·Hosted on Pantheon infrastructure, fronted by Fastly CDN (AS54113)

Email & Deliverability

95

Email health score

Barracuda Email Security Service (ESS)

Sterling Bay's email posture is strong: SPF hard-fails (-all) with only 5 includes, DMARC is enforced at p=reject with rua/ruf reporting to Barracuda, and multiple DKIM signing selectors are published, so spoofing is already well mitigated. The only real gap is the absent MTA-STS policy; the remaining opportunities are low-urgency hardening (TLS-RPT, BIMI) and DKIM key hygiene.

Mail configuration

  • Mail servers (MX)d129714a.ess.barracudanetworks.com, d129714b.ess.barracudanetworks.com

    2 MX records — the domain can receive mail.

  • SPFv=spf1 ip4:38.106.254.44/32 include:spf.protection.outlook.com include:sendgrid.net include:asp-spf1.yardi.com include:asp-spf2.yardi.com include:autotask.net -all

    SPF present with a hard fail (-all) — strong protection against spoofing.

  • DMARC policyv=DMARC1; p=reject; fo=1; rua=mailto:rua+sterlingbay.com@dmarc.barracudanetworks.com; ruf=mailto:ruf+sterlingbay.com@dmarc.barracudanetworks.com

    DMARC policy is p=reject — strongest setting, spoofed mail is rejected.

  • DKIMselector1._domainkey, k2._domainkey, s1._domainkey, s2._domainkey

    DKIM signing keys found (selectors: selector1, k2, s1, s2).

  • MTA-STS

    No MTA-STS policy — optional, but it enforces encryption for mail delivery.

  • SMTP serverBarracuda

    Primary mail server responded (Barracuda).

Recommended improvements

  • Add an MTA-STS policy to enforce TLS for inbound deliveryLow

    MTA-STS is the only failing check — inbound delivery to your Barracuda ESS gateways currently relies on opportunistic STARTTLS with no enforcement.

    → Publish TXT _mta-sts.sterlingbay.com with "v=STSv1; id=<YYYYMMDD>;" and serve https://mta-sts.sterlingbay.com/.well-known/mta-sts.txt listing "mx: d129714a.ess.barracudanetworks.com" and "mx: d129714b.ess.barracudanetworks.com" — start in testing mode, then flip to "mode: enforce" once your web PKI is verified.

    20%

    impact

  • Add a TLS-RPT record to monitor failed TLS deliveriesLow

    Without TLS reporting you cannot see which remote servers fail TLS to your gateways or whether MTA-STS is actually being honored.

    → Add TXT _smtp._tls.sterlingbay.com with "v=TLSRPTv1; rua=mailto:rua+sterlingbay.com@dmarc.barracudanetworks.com;" to reuse the DMARC reporting address you already aggregate at Barracuda.

    15%

    impact

  • Verify active DKIM selectors and rotate signing keysLow

    Four selectors (selector1, k2, s1, s2) are published — likely one per sender (Microsoft 365, SendGrid, Yardi, Autotask) — and any stale one silently widens your trust surface.

    → Confirm which of selector1, k2, s1, s2 map to live senders in your SPF includes, remove selectors no longer used, and rotate the remaining keys on a regular schedule.

    10%

    impact

  • Publish BIMI to show your brand logo next to verified emailLow

    With SPF -all and DMARC p=reject already enforced, BIMI is a low-risk way to improve brand recognition and engagement in supporting inboxes.

    → Publish TXT default._bimi.sterlingbay.com with "v=BIMI1; l=https://www.sterlingbay.com/logo.svg;" and host an SVG-branded logo, signed by a VMC, at that HTTPS URL.

    10%

    impact

Auto-rated from DNS & SMTP records · improvements suggested by AI

Loaded Resources (85 requests · sorted by load time)

ResourceSizeTimeStatus
Ccdnjs.cloudflare.com/ajax/libs/gsap/3.12.0/gsap.min.js?ver=3.12.0
69.8KB
178ms
200
Ssterlingbay.com/wp-content/plugins/akismet/_inc/akismet-frontend.js?ver=17907649
11.9KB
176ms
200
Ccdnjs.cloudflare.com/ajax/libs/gsap/3.12.0/ScrollTrigger.min.js?ver=3.12.0
41.4KB
170ms
200
Pplayer.vimeo.com/api/player.js?ver=2.16.2
—
156ms
200
Gwww.google.com/recaptcha/enterprise/anchor?ar=1&k=6LcwqpQtAAAAAMg3RJapyPVgrmYzyc
—
127ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/assets/css/dist/gravity-forms-or
—
124ms
200
Gwww.google.com/recaptcha/enterprise.js?render=6LcwqpQtAAAAAMg3RJapyPVgrmYzycscDb
—
72ms
200
Gwww.googletagmanager.com/gtm.js?id=GTM-5HCFTV5T
—
71ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/social-x-twitter.svg
414B
70ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-onDark.s
312B
70ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/js/jquery.json.min.js?ver=3.0.2
1.8KB
70ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/assets/js/dist/vendor-theme.min.
75.4KB
70ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_content/evolution/home/state-of-t
258.0KB
69ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-vimeo.svg
486B
69ms
200
Ssterlingbay.com/wp-content/plugins/gravityformsrecaptcha/js/frontend.min.js?ver=
6.5KB
69ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-facebook.svg
370B
68ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/js/placeholders.jquery.min.js?ve
4.5KB
68ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/js/gravityforms.min.js?ver=3.0.2
41.1KB
68ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/sterlingbay.js?ver=2.1
34.6KB
67ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/assets/js/dist/utils.min.js?ver=
58.9KB
67ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/images/grfx-button-arrow-orange.sv
389B
66ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/assets/js/dist/scripts-theme.min
63.5KB
66ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-linkedin.svg
363B
65ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/validate/validate.min.
23.9KB
65ms
200
Ssterlingbay.com/wp-includes/js/dist/dom-ready.min.js?ver=a06281ae5cf5500e9317
818B
64ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/assets/scrollLock.js?v
794B
63ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/magnific.js?ver=2.1.18
19.7KB
63ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/contact.js?ver=2.1.18
7.9KB
63ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/validate/methods.min.j
22.1KB
63ms
200
Ssterlingbay.com/wp-includes/js/dist/hooks.min.js?ver=7496969728ca0f95732d
4.9KB
63ms
200
Ssterlingbay.com/wp-includes/js/dist/i18n.min.js?ver=781d11515ad3d91786ec
5.6KB
63ms
200
Ssterlingbay.com/wp-includes/js/dist/a11y.min.js?ver=af934e5259bc51b8718e
2.4KB
63ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-instagram.svg
789B
60ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/assets/slick.min.js?ve
42.8KB
59ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/assets/splide.min.js?v
29.1KB
59ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/assets/aos.js?ver=2.3.
13.9KB
58ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/assets/jquery.nice-sel
2.9KB
58ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/assets/rellax.min.js?v
6.9KB
57ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/accessible-accordion/a
4.6KB
57ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/lazy/lazy.av.min.js?ve
1002B
56ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/accessible-tabs/tabs.j
4.3KB
56ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_content/evolution/home/home-slide
376.1KB
53ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_scripts/js/lazy/lazy.min.js?ver=1
4.9KB
45ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-submit.s
207B
34ms
200
Gwww.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js
828.4KB
34ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-nav-exit.svg
230B
33ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/.fonts/helvetica_neue_lt_75_bold-w
19.8KB
32ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/.fonts/helvetica_neue_lt_65_medium
19.3KB
30ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/fonts/helvetica_neue_lt_55_roman-w
12.9KB
29ms
200
Ssterlingbay.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1
85.5KB
24ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/assets/css/dist/gravity-forms-th
531.4KB
24ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/evolution/sb-burger.svg
791B
23ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_css/fontawesome.css?ver=2.1.18
56.0KB
22ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/assets/css/dist/gravity-forms-th
98.2KB
22ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/evolution/sb-close.svg
689B
22ms
200
Gwww.googletagmanager.com/gtag/js?id=G-QSSKR38Z96&cx=c&gtm=4e69s1
—
21ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_css/magnific.css?ver=2.1.18
5.0KB
20ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_content/evolution/home/property-h
198.8KB
20ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_content/evolution/home/home-slide
454.4KB
20ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_content/evolution/home/property-h
369.6KB
19ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_css/sterlingbay.min.css?ver=2.1.1
279.2KB
17ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_css/assets/aos.css?ver=2.3.1
25.4KB
17ms
200
Ssterlingbay.com/wp-content/plugins/gravityforms/assets/css/dist/gravity-forms-th
2.4KB
17ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_content/evolution/home/home-slide
388.8KB
17ms
200
Rregion1.google-analytics.com/g/collect?v=2&tid=G-QSSKR38Z96&gtm=45je69s1v9185282
—
17ms
204
Ssterlingbay.com/wp-content/themes/sterlingbay/style.css?ver=2.1.18
1.2KB
15ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_css/assets/splide-core.min.css?ve
1.9KB
14ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_css/animated.css?ver=2.1.18
60.8KB
14ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_content/evolution/home/property-h
250.0KB
14ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_css/assets/slick.min.css?ver=5.2.
1.3KB
13ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-onDark.s
312B
10ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-onDark.s
312B
9ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-onDark.s
312B
9ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-onDark.s
312B
8ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-submit.s
207B
7ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/images/grfx-button-arrow-orange.sv
389B
7ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-vimeo.svg
486B
7ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-facebook.svg
370B
7ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/social-x-twitter.svg
414B
7ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-button-arrow-onDark.s
312B
7ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/evolution/sb-close.svg
689B
6ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-nav-exit.svg
230B
6ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-linkedin.svg
363B
6ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/svg/grfx-social-instagram.svg
789B
6ms
200
Ssterlingbay.com/wp-content/themes/sterlingbay/_ui/evolution/sb-burger.svg
791B
5ms
200

Scan History (1 scans)

Page load time

696ms

TTFB

215ms
DateTTFBDOMLoadRequestsSizeErrorsScripts
Sep 30, 12:48 PM215ms430ms696ms854943KB02AI

Embed a badge

Pick what to show — your detected tech stack, the social-trend valuation, or both.

Badge style

Brand · detected technologies.

Preview
badge preview
HTML embed
<a href="https://madewith.tech/s/sterlingbay.com"><img src="https://madewith.tech/s/sterlingbay.com/badge.svg" alt="sterlingbay.com on MadeWithTech" /></a>
Markdown
[![sterlingbay.com on MadeWithTech](https://madewith.tech/s/sterlingbay.com/badge.svg)](https://madewith.tech/s/sterlingbay.com)
Share link
https://madewith.tech/s/sterlingbay.com
sterlingbay.com is built with Google Analytics, Google Recaptcha, Google Tag Manager · MadeWithTech