Website review, no card needed
aspensalesgroup.com website review
Visit site (opens in a new tab)Reviewed 5 November 202630 issues · 75 checks
This review found 30 issues worth fixing on aspensalesgroup.com, 10 of them high impact, across 75 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
81BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
3.9 s
7.8 s
11.7 s
15.6 s
19.4 s
23.3 s
27.2 s
31.1 s
Speed
Render-blocking requests
4.0 s51 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Reduce unused CSS
1.1 s · 215 KiBAbout 215 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
356 KiB4 images could be 356 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,650 HTML elements
The page has 1,650 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
95 KiBAbout 95 KiB of JavaScript is downloaded but never used on this page.
4 third-party services on the page
4 third-party services load with your homepage (GoDaddy, cloudflare.com and Google Fonts and others), adding 112 KiB and 58 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
19 KiB1 file is served with short cache lifetimes, so returning visitors download them again (19 KiB).
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 254 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 18.2 s
18.2 sVisually, the page fills in at 18.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Taking Your Business to New Heights”. Most of its time is element render delay (2.4 s).
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.
3 checks passed
Time to Interactive: 3.5 s
3.5 sThe page is fully interactive after 3.5 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.0 MB in 114 requests
2.0 MBYour homepage downloads 2.0 MB in 114 requests on a phone: images 1.2 MB (9), stylesheets 344 KiB (48) and scripts 310 KiB (44). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
42 KiB1 image is downloaded at several times the size a phone draws it, for example aspen_global_logo_whiteoutline_400.png at 390 px wide, shown at 68 px. Resized copies would save about 42 KiB.
1 image in older formats
1 image (58 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
1 image below the first screen load straight away
1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “Taking Your Business To New Heights – Taking Your Business To New Heights”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://aspenglobalenterprise.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at aspenglobalenterprise.com/robots.txt, the first file search crawlers ask for.
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
127 internal links, 2 external
The homepage links to 127 pages on aspensalesgroup.com and 2 external pages.
1 checks passed
Canonical URL set
The canonical URL is https://aspenglobalenterprise.com/.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,671 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://aspenglobalenterprise.com/sales-divisions, https://aspenglobalenterprise.com/sweet-potato-fries-and-specialty-potato-products, https://aspenglobalenterprise.com/french-fries-and-specialty-potato-products, https://aspenglobalenterprise.com/appetizers, https://aspenglobalenterprise.com/eggs and https://aspenglobalenterprise.com/frozen-fruits and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://aspenglobalenterprise.com/sales-divisions, https://aspenglobalenterprise.com/sweet-potato-fries-and-specialty-potato-products, https://aspenglobalenterprise.com/french-fries-and-specialty-potato-products, https://aspenglobalenterprise.com/eggs, https://aspenglobalenterprise.com/sugar and https://aspenglobalenterprise.com/sustainability and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
12 pages of 13 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 628 words of copy
The homepage carries about 628 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: “Contact” and “Learn more”.
21 calls to action
The homepage has 21 calls to action, for example “Contact”, “Learn more” and “Contact us”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 aspensalesgroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- GoDaddy
Company
- Headquarters
- Bedminster Township
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on aspensalesgroup.com, including 9 speed issues, 8 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.