Website review, no card needed
superiorplus.com website review
Visit site (opens in a new tab)Reviewed 20 October 202635 issues · 75 checks
This review found 35 issues worth fixing on superiorplus.com, 13 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
75CClosest competitors among reviewed websites
Compare side by sideOne 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
Use efficient cache lifetimes
3.5 s · 2.3 MB62 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).
Render-blocking requests
2.7 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.
Reduce unused JavaScript
1.3 s · 317 KiBAbout 317 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 88). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 725 KiB4 images could be 725 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
630 ms · 128 KiBAbout 128 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 630 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Accessibe Accessibility Overlay, Google Tag Manager and Bing Ads and others), adding 478 KiB and 275 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 88 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
7 KiB7 KiB could be saved by minifying JavaScript.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 823 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Building on our success”.
First Contentful Paint: 6.0 s
6.0 sThe first text or image appears after 6.0 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
6 images without width and height
6 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.
2 checks passed
Total Blocking Time: 142 ms
142 msScripts block the page for only 142 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image over 500 KB
Certarus_Logo_2026-scaled.jpg weighs 700 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
585 KiB1 image is downloaded at several times the size a phone draws it, for example Certarus_Logo_2026-scaled.jpg at 2,560 px wide, shown at 346 px. Resized copies would save about 585 KiB.
Page weight: 2.8 MB in 83 requests
2.8 MBYour homepage downloads 2.8 MB in 83 requests on a phone: images 1.8 MB (15), scripts 771 KiB (31) and stylesheets 193 KiB (21). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (742 KiB) are 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.
3 images below the first screen load straight away
3 images further down the page (762 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 95.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Home - Superior Plus”. Between 30 and 65 characters leaves room to say what you do and for whom.
6 H1 headlines
There are 6 <h1> headlines (“2025 Investor Day”, “About Superior Plus” and “Presentations”). One clear main headline is easier for people and search engines.
Meta description is long (386 characters)
Your meta description is 386 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
54 internal links, 1 external
The homepage links to 54 pages on superiorplus.com and 1 external page.
4 checks passed
Canonical URL set
The canonical URL is https://www.superiorplus.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://www.superiorplus.com/sitemap_index.xml.
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.
No llms.txt
There is no https://superiorplus.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 (371 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://superiorplus.com/q4-2025-earnings-release-vf has no <title>, so Google invents the link text in results.
1 page without a meta description
https://superiorplus.com/q4-2025-earnings-release-vf has no meta description, so Google writes the search snippet from whatever text it finds.
14 pages share a meta description
https://superiorplus.com/contact-us, https://superiorplus.com/investor-request-information, https://superiorplus.com/about, https://superiorplus.com/about/corporate-governance, https://superiorplus.com/our-businesses and https://superiorplus.com/our-businesses/energy-distribution and 8 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://superiorplus.com/q4-2025-earnings-release-vf has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://superiorplus.com/contact-us and https://superiorplus.com/investor-request-information have 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.
3 pages slow to respond
https://superiorplus.com/press-releases, https://superiorplus.com/investor-relations/events-presentations/2026-first-quarter-results-conference-call and https://superiorplus.com/q4-2025-earnings-release-vf took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.superiorplus.com/wp-content/plugins/advanced-popups/fonts/advanced-popups-icons.woff' fr…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
18 of 21 tappable elements near the top are at least 24 px.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 329 words of copy
The homepage carries about 329 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “Sign Up for News Releases” and “Request Information”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
9 other companies contacted
Loading the homepage contacts 9 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 superiorplus.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
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on superiorplus.com, including 12 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.