fpl.com website review

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

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

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

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

356 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 2.3 s faster on a phone.

416 KiB could be saved by minifying JavaScript.

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

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

8 third-party services load with your homepage (Adobe Tag Manager, sprinklr.com and AppDynamics and others), adding 817 KiB and 880 ms of main-thread time.

24 images could be 653 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

67 KiB could be saved by minifying CSS.

Adobe Tag Manager costs a phone 401 ms of main-thread work and 246 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.

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

sprinklr.com costs a phone 225 ms of main-thread work and 373 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 31.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our websites use technologies (e.g., cookies, pixels, and s…”.

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

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

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

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

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

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

Your homepage downloads 5.8 MB in 157 requests on a phone: scripts 3.7 MB (54), images 1.3 MB (41) and stylesheets 508 KiB (14). Under 2 MB keeps phones on slow connections fast.

9 images (934 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.

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

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

Some list items are not inside a list.

2 elements have a tabindex above 0, which scrambles the keyboard order.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 14 characters: “FPL | Homepage”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“We’re here to help” and “Every day is a storm prep day”). One clear main headline is easier for people and search engines.

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

Your meta description is 213 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

4 links have no real href, so search engines can't follow them.

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

The homepage links to 51 pages on fpl.com and 15 external pages.

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.

There is no /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.

/powertracker has no <title>, so Google invents the link text in results.

/powertracker is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/assistance.html, /help/saving-steps.html and /powertracker have no meta description, so Google writes the search snippet from whatever text it finds.

/support/contact.html and /powertracker have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 errors were logged to the browser console while the page loaded, for example “Error: multipleDefine”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

6 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

2 links go through two or more redirects, for example http://www.facebook.com/fplconnect.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fpl.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

fpl.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 439 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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.

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