Colorado Springs · serving the U.S. & Canada Custom-coded. Custom-cared-for.
(928) 315-9094 hello@pikespeakwebdesigns.com Client portal →
How It Works What's Included What I Build For You The Service Site Standard Pricing Return on Investment Service Agreement Sample Websites Sample Forms Technical Approach
Site Grader Lead-Leakage Calculator Free 5-Point Audit Walk-Through Results Status & Performance Public Changelog
vs. Wix vs. Squarespace vs. GoDaddy vs. Webflow vs. WordPress vs. AI Builders vs. Agencies vs. Freelance Dev
View all service areas → Phoenix, AZ Los Angeles, CA Denver, CO Miami, FL Tampa, FL Atlanta, GA Chicago, IL Charlotte, NC Las Vegas, NV Philadelphia, PA Nashville, TN Dallas, TX Houston, TX San Antonio, TX Seattle, WA Calgary, AB Vancouver, BC Toronto, ON Montreal, QC
Blog FAQ Glossary Owner's Guide Public Changelog
About Jon Ajinga Results Status & Performance The Tools I Use Style Guide Accessibility Press & Media Kit Partner Program Partner Agreement Sitemap
Veterans First Responders Medical Personnel
Client Portal Onboarding Content Updates Design Feedback Emergency Support Make A Referral Submit A Testimonial
Discovery Call Quick Question (928) 315-9094 hello@pikespeakwebdesigns.com
Appearance
Start Now Or Start a Conversation
Existing client? Open the Client Portal
Live numbers, not claims

Site status. Verifiable, refreshed every six hours.

The agency's site claims 95 to 100 mobile PageSpeed on every page, and this page is where I prove it. The numbers below are real Google PageSpeed Insights scores, refreshed automatically every six hours from the public PSI API. If any score drops below 90, the corresponding badge below goes red. Boring is the feature.

Live PageSpeed scores

Loading latest run…

Fetching latest scores from /api/pagespeed.json…

Source: pagespeed.web.dev via the Google PageSpeed Insights v5 API. You can run the same audit yourself by pasting any URL into the link above.

How this works

A small Cloudflare Pages Function at /api/pagespeed.json calls the PageSpeed Insights API for the agency's site and every demo site on a schedule. Results are cached at the Cloudflare edge for six hours, which means the badges refresh automatically without blowing through the API's free quota. The frontend reads that JSON and renders the badge grid above.

If something is off, whether a score dropped or a site moved, you will see it on this page within six hours of the change.

Recent ship cadence

The public changelog tracks every substantive change shipped. The number below is auto-derived from the changelog template at every build: 8 entries shipped in the last 30 days. The full history covers 25 ship events across 22 categories.

What this page does NOT track

  • Uptime. Cloudflare Pages reports near-perfect uptime by design (static files behind a global edge), but I do not run a paid synthetic-monitoring service yet. When that ships, the dot grid for the last 90 days will live here.
  • Real-user Core Web Vitals. Cloudflare Web Analytics RUM data is collected but not yet exposed publicly. Adding a client-side dashboard that summarizes 30-day RUM is on the roadmap.
  • Form-submission delivery. Web3Forms is reliable enough that a public uptime page on form delivery would be theatrics. If forms ever fail, the changelog will document it.

What changes when the badge goes red

If any score above drops below 90, I get an email alert from the cron job that runs the same query daily, and the fix tends to land quickly on most business days. A red score is not a marketing problem for me, it is a regression I have to fix in order to honor the Service Site Standard.