Website review, no card needed

sunlandasphalt.com logo

sunlandasphalt.com website review

Visit site (opens in a new tab)Reviewed 27 October 202640 issues · 88 checks

This review found 40 issues worth fixing on sunlandasphalt.com, 19 of them high impact, across 88 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.7 s4.7 sMay 9Oct 245.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.1 s
May 23, 20265.2 s
May 30, 20265.0 s
Jun 6, 20265.4 s
Jun 13, 20265.4 s
Jun 20, 20266.4 s
Jun 27, 20266.5 s
Jul 4, 20266.1 s
Jul 11, 20266.3 s
Jul 18, 20265.9 s
Jul 25, 20265.7 s
Aug 1, 20265.7 s
Aug 8, 20265.1 s
Aug 15, 20265.1 s
Aug 22, 20265.0 s
Aug 29, 20264.9 s
Sep 5, 20265.7 s
Sep 12, 20265.8 s
Sep 19, 20266.2 s
Sep 26, 20266.3 s
Oct 3, 20266.1 s
Oct 10, 20266.1 s
Oct 17, 20265.6 s
Oct 24, 20265.4 s
Real-visitor tap response (INP)75th percentile, phones
93 ms59 msMay 9Oct 2486 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202676 ms
May 16, 202675 ms
May 23, 202671 ms
May 30, 202667 ms
Jun 6, 202663 ms
Jun 13, 202665 ms
Jun 20, 202669 ms
Jun 27, 202671 ms
Jul 4, 202669 ms
Jul 11, 202663 ms
Jul 18, 202663 ms
Jul 25, 202664 ms
Aug 1, 202669 ms
Aug 8, 202670 ms
Aug 15, 202670 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202672 ms
Sep 12, 202677 ms
Sep 19, 202679 ms
Sep 26, 202682 ms
Oct 3, 202689 ms
Oct 10, 202688 ms
Oct 17, 202687 ms
Oct 24, 202686 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 sunlandasphalt.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sunlandasphalt.com at 1.0 s1.0 s
  2. sunlandasphalt.com at 2.0 s2.0 s
  3. sunlandasphalt.com at 3.0 s3.0 s
  4. sunlandasphalt.com at 4.0 s4.0 s
  5. sunlandasphalt.com at 5.0 s5.0 s
  6. sunlandasphalt.com at 6.0 s6.0 s
  7. sunlandasphalt.com at 7.0 s7.0 s
  8. sunlandasphalt.com at 8.0 s8.0 s

Speed

12 to fix45
  • Reduce unused JavaScript

    8.0 s · 1.6 MB

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

  • Render-blocking requests

    8.4 s

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

  • Improve image delivery

    2.1 s · 2.9 MB

    9 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

  • Reduce unused CSS

    4.0 s · 741 KiB

    About 741 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.0 s faster on a phone.

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 4.1 s

    A phone's processor spends 4.1 s on main-thread work while loading, 2.0 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 (Google Tag Manager, Vimeo and Accessibe Accessibility Overlay and others), adding 7.6 MB and 597 ms of main-thread time.

  • Vimeo adds 148 ms

    148 ms

    Vimeo costs a phone 148 ms of main-thread work and 6.9 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.

  • Font display

    650 ms

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

  • Google Tag Manager adds 324 ms

    324 ms

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

  • Minify JavaScript

    300 ms · 42 KiB

    42 KiB could be saved by minifying JavaScript.

  • 1,536 HTML elements

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

  • Document request latency

    191 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 11 long tasks on the main thread

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

  • Use efficient cache lifetimes

    56 KiB

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

  • Minify CSS

    10 ms · 19 KiB

    19 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    10 KiB

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

  • 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: 244 ms

    244 ms

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

Core Web Vitals

10 to fix0
  • 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: 8.0 s

    8.0 s

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

  • Real-user CLS: 0.51

    0.51

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

  • Real-user FCP: 4.5 s

    4.5 s

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

  • Real-user TTFB: 2.5 s

    2.5 s

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

  • First Contentful Paint: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 43.9 s

    43.9 s

    Your largest element takes 43.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ABOUT US SERVICES PROJECTS SUNLAND COMPANIES BLOG CAREER CO…”.

  • Speed Index: 20.1 s

    20.1 s

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

  • Time to Interactive: 51.2 s

    51.2 s

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

  • Total Blocking Time: 401 ms

    401 ms

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

1 checks passed
  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

4 to fix25
  • Page weight: 16.5 MB in 156 requests

    16.5 MB

    Your homepage downloads 16.5 MB in 156 requests on a phone: other files 6.4 MB (30), images 5.7 MB (16) and scripts 2.8 MB (49). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    494 KiB

    2 images are downloaded at several times the size a phone draws them, for example APEX-Concrete-Pour-11-scaled.jpg at 2,560 px wide, shown at 344 px. Resized copies would save about 494 KiB.

  • 10 images in older formats

    10 images (4.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images below the first screen load straight away

    2 images further down the page (161 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.7 g of CO₂ per visit

    4.68 g

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

Accessibility

2 to fixGoogle 9798
  • All page content should be contained by landmarks (2 elements)

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is short (14 characters)

    Your title is only 14 characters: “HOME - Sunland”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 51 internal links, 11 external

    The homepage links to 51 pages on sunlandasphalt.com and 11 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “From commercial to government projects, Sunland Asphalt provides reliable asphalt paving, maintenance, and repair servi…”.

  • One H1 headline

    Your main headline reads: “RELIABLE ASPHALT & PAVEMENT”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://sunlandasphalt.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://sunlandasphalt.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 (1,300 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://sunlandasphalt.com/market-sector/government-agencies, https://sunlandasphalt.com/market-sector/commercial-retail-mixed-use, https://sunlandasphalt.com/market-sector/residential-communities, https://sunlandasphalt.com/market-sector/education and https://sunlandasphalt.com/market-sector/hoa have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://sunlandasphalt.com/our-people, https://sunlandasphalt.com/market-sector/government-agencies, https://sunlandasphalt.com/market-sector/commercial-retail-mixed-use, https://sunlandasphalt.com/market-sector/residential-communities, https://sunlandasphalt.com/market-sector/education and https://sunlandasphalt.com/market-sector/hoa have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://sunlandasphalt.com/offices, https://sunlandasphalt.com/market-sector/education and https://sunlandasphalt.com/market-sector/hoa have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • 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

4 to fixGoogle 5883
  • 3 small tap targets

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

  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • 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

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 695 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST A QUOTE”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “CONTACT”, “Request a Quote” and “LEARN MORE ABOUT US”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 2 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 16 other companies contacted

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

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 sunlandasphalt.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
Hosting
Liquid Web

Company

Employees
1,143

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on sunlandasphalt.com, including 22 speed issues, 2 SEO issues and 2 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