anothersource.com website review

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

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

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

8 images could be 946 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and LinkedIn Ads and others), adding 914 KiB and 441 ms of main-thread time.

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

Desktop scores 90 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Another Source delivers innovative professional recruiting …”.

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

The first text or image appears after 3.5 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.

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

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.

2 images are downloaded at several times the size a phone draws them, for example Eva-Graham-CalArts.png at 627 px wide, shown at 126 px. Resized copies would save about 569 KiB.

Your homepage downloads 3.2 MB in 99 requests on a phone: images 1.9 MB (21), scripts 1.1 MB (34) and fonts 115 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

1 image (319 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.90 g of CO₂e: 108.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

The homepage links to 36 pages on anothersource.com and 1 external page.

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.

/industries/data-center-and-construction and /industries/data-center-real-estate all use the title “Data Center/Construction Recruitment -”. Search engines can't tell which page to show for a search, so each competes with the others.

/resources has no meta description, so Google writes the search snippet from whatever text it finds.

/industries/data-center-and-construction and /industries/data-center-real-estate use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /industries/data-center-real-estate, whose canonical is /industries/data-center-and-construction. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image is served at too low a resolution for sharp phone screens.

1 link from your homepage to your own site is broken, for example https://www.anothersource.com/cdn-cgi/content?id=lJOw1bW0BWIdpBz0I.R7kWgKwfS..NTY6wTW4Anbi.s-1792678057.7606707-1.2.1.1-c5pObBFOACHUbvPCt5BYfI2cAE2TEkq0evHvwt6VQPWT7yFwm1FFzk9Wj91VDVB5 (404).

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.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

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.

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

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

Social proof on the homepage: 74 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.

The homepage carries about 863 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 (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.

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

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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.