req.co website review

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

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

13 images could be 931 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

About 45 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

1 third-party service load with your homepage (podpitch.com), adding 27 KiB and 186 ms of main-thread time.

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

About 19 KiB of CSS is downloaded but never applied on this page. 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 150 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.

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 196 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

Firefly-7-768x463.png weighs 534 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.1 MB in 74 requests on a phone: images 1.3 MB (37), media 1.2 MB (1) and fonts 349 KiB (5). Under 2 MB keeps phones on slow connections fast.

5 images (782 KiB) 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.

2 images are downloaded at several times the size a phone draws them, for example 34148a128c123675369cbf7031e7ceaeaf2de50e.png at 390 px wide, shown at 94 px. Resized copies would save about 78 KiB.

4 images further down the page (150 KiB) 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 0.87 g of CO₂e: 104.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

The homepage links to 68 pages on req.co and 3 external pages.

There is no https://req.co/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.

/ and https://req.co/services/creative all use the title “REQ - Digital Marketing Agency for the Branded World”. Search engines can't tell which page to show for a search, so each competes with the others.

https://req.co/about-us, https://req.co/case-studies/carahsoft, https://req.co/case-studies/built-technologies and https://req.co/case-studies/building-a-scalable-federal-content-engine-to-drive-cybersecurity-demand-and-market-visibility have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://req.co/online-reputation-management, whose canonical is https://req.co/services/online-reputation-management. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 15 fields (2 required). Every extra field lowers completion.

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

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

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

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