Website review, no card needed
alliancesg.com website review
Visit site (opens in a new tab)Reviewed 19 October 202633 issues · 83 checks
This review found 33 issues worth fixing on alliancesg.com, 14 of them high impact, across 83 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
67DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.6 s
3.2 s
4.7 s
6.3 s
7.9 s
9.5 s
11.1 s
12.6 s
Speed
Render-blocking requests
2.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Vimeo adds 1.1 s
1.1 sVimeo costs a phone 1.1 s of main-thread work and 5.3 MB 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: 13.2 s
A phone's processor spends 13.2 s on main-thread work while loading, 7.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 23
23/100Your mobile performance score is 23 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
3.5 MBAbout 3.5 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Vimeo, goconsensus.com and Google Tag Manager and others), adding 8.6 MB and 2.6 s of main-thread time.
Use efficient cache lifetimes
1.1 MB199 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
goconsensus.com adds 507 ms
507 msgoconsensus.com costs a phone 507 ms of main-thread work and 1.4 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.
Reduce unused CSS
450 ms · 67 KiBAbout 67 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 371 ms. During a long task the page ignores taps.
Google Tag Manager adds 241 ms
241 msGoogle Tag Manager costs a phone 241 ms of main-thread work and 306 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.
website-files.com adds 193 ms
193 mswebsite-files.com costs a phone 193 ms of main-thread work and 769 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.
11x.ai adds 151 ms
151 ms11x.ai costs a phone 151 ms of main-thread work and 371 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.
Improve image delivery
120 KiB8 images could be 120 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 22.4 s
22.4 sVisually, the page fills in at 22.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 59.0 s
59.0 sThe page becomes fully interactive after 59.0 s. Good is under 3.8 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Technology built to support the full cycle of Construction …”.
Total Blocking Time: 2.5 s
2.5 sScripts block taps and scrolling for 2.5 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.157
0.157The layout shifts by 0.157 while loading, so content jumps under the reader's thumb. Good is under 0.1.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
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.
Images and page weight
Page weight: 10.1 MB in 465 requests
10.1 MBYour homepage downloads 10.1 MB in 465 requests on a phone: scripts 7.0 MB (193), other files 1.1 MB (140) and images 711 KiB (59). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
682e0f0eba596ddedfee3156_image-group-banner.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 2.9 g of CO₂ per visit
2.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.86 g of CO₂e: 343.4 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must be contained by particular parents (13 elements)
Certain ARIA roles must be contained by particular parents: 13 elements on the page fail this check, rated critical by axe-core.
Links must have discernible text (6 elements)
Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
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.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
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 45 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
53 internal links, 9 external
The homepage links to 53 pages on alliancesg.com and 9 external pages.
8 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Build smarter with Alliance Solutions: expert Sage 100, 300 CRE & Intacct ERP implementation for construction, real est…”.
One H1 headline
Your main headline reads: “Technology built to support the full cycle of Construction & Real Estate.”.
Title: 60 characters
Your title is a healthy 60 characters: “Alliance Solutions – Sage ERP for Construction & Real Estate”.
Canonical URL set
The canonical URL is https://www.alliancesg.com/.
Structured data in place
Structured data found: Organization, WebPage and WebSite.
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.alliancesg.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.alliancesg.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,126 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.alliancesg.com/industries/mechanical-contractors is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.alliancesg.com/sage-construction-management, https://www.alliancesg.com/sage-field-operations and https://www.alliancesg.com/sage-paperless-for-construction have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
5 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “$ is not defined”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
7 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 1,016 words of copy
The homepage carries about 1,016 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: “Talk to an expert”.
8 calls to action
The homepage has 8 calls to action, for example “Click here to download”, “Get in Touch” and “Get in touch”.
Social proof on the page
Social proof on the homepage: 77 testimonial or review blocks, 6 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Microsoft Clarity and HubSpot.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 3 of them by other companies (measured from a US location before any click).
43 other companies contacted
Loading the homepage contacts 43 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 alliancesg.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
- Webflow
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on alliancesg.com, including 20 speed 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.