Website review, no card needed

dysarts.com logo

dysarts.com website review

Visit site (opens in a new tab)Reviewed 20 October 202638 issues · 86 checks

This review found 38 issues worth fixing on dysarts.com, 12 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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
4.0 s3.0 sMay 2Oct 173.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.1 s
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.7 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
64 ms62 msMay 2Oct 1763 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202662 ms
May 9, 202662 ms
May 16, 202663 ms
May 23, 202662 ms
May 30, 202663 ms
Jun 6, 202662 ms
Jun 13, 202662 ms
Jun 20, 202662 ms
Jun 27, 202662 ms
Jul 4, 202663 ms
Jul 11, 202662 ms
Jul 18, 202662 ms
Jul 25, 202662 ms
Aug 1, 202662 ms
Aug 8, 202663 ms
Aug 15, 202664 ms
Aug 22, 202663 ms
Aug 29, 202662 ms
Sep 5, 202662 ms
Sep 12, 202662 ms
Sep 19, 202662 ms
Sep 26, 202663 ms
Oct 3, 202663 ms
Oct 10, 202663 ms
Oct 17, 202663 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 dysarts.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix64
  • Render-blocking requests

    2.2 s

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

  • Improve image delivery

    1.1 s · 466 KiB

    15 images could be 466 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 1.6 MB and 886 ms of main-thread time.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    736 KiB

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

  • Google Tag Manager adds 430 ms

    430 ms

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

  • Google CDN adds 404 ms

    404 ms

    Google CDN costs a phone 404 ms of main-thread work and 733 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.

  • Reduce unused CSS

    150 ms · 59 KiB

    About 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Use efficient cache lifetimes

    10 KiB

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

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

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dysart's Restaurant & Truck Stop I-95 Exit 180 530 Coldbroo…”.

  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Total Blocking Time: 284 ms

    284 ms

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

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

3 checks passed
  • Real-user INP: 62 ms

    62 ms

    Real visitors wait 62 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.

  • Cumulative Layout Shift: 0.045

    0.045

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 66 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 66 requests on a phone: scripts 1.5 MB (26), images 862 KiB (16) and other files 349 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (98 KiB) 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.

  • 3 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.84 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8390
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 9284
  • Title is short (15 characters)

    Your title is only 15 characters: “Home | Dysart's”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Home”, “Keeping Maine Warm” and “Home Heat Customers”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links with vague text

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

  • 31 internal links, 9 external

    The homepage links to 31 pages on dysarts.com and 9 external pages.

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Keeping Maine Warm Order Oil Online Home Heat Customers Get Started Today Pay My Oil Bill Today Home Heat Customers PAY…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, Person 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.dysarts.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.dysarts.com/ourstory/buttery-flakey-blog and https://www.dysarts.com/dysarts-fleet-card have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages with very little text

    https://www.dysarts.com/employment, https://www.dysarts.com/contact-us, https://www.dysarts.com/preorders, https://www.dysarts.com/orderonline and https://www.dysarts.com/marina 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 18 found) and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 165 words

    The homepage has only about 165 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Come Join our Team!” and “Contact Us”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Come Join our Team!”, “Contact Us” and “Order Fuel”.

  • Analytics in place

    Analytics detected: Google Analytics and Matomo.

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (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.

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

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 dysarts.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
E-commerce
WooCommerce
Analytics
Google Analytics | Matomo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on dysarts.com, including 18 speed issues, 4 SEO issues and 4 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