edictsystems.com website review

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

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

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

4 images could be 212 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, sf14g.com and Hubspot and others), adding 1.1 MB and 1.1 s of main-thread time.

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

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

15 KiB could be saved by minifying JavaScript.

A phone's processor spends 2.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EDI SOLUTIONS & MANAGED SERVICES Our cloud-based Electronic…”.

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

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

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

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

6 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 2.4 MB in 230 requests on a phone: scripts 1.4 MB (77), images 482 KiB (21) and stylesheets 279 KiB (95). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example EdictHomeTP.jpg at 1,100 px wide, shown at 351 px. Resized copies would save about 7 KiB.

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

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

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

18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

Elements with visible text labels do not have matching accessible names. (5 elements).

There are 5 <h1> headlines (“Home”, “EDI SOLUTIONS & MANAGED SERVICES” and “WHAT CAN WE DO FOR YOU?”). One clear main headline is easier for people and search engines.

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 80 pages on edictsystems.com and 4 external pages.

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.

There is no /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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5796398&tm=gtm002&Ver=2&mid=a2e68812-c8bb-464c-b9ee-1dc47d8922c3&bo=1&sid=c58303d0cbbf11f19eb6892eda4915a2&vid=c58335d0cbbf11f1ab39a393bb331449&vids=1&msclkid=N&pi=918.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 527 words of visible text.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (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.

Opening the homepage sets 16 cookies (measured from a US location before any click).

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