electronicscience.com website review

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

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

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

4 third-party services load with your homepage (JSDelivr CDN, Google Fonts and Amazon Web Services and others), adding 11.0 MB and 3 ms of main-thread time.

cloudfront.net costs a phone 0 ms of main-thread work and 10.6 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.

Your mobile performance score is 58 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

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

71 KiB could be saved by minifying CSS.

Amazon Web Services costs a phone 0 ms of main-thread work and 438 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.

27 KiB could be saved by minifying JavaScript.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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.

Your homepage downloads 22.5 MB in 107 requests on a phone: images 21.7 MB (18), other files 444 KiB (8) and stylesheets 195 KiB (3). Under 2 MB keeps phones on slow connections fast.

whatwedo-img.jpeg weighs 2.3 MB. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example whatwedo-img.jpeg at 3,008 px wide, shown at 336 px. Resized copies would save about 2.5 MB.

4 images (2.9 MB) 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.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your meta description is 179 characters; Google truncates after about 160, so the end of your pitch is cut.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 9 pages on electronicscience.com and 0 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

/nav-pages/npc-seal.html has no <h1> headline, so visitors and search engines get no clear main topic.

/nav-pages/solutions.html, /nav-pages/blog.html, /nav-pages/contact-us.html, /nav-pages/terms.html, /nav-pages/privacy.html and /nav-pages/npc-seal.html 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.

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

6 images failed to load on a phone, for example https://electronicscience.com/.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

6 errors were logged to the browser console while the page loaded, for example “Loading the font 'https://fonts.gstatic.com/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSKmu0SC55K5gw.woff2' vi…”.

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

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

electronicscience.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

electronicscience.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 448 words of visible text.

electronicscience.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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.

Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.