Website review, no card needed

vexusfiber.com logo

vexusfiber.com website review

Visit site (opens in a new tab)Reviewed 19 November 202644 issues · 88 checks

This review found 44 issues worth fixing on vexusfiber.com, 19 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.3 s2.1 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.6 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.0 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.3 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
213 ms145 msMay 30Nov 14185 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026153 ms
Jun 6, 2026154 ms
Jun 13, 2026154 ms
Jun 20, 2026155 ms
Jun 27, 2026157 ms
Jul 4, 2026157 ms
Jul 11, 2026160 ms
Jul 18, 2026159 ms
Jul 25, 2026157 ms
Aug 1, 2026157 ms
Aug 8, 2026162 ms
Aug 15, 2026170 ms
Aug 22, 2026176 ms
Aug 29, 2026179 ms
Sep 5, 2026181 ms
Sep 12, 2026182 ms
Sep 19, 2026186 ms
Sep 26, 2026194 ms
Oct 3, 2026196 ms
Oct 10, 2026205 ms
Oct 17, 2026205 ms
Oct 24, 2026204 ms
Oct 31, 2026203 ms
Nov 7, 2026192 ms
Nov 14, 2026185 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

Full-page screenshot of vexusfiber.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vexusfiber.com at 0.6 s0.6 s
  2. vexusfiber.com at 1.1 s1.1 s
  3. vexusfiber.com at 1.7 s1.7 s
  4. vexusfiber.com at 2.2 s2.2 s
  5. vexusfiber.com at 2.8 s2.8 s
  6. vexusfiber.com at 3.3 s3.3 s
  7. vexusfiber.com at 3.9 s3.9 s
  8. vexusfiber.com at 4.4 s4.4 s

Speed

12 to fix26
  • Use efficient cache lifetimes

    5.1 s · 1.9 MB

    69 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

  • Improve image delivery

    3.8 s · 2.7 MB

    9 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

  • Reduce unused JavaScript

    3.8 s · 935 KiB

    About 935 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Render-blocking requests

    1.2 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Mobile performance score: 26

    26/100

    Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.5 s

    A phone's processor spends 4.5 s on main-thread work while loading, 2.8 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 (Google Tag Manager, Facebook and pega.digital and others), adding 2.2 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 912 ms

    912 ms

    Google Tag Manager costs a phone 912 ms of main-thread work and 1.2 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

    560 ms · 154 KiB

    About 154 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 560 ms faster on a phone.

  • Facebook adds 368 ms

    368 ms

    Facebook costs a phone 368 ms of main-thread work and 356 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.

  • Legacy JavaScript

    300 ms · 39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • pega.digital adds 284 ms

    284 ms

    pega.digital costs a phone 284 ms of main-thread work and 447 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.

  • 19 long tasks on the main thread

    19 long tasks block the main thread while loading, the longest for 236 ms. During a long task the page ignores taps.

  • Duplicated JavaScript

    150 ms · 5 KiB

    5 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    110 ms · 17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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: 23 ms

    23 ms

    Your server sent the HTML in 23 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 21.8 s

    21.8 s

    Your largest element takes 21.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 25.3 s

    25.3 s

    The page becomes fully interactive after 25.3 s. Good is under 3.8 s.

  • Speed Index: 11.2 s

    11.2 s

    Visually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 4.2 s

    4.2 s

    The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 1.1 s

    1.1 s

    Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

  • Real-user CLS: 0.25

    0.25

    For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 23% slower for real visitors

    +23%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 153 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user TTFB: 880 ms

    880 ms

    Real visitors wait 880 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.19

    0.19

    The layout shifts by 0.19 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 177 ms

    177 ms

    Real visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

Images and page weight

2 to fix64
  • Page weight: 6.0 MB in 133 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 133 requests on a phone: images 2.8 MB (23), scripts 2.6 MB (66) and fonts 364 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Vex-1920x1080_construction-480x270.png 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).

  • 2 images in older formats

    2 images (214 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.

  • About 1.7 g of CO₂ per visit

    1.69 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 203.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8089
  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 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.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 37 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: 37 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9290
  • 4 H1 headlines

    There are 4 <h1> headlines (“Business Internet”, “BY PHONE” and “CHAT”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 24 internal links, 10 external

    The homepage links to 24 pages on vexusfiber.com and 10 external pages.

6 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Vexus Fiber offers high speed home internet and business internet with local friendly support. Get faster fiber interne…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Vexus Fiber - Home & Business Internet Provider”.

  • Canonical URL set

    The canonical URL is https://www.vexusfiber.com/.

  • Structured data in place

    Structured data found: Article, Organization, Person, 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.vexusfiber.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.vexusfiber.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 (401 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix50
  • 1 linked page is broken

    Your homepage links to https://www.vexusfiber.com/residential/customer-care/gocare, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://www.vexusfiber.com/t-mobile-fiber-faq is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages share 2 titles

    https://www.vexusfiber.com/business-internet and https://www.vexusfiber.com/business/small-midsize-business/business-internet all use the title “All Sizes Business Internet Solution in 2024: Vexus Fiber”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://www.vexusfiber.com/business-internet and https://www.vexusfiber.com/business/small-midsize-business/business-internet use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.vexusfiber.com/residential/customer-care, whose canonical is https://www.vexusfiber.com/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.vexusfiber.com/contact-us, https://www.vexusfiber.com/residential/customer-care, https://www.vexusfiber.com/t-mobile-fiber-faq and https://www.vexusfiber.com/residential/customer-care/report-trouble have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.vexusfiber.com/contact-us, https://www.vexusfiber.com/residential/customer-care and https://www.vexusfiber.com/residential/customer-care/report-trouble 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://px.adentifi.com/Pixels?a_id=11722;p_url=https%3A%2F%2Fwww.vexusfiber.com%2F;uq=9147428752249.299.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://signup.vexusfiber.com/vssuaddress-search/AddressSearchComponent.js' from origin 'https://w…”.

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 315 words of copy

    The homepage carries about 315 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start Shopping”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Shop” and “Visit Our FAQs to Learn More”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 5 of them by other companies (measured from a US location before any click).

  • 30 other companies contacted

    Loading the homepage contacts 30 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 vexusfiber.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 Tag Manager
Hosting
Sucuri

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on vexusfiber.com, including 22 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25