Website review, no card needed

hydrite.com logo

hydrite.com website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 102 checks

This review found 31 issues worth fixing on hydrite.com, 7 of them high impact, across 102 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
2.5 s1.2 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.5 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
123 ms100 msMay 9Oct 24115 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026106 ms
May 16, 2026111 ms
May 23, 2026111 ms
May 30, 2026113 ms
Jun 6, 2026116 ms
Jun 13, 2026104 ms
Jun 20, 2026103 ms
Jun 27, 2026104 ms
Jul 4, 2026104 ms
Jul 11, 2026107 ms
Jul 18, 2026111 ms
Jul 25, 2026111 ms
Aug 1, 2026112 ms
Aug 8, 2026112 ms
Aug 15, 2026110 ms
Aug 22, 2026109 ms
Aug 29, 2026111 ms
Sep 5, 2026114 ms
Sep 12, 2026113 ms
Sep 19, 2026115 ms
Sep 26, 2026116 ms
Oct 3, 2026113 ms
Oct 10, 2026120 ms
Oct 17, 2026116 ms
Oct 24, 2026115 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 hydrite.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

hydrite.com does not allow embedding, so this is Google's rendering of the page.

Speed

6 to fix62
  • Render-blocking requests

    2.6 s

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

  • Improve image delivery

    6.6 MB

    10 images could be 6.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    850 ms · 114 KiB

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

  • Reduce unused JavaScript

    610 ms · 135 KiB

    About 135 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

  • Reduce unused CSS

    610 ms · 66 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, termly.io and Microsoft Hosted Libs and others), adding 747 KiB and 278 ms of main-thread time.

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 110 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).

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PROVIDING CREATIVE SOLUTIONS Hydrite, founded in 1929, is a…”.

  • Time to Interactive: 15.1 s

    15.1 s

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

  • Speed Index: 7.6 s

    7.6 s

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

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

    +52%

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 106 ms to 115 ms 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: 2.4 s

    2.4 s

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

  • Real-user INP: 95 ms

    95 ms

    Real visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 561 ms

    561 ms

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

  • Total Blocking Time: 113 ms

    113 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 8.9 MB in 54 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 54 requests on a phone: images 8.0 MB (11), scripts 473 KiB (24) and fonts 298 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    156 KiB

    1 image is downloaded at several times the size a phone draws it, for example cheese_platter.jpg at 640 px wide, shown at 82 px. Resized copies would save about 156 KiB.

  • 1 image in older formats

    1 image (183 KiB) is 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.

  • About 2.5 g of CO₂ per visit

    2.51 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.51 g of CO₂e: 301.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9696
  • 28 text elements with low contrast

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

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 8589
  • No structured data

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

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

  • 7 links with vague text

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

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 82 internal links, 7 external

    The homepage links to 82 pages on hydrite.com and 7 external pages.

6 checks passed
  • Meta description: 98 characters

    Your meta description is 98 characters: “Hydrite Chemical Co. is an integrated manufacturer and supplier of chemicals and related services.”.

  • One H1 headline

    Your main headline reads: “Providing Creative Solutions”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Chemical Manufacturing | Hydrite Chemical Co.”.

  • Canonical URL set

    The canonical URL is https://www.hydrite.com/home.htm.

  • 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://www.hydrite.com/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.

3 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 (676 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (7 KiB, 47 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 2 pages share a title

    / and /Hydrite_New.htm all use the title “Chemical Manufacturing | Hydrite Chemical Co.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /Hydrite_New.htm, whose canonical is /home.htm. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 52 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 10087
  • 4 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

2 to fix88
  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Content-Security-Policy

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

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

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

  • No security.txt

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

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (hydrite.com).

  • Valid certificate (72 days left)

    The certificate from Let's Encrypt · YR2 verifies for hydrite.com and is valid for another 72 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • http:// redirects to https

    http://hydrite.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 46 links work

    All 46 links checked from your homepage (40 internal, 6 external) answered without errors.

Domain and trust

  • No CAA record

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

3 checks passed
  • Domain is 30 years old

    30 years

    hydrite.com was registered in Feb 1996 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • DNSSEC is on

    hydrite.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

  • Registered until May 2029

    hydrite.com is registered until May 2029.

Content and conversion

3 to fix71
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 624 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Product Data or Safety Data Request”, “Contact Us” and “Request an SDS”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Email authentication

95
  • Email authentication score: 95/100

    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.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 ip4:52.240.155.145 ip4:52.240.137.71 ip4:192.254.115.42 ip4:192.254.115.210 ip4:167.89.62.142 ip4:35.80.141.6 ip…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1” and “k1”), so receivers can verify mail really came from you.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

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

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Titan CMS 7.5
Analytics
Google Tag Manager
Hosting
Azure

Hiring

Hiring
67 open roles
Teams
Field Sales (18), Production (15), Lab (8), Engineering (6)
Job board
greenhouse

Company

Employees
803

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on hydrite.com, including 12 speed issues, 4 SEO issues and 3 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