flow-rite.com website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (Wistia, Google Tag Manager and Facebook and others), adding 1.3 MB and 1.3 s of main-thread time.

Wistia costs a phone 574 ms of main-thread work and 453 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 Tag Manager costs a phone 438 ms of main-thread work and 514 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 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

42 KiB could be saved by minifying JavaScript.

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.

2 KiB could be saved by minifying CSS.

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.8 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 27.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “U.S.A. Made Innovations, Industry-Leading Solutions Total B…”.

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

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

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

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

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

Your homepage downloads 5.7 MB in 341 requests on a phone: scripts 2.5 MB (167), images 2.2 MB (25) and stylesheets 426 KiB (101). Under 2 MB keeps phones on slow connections fast.

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

6 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “WebSite: missing name”.

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

The homepage links to 187 pages on flow-rite.com and 9 external pages.

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.

/, /marine and /livewell-and-baitwell-systems-guide all use the title “Fluid Control Systems & Products - Flow-Rite”. Search engines can't tell which page to show for a search, so each competes with the others.

/shop, /application/marine/qwik-lok-marine-plumbing-system and /marine/store have no meta description, so Google writes the search snippet from whatever text it finds.

/marine and /livewell-and-baitwell-systems-guide use the same meta description. A description written for each page earns more clicks.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example /marine/store/filters/product_cat/livewell, whose canonical is /marine/store. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/marine/store/filters/product_cat/livewell, /marine/store/filters/product_cat/remote-drain-plug, /marine/store/filters/product_cat/valves, /marine/store/filters/product_cat/pumps-timers, /marine/store and /marine/store/filters/product_cat/1-1-2-fittings and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/livewell-and-baitwell-systems-guide, /marine/store/filters/product_cat/remote-drain-plug, /marine/store/filters/product_cat/pumps-timers, /marine/store, /marine/store/filters/product_cat/3-4-fittings and /marine/store/filters/product_cat/actuators-cables took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187279067&tm=gtm002&Ver=2&mid=63766bfd-8327-400c-9b6f-de5309775774&bo=1&sid=441dd450cee511f1a24ea39ae00858ae&vid=441dfd00cee511f1afe1791ee0a123f2&vids=1&msclkid=N&gtm_.

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

1 error was logged to the browser console while the page loaded, for example “window.searchAndFilter.frontend.queries.on is not a function”.

Large scripts ship without source maps.

1 image is served at too low a resolution for sharp phone screens.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

X-XSS-Protection is set to “1”; 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.

flow-rite.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.

flow-rite.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.

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,246 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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.

Opening the homepage sets 14 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.