Website review, no card needed

Instrumentl logo

instrumentl.com website review

Visit site (opens in a new tab)Reviewed 24 October 202636 issues · 80 checks

This review found 36 issues worth fixing on instrumentl.com, 15 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.

Read the full growth playbook for Instrumentl

  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.2 s1.8 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.5 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.1 s
Sep 26, 20262.9 s
Oct 3, 20262.5 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
435 ms195 msMay 2Oct 17364 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026248 ms
May 9, 2026252 ms
May 16, 2026251 ms
May 23, 2026260 ms
May 30, 2026254 ms
Jun 6, 2026251 ms
Jun 13, 2026244 ms
Jun 20, 2026238 ms
Jun 27, 2026231 ms
Jul 4, 2026227 ms
Jul 11, 2026226 ms
Jul 18, 2026223 ms
Jul 25, 2026223 ms
Aug 1, 2026248 ms
Aug 8, 2026271 ms
Aug 15, 2026282 ms
Aug 22, 2026290 ms
Aug 29, 2026329 ms
Sep 5, 2026377 ms
Sep 12, 2026393 ms
Sep 19, 2026407 ms
Sep 26, 2026382 ms
Oct 3, 2026327 ms
Oct 10, 2026375 ms
Oct 17, 2026364 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 instrumentl.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. instrumentl.com at 0.5 s0.5 s
  2. instrumentl.com at 1.0 s1.0 s
  3. instrumentl.com at 1.5 s1.5 s
  4. instrumentl.com at 2.0 s2.0 s
  5. instrumentl.com at 2.5 s2.5 s
  6. instrumentl.com at 3.1 s3.1 s
  7. instrumentl.com at 3.6 s3.6 s
  8. instrumentl.com at 4.1 s4.1 s

Speed

12 to fix38
  • Reduce unused JavaScript

    5.2 s · 893 KiB

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

  • Render-blocking requests

    4.5 s

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

  • Use efficient cache lifetimes

    1.9 s · 376 KiB

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

  • Mobile performance score: 38

    38/100

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

  • 8 third-party services on the page

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

  • Improve image delivery

    600 ms · 153 KiB

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

  • Reduce unused CSS

    450 ms · 117 KiB

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

  • Google Tag Manager adds 422 ms

    422 ms

    Google Tag Manager costs a phone 422 ms of main-thread work and 659 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: 4.0 s

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

  • Legacy JavaScript

    300 ms · 61 KiB

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

  • 14 long tasks on the main thread

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

  • 1,920 HTML elements

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

  • Minify CSS

    150 ms · 27 KiB

    27 KiB could be saved by minifying CSS.

  • Duplicated JavaScript

    150 ms · 17 KiB

    17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

    7 ms

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

Core Web Vitals

12 to fix33
  • 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: 502 ms

    502 ms

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • First Contentful Paint: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 21.7 s

    21.7 s

    Your largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Instrumentl awards view showing funder types, total awarded…”.

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Total Blocking Time: 705 ms

    705 ms

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

  • Real-user LCP: 3.8 s

    3.8 s

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

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

    +48%

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

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

    +46%

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

2 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 6.3 MB in 119 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 119 requests on a phone: media 3.3 MB (2), scripts 1.8 MB (43) and images 555 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    87 KiB

    1 image is downloaded at several times the size a phone draws it, for example hero-product-ui-6d8448923c7cfe2eb32b6c461fe381c2e4711be32b1a at 2,048 px wide, shown at 352 px. Resized copies would save about 87 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (359 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.79 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9395
  • 10 text elements with low contrast

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

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 3 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 9289
  • 2 H1 headlines

    There are 2 <h1> headlines (“Grant work was scattered. Now it’s a system.” and “Nourish Community Garden”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://www.instrumentl.com/sitemaps/main/sitemap.xml.gz, so Google discovers your pages only by following links.

  • 4 links with vague text

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

  • 138 internal links, 9 external

    The homepage links to 138 pages on instrumentl.com and 9 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Instrumentl is grant management software for nonprofits: find, win, and manage every grant in one workspace. Trusted by…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Instrumentl - Your intelligent grant operating system”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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.

AI search readiness

1 to fix83
  • Parts of the site are closed to 2 AI crawlers

    Your robots.txt lets ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,912 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.instrumentl.com/llms.txt (2 KiB, 11 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 77 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

2 to fixGoogle 10087
  • 5 small tap targets

    5 of 21 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”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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,440 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try 14 days free”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Pricing”, “Try 14 days free” and “02 Apply”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo, 1 trust badge and “5,500+ active customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, HubSpot and Heap.

  • Direct contact links

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

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 1 of them by other companies (measured from a US location before any click).

  • 42 other companies contacted

    Loading the homepage contacts 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 instrumentl.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager | Heap

Hiring

Hiring
10 open roles
Teams
SDR (3), Customer Success (2), Engineering (2), Product (2)
Job board
lever

Company

Employees
120
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on instrumentl.com, including 24 speed issues and 3 SEO issues. 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