Website review, no card needed

flotekind.com logo

flotekind.com website review

Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 80 checks

This review found 33 issues worth fixing on flotekind.com, 12 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
3.7 s2.1 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.4 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.3 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.3 s
Aug 1, 20263.4 s
Aug 8, 20263.1 s
Aug 15, 20263.3 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20262.9 s
Sep 26, 20262.7 s
Oct 3, 20262.4 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
114 ms63 msMay 9Oct 2479 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026103 ms
May 16, 2026108 ms
May 23, 202699 ms
May 30, 202698 ms
Jun 6, 202699 ms
Jun 13, 202682 ms
Jun 20, 202678 ms
Jun 27, 202684 ms
Aug 8, 202684 ms
Aug 15, 202684 ms
Aug 22, 202684 ms
Aug 29, 202677 ms
Sep 5, 202687 ms
Sep 12, 202694 ms
Sep 19, 202695 ms
Sep 26, 202686 ms
Oct 3, 202670 ms
Oct 10, 202669 ms
Oct 17, 202670 ms
Oct 24, 202679 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 flotekind.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. flotekind.com at 0.4 s0.4 s
  2. flotekind.com at 0.8 s0.8 s
  3. flotekind.com at 1.3 s1.3 s
  4. flotekind.com at 1.7 s1.7 s
  5. flotekind.com at 2.1 s2.1 s
  6. flotekind.com at 2.5 s2.5 s
  7. flotekind.com at 3.0 s3.0 s
  8. flotekind.com at 3.4 s3.4 s

Speed

10 to fix56
  • Reduce unused JavaScript

    4.7 s · 566 KiB

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

  • Render-blocking requests

    2.3 s

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

  • Use efficient cache lifetimes

    1.8 s · 486 KiB

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

  • Mobile performance score: 56

    56/100

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

  • Reduce unused CSS

    750 ms · 131 KiB

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

  • 7 third-party services on the page

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

  • Improve image delivery

    350 ms · 107 KiB

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

  • Google CDN adds 336 ms

    336 ms

    Google CDN costs a phone 336 ms of main-thread work and 734 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 adds 199 ms

    199 ms

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

  • Main-thread work: 2.1 s

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

  • Legacy JavaScript

    150 ms · 7 KiB

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

  • 6 long tasks on the main thread

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

1 checks passed
  • Server response: 23 ms

    23 ms

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

Core Web Vitals

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

  • First Contentful Paint: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 14.8 s

    14.8 s

    Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To provide the best experiences, we use technologies like c…”.

  • 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: 9.9 s

    9.9 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 948 ms

    948 ms

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

6 checks passed
  • 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.01

    0.01

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

  • Tap response (INP) got 29% faster for real visitors

    -29%

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

  • Largest content (LCP) got 29% faster for real visitors

    -29%

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

  • Total Blocking Time: 68 ms

    68 ms

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

  • Cumulative Layout Shift: 0.018

    0.018

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

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 91 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 91 requests on a phone: scripts 1.4 MB (37), images 624 KiB (15) and other files 353 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (46 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.

  • 1 image below the first screen load straight away

    1 image further down the page (46 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.79 g

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

4 to fixGoogle 9294
  • 1 text element with low contrast

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

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “Flotek Industries - Leading Chemistry & Data Analytics for Oil and Gas Efficiency”.

  • 4 H1 headlines

    There are 4 <h1> headlines (“World Class Chemistry and Data Analytics Technolo…”, “ENERGY CHEMISTRY TECHNOLOGIES” and “DATA ANALYTICS”). One clear main headline is easier for people and search engines.

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

  • 18 internal links, 27 external

    The homepage links to 18 pages on flotekind.com and 27 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Discover Flotek's innovative chemistry solutions and data analytics, designed to enhance the performance and economics …”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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 and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

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

    Your Organization JSON-LD is missing 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.flotekind.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 (716 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

    5 of 22 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: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 435 words of copy

    The homepage carries about 435 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Stock Quote & Chart”, “Contact” and “DOWNLOAD OUR BROCHURE”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

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 flotekind.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
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on flotekind.com, including 18 speed issues, 3 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