Website review, no card needed
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
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 248 ms |
| May 9, 2026 | 252 ms |
| May 16, 2026 | 251 ms |
| May 23, 2026 | 260 ms |
| May 30, 2026 | 254 ms |
| Jun 6, 2026 | 251 ms |
| Jun 13, 2026 | 244 ms |
| Jun 20, 2026 | 238 ms |
| Jun 27, 2026 | 231 ms |
| Jul 4, 2026 | 227 ms |
| Jul 11, 2026 | 226 ms |
| Jul 18, 2026 | 223 ms |
| Jul 25, 2026 | 223 ms |
| Aug 1, 2026 | 248 ms |
| Aug 8, 2026 | 271 ms |
| Aug 15, 2026 | 282 ms |
| Aug 22, 2026 | 290 ms |
| Aug 29, 2026 | 329 ms |
| Sep 5, 2026 | 377 ms |
| Sep 12, 2026 | 393 ms |
| Sep 19, 2026 | 407 ms |
| Sep 26, 2026 | 382 ms |
| Oct 3, 2026 | 327 ms |
| Oct 10, 2026 | 375 ms |
| Oct 17, 2026 | 364 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.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.1 s
3.6 s
4.1 s
Speed
Reduce unused JavaScript
5.2 s · 893 KiBAbout 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 s10 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 KiB16 files are served with short cache lifetimes, so returning visitors download them again (376 KiB).
Mobile performance score: 38
38/100Your 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 KiB4 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 KiBAbout 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 msGoogle 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 KiBPolyfills 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 KiB27 KiB could be saved by minifying CSS.
Duplicated JavaScript
150 ms · 17 KiB17 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 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 msReal 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 sReal 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 sThe 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 sYour 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 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 705 ms
705 msScripts 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 sReal 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 sReal 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.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 119 requests
6.3 MBYour 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 KiB1 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 gBy 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
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
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
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
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
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
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
6Before 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
27Opening 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
- Careers page
- www.instrumentl.com/careers (opens in a new tab)
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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.