Website review, no card needed
integritymusic.com website review
Visit site (opens in a new tab)Reviewed 24 October 202646 issues · 89 checks
This review found 46 issues worth fixing on integritymusic.com, 16 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
71CClosest competitors among Squarespace websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.3 s |
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.5 s |
| Jun 27, 2026 | 4.8 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 189 ms |
| May 9, 2026 | 191 ms |
| May 16, 2026 | 171 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 183 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 186 ms |
| Jul 18, 2026 | 177 ms |
| Jul 25, 2026 | 177 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 206 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 172 ms |
| Sep 26, 2026 | 182 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 157 ms |
| Oct 17, 2026 | 157 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.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
6.0 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.0 s.
Reduce unused JavaScript
2.3 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 49). 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 (Squarespace, Google Tag Manager and Google CDN and others), adding 2.9 MB and 1.7 s of main-thread time.
Use efficient cache lifetimes
700 ms · 138 KiB6 files are served with short cache lifetimes, so returning visitors download them again (138 KiB).
Squarespace adds 497 ms
497 msSquarespace costs a phone 497 ms of main-thread work and 995 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 454 ms
454 msGoogle Tag Manager costs a phone 454 ms of main-thread work and 506 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 CDN adds 414 ms
414 msGoogle CDN costs a phone 414 ms of main-thread work and 764 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.
Reduce unused CSS
300 ms · 113 KiBAbout 113 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Legacy JavaScript
300 ms · 72 KiBPolyfills for old browsers add 72 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 291 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Improve image delivery
24 KiB3 images could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 39 ms
39 msYour server sent the HTML in 39 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 LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.5 s
8.5 sThe first text or image appears after 8.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “What A Life - CalledOut Music”.
Time to Interactive: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 829 ms
829 msScripts block taps and scrolling for 829 ms in total while the page loads. Good is under 200 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.3 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user TTFB: 759 ms
759 msReal visitors wait 759 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 189 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 106 requests
3.8 MBYour homepage downloads 3.8 MB in 106 requests on a phone: scripts 2.4 MB (47), other files 484 KiB (15) and images 385 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (15 characters)
Your title is only 15 characters: “Integrity Music”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (304 characters)
Your meta description is 304 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5c34e2bc2971145d5d8…”.
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.
19 internal links, 27 external
The homepage links to 19 pages on integritymusic.com and 27 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.integritymusic.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.integritymusic.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, url, logo and description. 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.integritymusic.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 (141 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.integritymusic.com/us-artists and https://www.integritymusic.com/roster all use the title “US Artists - Integrity Music”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://www.integritymusic.com/news, https://www.integritymusic.com/about, https://www.integritymusic.com/us-artists, https://www.integritymusic.com/global-artists, https://www.integritymusic.com/songwriters and https://www.integritymusic.com/roster and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.integritymusic.com/roster, whose canonical is https://www.integritymusic.com/us-artists. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.integritymusic.com/news and https://www.integritymusic.com/uk-job-openings-content have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.integritymusic.com/uk-job-openings-content has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/5c34e2bc2971145d5d83d73a/410/679d36ccfa440f…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 152 words
The homepage has only about 152 words of visible text; thin pages give Google and first-time buyers little to go on.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
7 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Sign Up” and “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel, HubSpot and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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 Meta Pixel and 1 more (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 2 of them by other companies (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.
27 other companies contacted
Loading the homepage contacts 27 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 integritymusic.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
- Squarespace
- Framework
- jQuery
- Analytics
- Google Analytics
Company
- Founded
- 1987
- Headquarters
- Colorado Springs
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on integritymusic.com, including 21 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.