Website review, no card needed
fleetsheets.com website review
Visit site (opens in a new tab)Reviewed 6 November 202622 issues · 94 checks
This review found 22 issues worth fixing on fleetsheets.com, 7 of them high impact, across 94 checks. The most urgent: aRIA attributes must conform to valid values (1 element). Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
91A- #1,017 of 81,780 reviewed websitesbeats 98%
- #413 of 40,573 online storesbeats 98%
- #393 of 35,953 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 781 ms |
| May 23, 2026 | 779 ms |
| May 30, 2026 | 772 ms |
| Jun 6, 2026 | 729 ms |
| Jun 13, 2026 | 697 ms |
| Jun 20, 2026 | 670 ms |
| Jun 27, 2026 | 629 ms |
| Jul 4, 2026 | 656 ms |
| Jul 11, 2026 | 677 ms |
| Jul 18, 2026 | 664 ms |
| Jul 25, 2026 | 692 ms |
| Aug 1, 2026 | 651 ms |
| Aug 8, 2026 | 616 ms |
| Aug 15, 2026 | 640 ms |
| Aug 22, 2026 | 671 ms |
| Aug 29, 2026 | 683 ms |
| Sep 5, 2026 | 703 ms |
| Sep 12, 2026 | 687 ms |
| Sep 19, 2026 | 662 ms |
| Sep 26, 2026 | 657 ms |
| Oct 3, 2026 | 646 ms |
| Oct 10, 2026 | 621 ms |
| Oct 17, 2026 | 611 ms |
| Oct 24, 2026 | 612 ms |
| Oct 31, 2026 | 607 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 20, 2026 | 69 ms |
| Jun 27, 2026 | 68 ms |
| Jul 18, 2026 | 66 ms |
| Jul 25, 2026 | 66 ms |
| Aug 1, 2026 | 63 ms |
| Aug 8, 2026 | 64 ms |
| Aug 15, 2026 | 64 ms |
| Aug 22, 2026 | 63 ms |
| Aug 29, 2026 | 63 ms |
| Sep 5, 2026 | 62 ms |
| Sep 12, 2026 | 62 ms |
| Sep 19, 2026 | 62 ms |
| Sep 26, 2026 | 62 ms |
| Oct 10, 2026 | 63 ms |
| Oct 17, 2026 | 62 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
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.7 s
2.1 s
2.6 s
3.0 s
3.4 s
fleetsheets.com does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Improve image delivery
198 KiB5 images could be 198 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 90 ms. During a long task the page ignores taps.
Reduce unused JavaScript
52 KiBAbout 52 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
30 KiBAbout 30 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
7 KiB4 files are served with short cache lifetimes, so returning visitors download them again (7 KiB).
3 third-party services on the page
3 third-party services load with your homepage (ahrefs.com, Shopify and shop.app), adding 13 KiB and 5 ms of main-thread time.
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.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 80 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 69 ms to 62 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 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.6 s
0.6 sReal visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 0.5 s
0.5 sReal visitors see the first content after 0.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 327 ms
327 msReal visitors wait 327 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.036
0.036The layout barely moves while loading (CLS 0.036, good is under 0.1).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Perfectly fitted, Premium & Luxury Rack Sheets, Rack Curtai…”.
Total Blocking Time: 16 ms
16 msScripts block the page for only 16 ms while loading. Good is under 200 ms.
Time to Interactive: 1.9 s
1.9 sThe page is fully interactive after 1.9 s.
Images and page weight
An image on the first screen is lazy-loaded
Copy_of_Homepage_Hero_5_-_1300x700_ddba7b59-de12-439a-9be5-2 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.2 g of CO₂ per visit
0.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.20 g of CO₂e: 24.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 725 KiB in 38 requests
725 KiBYour homepage downloads 725 KiB in 38 requests on a phone: images 450 KiB (19), scripts 155 KiB (12) and HTML 47 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
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.
1 image without alt text
1 image has 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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
Title is long (84 characters)
Your title is 84 characters, so Google will cut it off around 60: “Premium Rack Sheets & Rack Curtain Accessories for Navy & Coast Guard – Fleet Sheets”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
38 internal links, 13 external
The homepage links to 38 pages on fleetsheets.com and 13 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Shop luxury and premium rack sheets and rack curtain accessories designed for Navy and Coast Guard. Get comfort away fr…”.
One H1 headline
Your main headline reads: “Fleet Sheets”.
Canonical URL set
The canonical URL is https://www.fleetsheets.com/.
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.fleetsheets.com/sitemap.xml.
AI search readiness
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 (279 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to /collections/comfort-care-packages, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
/customer_authentication/redirect and /collections/all have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
/pages/faq, /customer_authentication/redirect and /pages/contact-us-get-quote 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 17 found) and read each the way a search engine does.
2 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
14 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
1 broken link to your own pages
1 link from your homepage to your own site is broken, for example https://www.fleetsheets.com/collections/comfort-care-packages (404).
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
2 links through redirect chains
2 links go through two or more redirects, for example https://www.fleetsheets.com/customer_authentication/redirect?locale=en®ion_country=US.
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.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
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 (fleetsheets.com).
Valid certificate (43 days left)
The certificate from Let's Encrypt · YE2 verifies for fleetsheets.com and is valid for another 43 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://fleetsheets.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
Domain and trust
DNSSEC is off
fleetsheets.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.
3 checks passed
Domain is 23 years old
23 yearsfleetsheets.com was registered in May 2003 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Certificate issuers are restricted
CAA records allow only letsencrypt.org, pki.goog, ssl.com and digicert.com to issue certificates for fleetsheets.com, so a mis-issued certificate from anyone else is refused.
Registered until May 2028
fleetsheets.com is registered until May 2028.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 244 words
The homepage has only about 244 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
7 calls to action
The homepage has 7 calls to action, for example “Shop Now”, “Shop Care Packages” and “Shop All”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be fleetsheets.com is still delivered. Add a report address, check the reports, then move to quarantine.
Email authentication score: 70/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.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:mailgun.org include:_spf.google.com include:shops.shopify.com include:amazonses.com ~all”.
DKIM signing found
A DKIM key is published (selector “google”, “s1” and “s2”), so receivers can verify mail really came from you.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Apps on your store
No apps were seen in the code your storefront loads.
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Bradenton
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on fleetsheets.com, including 2 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.