Website review, no card needed

ferndalemi.gov logo

ferndalemi.gov website review

Visit site (opens in a new tab)Reviewed 23 October 202636 issues · 81 checks

This review found 36 issues worth fixing on ferndalemi.gov, 15 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
1.4 s796 msMay 2Oct 17902 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026885 ms
May 9, 2026888 ms
May 16, 2026943 ms
May 23, 2026935 ms
May 30, 2026954 ms
Jun 6, 2026931 ms
Jun 13, 2026969 ms
Jun 20, 20261.0 s
Jun 27, 20261.1 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.1 s
Jul 25, 20261.3 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.0 s
Sep 12, 2026860 ms
Sep 19, 2026927 ms
Sep 26, 2026990 ms
Oct 3, 20261.0 s
Oct 10, 2026927 ms
Oct 17, 2026902 ms
Real-visitor tap response (INP)75th percentile, phones
95 ms66 msMay 2Oct 1780 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202671 ms
May 9, 202670 ms
May 16, 202670 ms
May 23, 202672 ms
May 30, 202669 ms
Jun 6, 202678 ms
Jun 13, 202678 ms
Jun 20, 202677 ms
Jun 27, 202680 ms
Jul 4, 202687 ms
Jul 11, 202692 ms
Jul 18, 202692 ms
Jul 25, 202692 ms
Aug 1, 202688 ms
Aug 8, 202688 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202683 ms
Sep 12, 202683 ms
Sep 19, 202683 ms
Sep 26, 202683 ms
Oct 3, 202685 ms
Oct 10, 202679 ms
Oct 17, 202680 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 ferndalemi.gov (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ferndalemi.gov at 0.5 s0.5 s
  2. ferndalemi.gov at 1.0 s1.0 s
  3. ferndalemi.gov at 1.5 s1.5 s
  4. ferndalemi.gov at 2.1 s2.1 s
  5. ferndalemi.gov at 2.6 s2.6 s
  6. ferndalemi.gov at 3.1 s3.1 s
  7. ferndalemi.gov at 3.6 s3.6 s
  8. ferndalemi.gov at 4.1 s4.1 s

Speed

6 to fix57
  • Improve image delivery

    2.5 s · 863 KiB

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

  • Render-blocking requests

    2.7 s

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

  • Reduce unused JavaScript

    2.3 s · 385 KiB

    About 385 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Use efficient cache lifetimes

    1.5 s · 331 KiB

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

  • Reduce unused CSS

    1.1 s · 211 KiB

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

  • Mobile performance score: 57

    57/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Accessibe Accessibility Overlay, Google Tag Manager and Mailchimp and others), adding 749 KiB and 421 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 504 ms 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

5 to fix100
  • First Contentful Paint: 8.5 s

    8.5 s

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

  • Largest Contentful Paint: 13.4 s

    13.4 s

    Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 13.4 s

    13.4 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • 24 images without width and height

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

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user INP: 79 ms

    79 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 331 ms

    331 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 11 ms

    11 ms

    Scripts block the page for only 11 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 2.6 MB in 58 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 58 requests on a phone: images 1.2 MB (22), scripts 806 KiB (11) and fonts 327 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    356 KiB

    6 images are downloaded at several times the size a phone draws them, for example HAN_8380 - Edited.webp at 1,500 px wide, shown at 390 px. Resized copies would save about 356 KiB.

  • 4 images below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.74 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8191
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 31 text elements with low contrast

    31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 13 images without alt text

    13 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 13 links without text

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 8380
  • Title is short (15 characters)

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 61 internal links, 21 external

    The homepage links to 61 pages on ferndalemi.gov and 21 external pages.

4 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Welcome to the City of Ferndale, Michigan. Visit us at www.ferndalemi.gov to learn more about our incredible people, pr…”.

  • One H1 headline

    Your main headline reads: “Welcome to Ferndale!”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://ferndalemi.gov/sitemap.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://ferndalemi.gov/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 (559 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix57
  • 1 linked page is broken

    Your homepage links to https://ferndalemi.gov/government/services/garbage-recycling-and-waste-removal, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 7 pages share 2 titles

    / and https://ferndalemi.gov/permit all use the title “Home - Ferndale”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://ferndalemi.gov/residents, https://ferndalemi.gov/visitors, https://ferndalemi.gov/business, https://ferndalemi.gov/calendar, https://ferndalemi.gov/news and https://ferndalemi.gov/contact and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://ferndalemi.gov/government, https://ferndalemi.gov/parking, https://ferndalemi.gov/Government/Services%20List/Pay%20Property%20Taxes, https://ferndalemi.gov/permit, https://ferndalemi.gov/government/city-meetings and https://ferndalemi.gov/Government/Services%20List/Ferndale%20Emergency%20Alerts use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://ferndalemi.gov/Resources/Water%20Bills and https://ferndalemi.gov/news/november-3--2026--general-election-information have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9685
  • 7 small tap targets

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

  • 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 404 ()”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

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

    The homepage carries about 569 words of visible text.

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “CONTACT”, “LEARN MORE” and “Final Water Bill Request”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 ferndalemi.gov, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Analytics
Google Analytics

Company

Founded
1918

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on ferndalemi.gov, including 11 speed issues, 5 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