represent.us website review

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

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

YouTube costs a phone 1.2 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 3.3 MB and 2.8 s of main-thread time.

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

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

Facebook costs a phone 384 ms of main-thread work and 267 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.

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

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

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

17 KiB could be saved by minifying JavaScript.

About 79 KiB of CSS is downloaded but never applied on this page.

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.

Real visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE CORRUPTION IS REAL. BUT WE WON’T STAND FOR IT. A mafia-…”.

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

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

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

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 6.1 MB in 149 requests on a phone: scripts 3.3 MB (65), images 2.1 MB (19) and fonts 346 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

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

All page content should be contained by landmarks: 47 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.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

9 elements hidden from screen readers can still receive keyboard focus.

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

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

The homepage links to 39 pages on represent.us and 28 external pages.

There is no https://represent.us/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://represent.us/donate and https://represent.us/resource-library are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://represent.us/events, whose canonical is https://represent.us/upcoming-events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://represent.us/our-strategy, https://represent.us/financials, https://represent.us/courage, https://represent.us/trump-corruption-tracker, https://represent.us/explains and https://represent.us/volunteer have no <h1> headline, so visitors and search engines get no clear main topic.

https://represent.us/events took over 3 s to send its HTML from our server.

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

7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Invalid regular expression: missing /”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage has only about 233 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap 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 20 cookies, 1 of them by other companies (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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.