derbysoft.com website review

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

About 2.5 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 12.0 s faster on a phone.

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.4 s faster on a phone.

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

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

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

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

88 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and Google CDN and others), adding 2.7 MB and 1.9 s of main-thread time.

hsappstatic.net costs a phone 619 ms of main-thread work and 711 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.

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

Google CDN costs a phone 280 ms of main-thread work and 742 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.

16 long tasks block the main thread while loading, the longest for 304 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.

59 KiB could be saved by minifying CSS.

Polyfills for old browsers add 43 KiB JavaScript that modern phones do not need.

25 KiB could be saved by minifying JavaScript.

17 KiB JavaScript is shipped twice across bundles.

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.

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

Your largest element takes 58.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DerbySoft's travel commerce accelerator visually connects n…”.

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

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

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

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

35 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 19.9 MB in 307 requests on a phone: media 8.8 MB (8), scripts 4.1 MB (76) and images 3.2 MB (150). Under 2 MB keeps phones on slow connections fast.

Low-Cost-Carriers-in-Air-Travel.jpg weighs 678 KiB. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example mgm.png at 2,644 px wide, shown at 130 px. Resized copies would save about 653 KiB.

14 images (1.6 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.

26 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.

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

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: url points at a different host (https://ds2024.onpressidium.com/)”.

No XML sitemap at https://derbysoft.com/sitemap.xml, so Google discovers your pages only by following links.

17 links have no real href, so search engines can't follow them.

There is no robots.txt at derbysoft.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 77 pages on derbysoft.com and 7 external pages.

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.

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.

/cn, /why-derbysoft, /resources, /streamlined-connectivity, /exchange and /property-connector and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

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

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

Social proof on the homepage: 20 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

DMARC is set to p=none, so mail pretending to be derbysoft.com is still delivered. Reports are on, so moving to quarantine is the next step.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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