Website review, no card needed

aegiselect.com logo

aegiselect.com website review

Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 72 checks

This review found 31 issues worth fixing on aegiselect.com, 9 of them high impact, across 72 checks. The most urgent: improve image delivery. 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
4.0 s2.8 sMay 30Nov 142.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.7 s
Jun 6, 20263.5 s
Jun 13, 20263.3 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20263.8 s
Jul 11, 20263.9 s
Jul 18, 20263.6 s
Jul 25, 20263.4 s
Aug 1, 20263.3 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.2 s
Aug 29, 20263.1 s
Sep 5, 20263.3 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.3 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Oct 24, 20263.2 s
Oct 31, 20263.1 s
Nov 7, 20263.1 s
Nov 14, 20262.9 s

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 aegiselect.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aegiselect.com at 0.6 s0.6 s
  2. aegiselect.com at 1.2 s1.2 s
  3. aegiselect.com at 1.8 s1.8 s
  4. aegiselect.com at 2.4 s2.4 s
  5. aegiselect.com at 3.1 s3.1 s
  6. aegiselect.com at 3.7 s3.7 s
  7. aegiselect.com at 4.3 s4.3 s
  8. aegiselect.com at 4.9 s4.9 s

Speed

4 to fix67
  • Improve image delivery

    3.6 s · 1.0 MB

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

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    550 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • 1,642 HTML elements

    The page has 1,642 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    150 ms · 25 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (25 KiB).

  • 4 third-party services on the page

    4 third-party services load with your homepage (Cloudflare CDN, Google Fonts and Google Tag Manager and others), adding 240 KiB and 4 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.

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

    A phone's processor spends 1.0 s on main-thread work while loading, 334 ms of it running JavaScript. That is comfortably low.

  • Server response: 51 ms

    51 ms

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

Core Web Vitals

9 to fix50
  • 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: 9.1 s

    9.1 s

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

  • Time to Interactive: 9.2 s

    9.2 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • 12 images without width and height

    12 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 1.8 s

    1.8 s

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Total Blocking Time: 136 ms

    136 ms

    Scripts block the page for only 136 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix83
  • 8 images far larger than shown

    428 KiB

    8 images are downloaded at several times the size a phone draws them, for example Screen_Shot_2023-02-07_at_1.25.58_PM.png at 1,208 px wide, shown at 156 px. Resized copies would save about 428 KiB.

  • 9 images below the first screen load straight away

    9 images further down the page (709 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (170 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.

  • About 0.5 g of CO₂ per visit

    0.50 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 59.9 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: 1.8 MB in 71 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 71 requests on a phone: images 1.4 MB (58), scripts 197 KiB (3) and HTML 67 KiB (1). That is a lean page.

Accessibility

4 to fixGoogle 9794
  • 21 tap targets too small

    21 tap targets are too small or too close together to hit reliably with a finger.

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 18 links without text

    18 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9270
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (106 characters)

    Your title is 106 characters, so Google will cut it off around 60: “Industrial Cameras, Industrial Imaging and Machine Vision - Wholesale Distributor - Aegis…”.

  • Meta description is short (19 characters)

    Your meta description is only 19 characters: “Default Description”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

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

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 56 internal links, 6 external

    The homepage links to 56 pages on aegiselect.com and 6 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://aegis-elec.com/.

  • 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://aegis-elec.com/pub/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (467 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://aegis-elec.com/llms.txt (195 KiB, 1,317 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9287
  • 14 small tap targets

    14 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “require is not defined”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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.

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

    The homepage carries about 312 words of visible text.

6 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Learn more” and “Learn More >”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 2 trust badges.

  • Analytics in place

    Analytics detected: 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

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 aegiselect.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
Tailwind CSS
E-commerce
Magento
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on aegiselect.com, including 13 speed issues, 6 SEO 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

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