Website review, no card needed
gtmtax.com website review
Visit site (opens in a new tab)Reviewed 26 October 202629 issues · 79 checks
This review found 29 issues worth fixing on gtmtax.com, 13 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
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
Speed
Reduce unused JavaScript
10.0 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.0 s faster on a phone.
Render-blocking requests
8.6 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.6 s.
Minify JavaScript
3.1 s · 651 KiB651 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
2.0 s · 393 KiB18 files are served with short cache lifetimes, so returning visitors download them again (393 KiB).
Unpkg adds 1.0 s
1.0 sUnpkg costs a phone 1.0 s of main-thread work and 102 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 8.6 s
A phone's processor spends 8.6 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Unpkg, Google CDN and Google Tag Manager and others), adding 2.3 MB and 2.1 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 68). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
659 KiB1 image could be 659 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 472 ms
472 msGoogle CDN costs a phone 472 ms of main-thread work and 1.1 MB 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 303 ms
303 msGoogle Tag Manager costs a phone 303 ms of main-thread work and 523 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.
Hubspot adds 131 ms
131 msHubspot costs a phone 131 ms of main-thread work and 305 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
290 ms · 26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
Legacy JavaScript
150 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 136 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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 20.0 s
20.0 sThe first text or image appears after 20.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.2 s
24.2 sYour largest element takes 24.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Global tax experts obsessed with what’s best for you.”.
Speed Index: 20.0 s
20.0 sVisually, the page fills in at 20.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.2 s
24.2 sThe page becomes fully interactive after 24.2 s. Good is under 3.8 s.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 17 ms
17 msScripts block the page for only 17 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.7 MB in 92 requests
4.7 MBYour homepage downloads 4.7 MB in 92 requests on a phone: scripts 3.3 MB (39), images 738 KiB (16) and other files 377 KiB (23). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
shutterstock_2477129197.jpg.webp weighs 693 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
577 KiB1 image is downloaded at several times the size a phone draws it, for example shutterstock_2477129197.jpg.webp at 2,560 px wide, shown at 350 px. Resized copies would save about 577 KiB.
About 1.3 g of CO₂ per visit
1.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 160.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Banner landmark should not be contained in another landmark (3 elements)
Banner landmark should not be contained in another landmark: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
85 internal links, 10 external
The homepage links to 85 pages on gtmtax.com and 10 external pages.
7 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Global Tax Management (GTM Tax) is a corporate tax service firm built on people, purpose, and performance. We deliver e…”.
One H1 headline
Your main headline reads: “Global tax experts obsessed with what’s best for you.”.
Title: 53 characters
Your title is a healthy 53 characters: “Leading Corporate Tax Services & Automation | GTM Tax”.
Canonical URL set
The canonical URL is https://gtmtax.com/.
Structured data in place
Structured data found: BreadcrumbList, Corporation, WebPage and WebSite.
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://gtmtax.com/page-sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (631 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://gtmtax.com/llms.txt (4 KiB, 40 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://gtmtax.com/service/tax-accounting and https://gtmtax.com/event/enterprise-training-solutions-for-corporate-tax-teams have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://gtmtax.com/specialty-area/federal-income-tax took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.
6 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.
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
17 small tap targets
17 of 69 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 486 words of copy
The homepage carries about 486 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: “Transfer Pricing” and “Learn more about our clients”.
7 calls to action
The homepage has 7 calls to action, for example “Transfer Pricing”, “Contact Us” and “Download PDF”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, HubSpot and LinkedIn Insight.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
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.
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 gtmtax.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 Analytics | Google Tag Manager
- Hosting
- WP Engine
Company
- Employees
- 214
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on gtmtax.com, including 16 speed issues, 2 SEO issues and 1 conversion gap. 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.