republicservices.com website review

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

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

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

1 long task block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.

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

1 image could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

3 third-party services load with your homepage (site.com, Google Fonts and FontAwesome CDN), adding 70 KiB and 1 ms of main-thread time.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.69 (75th percentile). Good is under 0.1.

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Enter your address to shop services in your area”. Most of its time is element render delay (3.3 s).

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

1 button has no accessible name, so screen readers announce just “button”.

ARIA commands must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 60 pages on republicservices.com and 11 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 https://www.republicservices.com/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.

https://www.republicservices.com/service-alerts, https://www.republicservices.com/schedule, https://www.republicservices.com/payment/bulk-waste/bulk-request-details, https://www.republicservices.com/blog, https://www.republicservices.com/blog/how-can-small-businesses-be-eco-friendly-waste and https://www.republicservices.com/blog/our-elements-of-sustainability and 1 other all use the title “Republic Services”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.republicservices.com/service-alerts, https://www.republicservices.com/schedule, https://www.republicservices.com/payment/bulk-waste/bulk-request-details, https://www.republicservices.com/blog, https://www.republicservices.com/blog/how-can-small-businesses-be-eco-friendly-waste and https://www.republicservices.com/blog/our-elements-of-sustainability and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.republicservices.com/service-alerts, https://www.republicservices.com/schedule, https://www.republicservices.com/sustainability, https://www.republicservices.com/about-us, https://www.republicservices.com/payment/bulk-waste/bulk-request-details and https://www.republicservices.com/blog and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.republicservices.com/service-alerts, https://www.republicservices.com/schedule, https://www.republicservices.com/blog, https://www.republicservices.com/blog/how-can-small-businesses-be-eco-friendly-waste, https://www.republicservices.com/blog/our-elements-of-sustainability and https://www.republicservices.com/blog/fulfilling-our-community-promises 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 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://republicservices.my.site.com/ESWRepublicServicesEmbe1732604657666/assets/styles/bo…”.

Social proof on the homepage: 3 customer or partner logos. 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.

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

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

Before a visitor clicks anything, the page loads Meta Pixel (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 11 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.