Website review, no card needed

filestack.com logo

filestack.com website review

Visit site (opens in a new tab)Reviewed 21 November 202612 issues · 67 checks

This review found 12 issues worth fixing on filestack.com, 3 of them high impact, across 67 checks. The most urgent: fails Core Web Vitals for real visitors. 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
5.7 s3.3 sMay 30Nov 143.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.7 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.7 s
Jun 27, 20263.9 s
Jul 4, 20264.1 s
Jul 11, 20264.3 s
Jul 18, 20264.4 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.2 s
Aug 15, 20264.2 s
Aug 22, 20264.2 s
Aug 29, 20264.3 s
Sep 5, 20264.2 s
Sep 12, 20264.2 s
Sep 19, 20264.3 s
Sep 26, 20264.9 s
Oct 3, 20265.3 s
Oct 10, 20265.4 s
Oct 17, 20265.4 s
Oct 24, 20265.2 s
Oct 31, 20264.8 s
Nov 7, 20264.2 s
Nov 14, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
429 ms307 msMay 30Nov 14389 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026347 ms
Jun 6, 2026334 ms
Jun 13, 2026321 ms
Jun 20, 2026340 ms
Jun 27, 2026348 ms
Jul 4, 2026378 ms
Jul 11, 2026387 ms
Jul 18, 2026369 ms
Jul 25, 2026378 ms
Aug 1, 2026371 ms
Aug 8, 2026365 ms
Aug 15, 2026372 ms
Aug 22, 2026372 ms
Aug 29, 2026368 ms
Sep 5, 2026368 ms
Sep 12, 2026348 ms
Sep 19, 2026342 ms
Sep 26, 2026338 ms
Oct 3, 2026355 ms
Oct 10, 2026370 ms
Oct 17, 2026388 ms
Oct 24, 2026408 ms
Oct 31, 2026415 ms
Nov 7, 2026404 ms
Nov 14, 2026389 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 filestack.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix94
  • 1,539 HTML elements

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

  • 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: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

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

  • Real-user INP: 309 ms

    309 ms

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Cumulative Layout Shift: 0.118

    0.118

    The layout shifts by 0.118 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

8 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “More than a file upload API. Securely upload, transform, st…”.

  • Time to Interactive: 2.4 s

    2.4 s

    The page is fully interactive after 2.4 s.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Speed Index: 1.1 s

    1.1 s

    Visually, the page fills in at 1.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 15 ms

    15 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.41 g

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

4 checks passed
  • Page weight: 1.5 MB in 19 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 19 requests on a phone: media 963 KiB (1), fonts 440 KiB (8) and HTML 56 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • 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 9193
  • 40 text elements with low contrast

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

  • 15 tap targets too small

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

  • All page content should be contained by landmarks (34 elements)

    All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 164 internal links, 12 external

    The homepage links to 164 pages on filestack.com and 12 external pages.

8 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Add a sleek file uploader to your website with two lines of code. Upload from local disk, Dropbox, Instagram, Google Dr…”.

  • One H1 headline

    Your main headline reads: “Your entire file infrastructure in two lines of code.”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “The Best File Uploader & Upload API - Filestack”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, Organization and WebPage.

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

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

  • llms.txt published

    The site publishes https://www.filestack.com/llms.txt (8 KiB, 62 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 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 15 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

    88 of 104 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

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

  • 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 1,266 words of copy

    The homepage carries about 1,266 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a Walkthrough” and “Quick start”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Book a Walkthrough”, “Pricing” and “Quick start”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

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

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

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 filestack.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 Tag Manager
Hosting
Fastly

Company

Headquarters
San Antonio

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 12 issues on filestack.com, including 5 speed issues and 1 SEO issue. 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