Website review, no card needed

SmartSites logo

smartsites.com website review

Visit site (opens in a new tab)Reviewed 28 October 202617 issues · 79 checks

This review found 17 issues worth fixing on smartsites.com, 5 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for SmartSites

  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
4.6 s2.1 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.6 s
Jun 6, 20263.7 s
Jun 13, 20263.6 s
Jun 20, 20263.5 s
Jun 27, 20263.8 s
Jul 4, 20264.0 s
Jul 11, 20264.2 s
Jul 18, 20264.3 s
Jul 25, 20264.2 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20263.8 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20264.0 s
Sep 12, 20264.1 s
Sep 19, 20264.1 s
Sep 26, 20264.2 s
Oct 3, 20263.3 s
Oct 10, 20262.9 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
200 ms121 msMay 9Oct 24140 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026167 ms
May 16, 2026177 ms
May 23, 2026174 ms
May 30, 2026169 ms
Jun 6, 2026161 ms
Jun 13, 2026158 ms
Jun 20, 2026153 ms
Jun 27, 2026169 ms
Jul 4, 2026186 ms
Jul 11, 2026191 ms
Jul 18, 2026186 ms
Jul 25, 2026166 ms
Aug 1, 2026151 ms
Aug 8, 2026144 ms
Aug 15, 2026130 ms
Aug 22, 2026140 ms
Aug 29, 2026136 ms
Sep 5, 2026156 ms
Sep 12, 2026156 ms
Sep 19, 2026156 ms
Sep 26, 2026161 ms
Oct 3, 2026133 ms
Oct 10, 2026136 ms
Oct 17, 2026144 ms
Oct 24, 2026140 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 smartsites.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. smartsites.com at 0.4 s0.4 s
  2. smartsites.com at 0.8 s0.8 s
  3. smartsites.com at 1.1 s1.1 s
  4. smartsites.com at 1.5 s1.5 s
  5. smartsites.com at 1.9 s1.9 s
  6. smartsites.com at 2.3 s2.3 s
  7. smartsites.com at 2.6 s2.6 s
  8. smartsites.com at 3.0 s3.0 s

Speed

7 to fix80
  • 3,536 HTML elements

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

  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Hubspot and Bing Ads and others), adding 509 KiB and 691 ms of main-thread time.

  • Render-blocking requests

    700 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

  • Google Tag Manager adds 491 ms

    491 ms

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

  • 11 long tasks on the main thread

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

  • Main-thread work: 2.9 s

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

  • Reduce unused JavaScript

    232 KiB

    About 232 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    93 KiB

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

  • Improve image delivery

    13 KiB

    1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

6 to fix67
  • 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.

  • Time to Interactive: 8.8 s

    8.8 s

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

  • Total Blocking Time: 768 ms

    768 ms

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

8 checks passed
  • Real-user INP: 177 ms

    177 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

  • Largest content (LCP) got 32% faster for real visitors

    -32%

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

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “15 years. Thousands of success stories. Billions of data po…”.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.32 g of CO₂e: 38.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed
  • Page weight: 1.1 MB in 71 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 71 requests on a phone: scripts 666 KiB (21), images 301 KiB (28) and HTML 66 KiB (1). That is a lean page.

  • 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

1 to fixGoogle 10099
  • 57 links without text

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

2 checks passed
  • Every image has alt text

    All 310 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 259 internal links, 7 external

    The homepage links to 259 pages on smartsites.com and 7 external pages.

8 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “SmartSites is a digital marketing agency rated 4.9 from 2,100+ client reviews: SEO, PPC, social media, email and SMS, e…”.

  • One H1 headline

    Your main headline reads: “The Modern Digital Marketing Agency Built to Outperform”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Digital Marketing Agency | 2,100+ Reviews | SmartSites”.

  • Canonical URL set

    The canonical URL is https://www.smartsites.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, ProfessionalService, 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://www.smartsites.com/sitemap_index.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,881 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.smartsites.com/llms.txt (13 KiB, 74 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 1 page slow to respond

    https://www.smartsites.com/organic-seo took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10084
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=18005172&tm=gtm002&Ver=2&mid=5e59c6ce-65fa-4c62-99a0-6a33683e5f1f&bo=1&sid=2ab938f0d31d11f1a413ab3518f2abd7&vid=2ab94180d31d11f1b4984b2737b2317d&vids=1&msclkid=N&pi=91.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    46 of 46 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • A 11-field form

    Your longest form asks for 11 fields (3 required). Every extra field lowers completion.

  • 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 2,687 words of copy

    The homepage carries about 2,687 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get Started”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact Us”, “Get a Free Proposal” and “Call 201-870-6000”.

  • Social proof on the page

    Social proof on the homepage: 43 testimonial or review blocks, 21 customer or partner logos, a star rating and 29 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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 Microsoft Ads (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.

  • 11 cookies set on arrival

    11

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 smartsites.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 Tag Manager
Hosting
Is As

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on smartsites.com, including 13 speed issues, 1 SEO issue and 1 conversion gap. 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