cycleoregon.com website review

21 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.6 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Mapbox and others), adding 1.1 MB and 596 ms of main-thread time.

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

61 KiB could be saved by minifying JavaScript.

29 KiB could be saved by minifying CSS.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

Your largest element takes 38.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A MOVEMENT FOR OREGON THE CYCLE OREGON FOUNDATION DETAILS”.

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

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

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

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

14 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-31, real Chrome visitors' tap response (inp) went from 88 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.6 MB in 113 requests on a phone: images 6.0 MB (25), scripts 1.3 MB (43) and stylesheets 164 KiB (27). Under 2 MB keeps phones on slow connections fast.

17 images (3.4 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.

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

12 images are downloaded at several times the size a phone draws them, for example Cycle_Oregon_GRAVEL_2026_Event_Page_Carosuel_1-1200x600.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 138 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

4 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 12 characters: “Cycle Oregon”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 58 pages on cycleoregon.com and 5 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.

/our-work/our-impact, /about/staff-board, /first-ride-fundraiser, /about/volunteer and /community-of-giving have no meta description, so Google writes the search snippet from whatever text it finds.

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

37 of 86 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 “Cannot read properties of null (reading 'getAttribute')”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example http://www.facebook.com/CycleOregon.

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.

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

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

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

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

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be cycleoregon.com is still delivered. Add a report address, check the reports, then move to quarantine.

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