Website review, no card needed
opexustech.com website review
Visit site (opens in a new tab)Reviewed 2 November 202619 issues · 68 checks
This review found 19 issues worth fixing on opexustech.com, 5 of them high impact, across 68 checks. The most urgent: unlabelled dropdowns. 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
90AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 84 ms |
| May 23, 2026 | 86 ms |
| May 30, 2026 | 84 ms |
| Jun 6, 2026 | 93 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
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused CSS
150 ms · 54 KiBAbout 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
150 ms · 17 KiB1 image could be 17 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.
3 third-party services on the page
3 third-party services load with your homepage (shortpixel.ai, Vimeo and Adobe TypeKit), adding 369 KiB and 18 ms of main-thread time.
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.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 62 ms of it running JavaScript. That is comfortably low.
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest content (LCP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (1.6 s).
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Time to Interactive: 3.9 s
3.9 sThe page becomes fully interactive after 3.9 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 84 ms to 93 ms 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.003
0.003The layout barely moves while loading (CLS 0.003, 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
About 0.2 g of CO₂ per visit
0.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.16 g of CO₂e: 19.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 594 KiB in 43 requests
594 KiBYour homepage downloads 594 KiB in 43 requests on a phone: images 253 KiB (19), fonts 194 KiB (5) and stylesheets 86 KiB (11). That is a lean page.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
22 tap targets too small
22 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
65 internal links, 39 external
The homepage links to 65 pages on opexustech.com and 39 external pages.
8 checks passed
Meta description: 120 characters
Your meta description is 120 characters: “We are a team of passionate government insiders who design, develop, and deliver government process management software.”.
One H1 headline
Your main headline reads: “Fed up with software that government can't use?”.
Title: 45 characters
Your title is a healthy 45 characters: “OPEXUS: Operational Excellence for Government”.
Canonical URL set
The canonical URL is https://www.opexustech.com/.
Structured data in place
Structured data found: BreadcrumbList, 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.opexustech.com/sitemap_index.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 (1,101 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.opexustech.com/llms.txt (5 KiB, 52 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.opexustech.com/reseller-partners declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.opexustech.com/reseller-partners all use the title “OPEXUS: Operational Excellence for Government”. Search engines can't tell which page to show for a search, so each competes with the others.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 818 words of copy
The homepage carries about 818 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: “REQUEST DEMO” and “CONTACT”.
8 calls to action
The homepage has 8 calls to action, for example “Request Demo”, “Contact” and “REQUEST DEMO”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links 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
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 opexustech.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
- WordPress.com
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on opexustech.com, including 8 speed issues and 2 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.