Real visitors to mankowindowsystems.com fail Google's Core Web Vitals: the server takes about 3 seconds before it sends anything, the main content needs nearly 4 seconds, and it has got 45% slower. The cause is visible in the response headers: the site already runs behind Cloudflare, but every page is marked "DYNAMIC" and built from scratch by WordPress, so no visitor ever gets a cached copy. An architect checking 450 Series details on a phone, or a glazier opening a spec between bids, waits on each page.
First action
Add a Cloudflare cache rule for HTML on a test page and compare first-byte time.
How to measure it
Field LCP
- Now
- –
- Target
- Under 2.5s (passing)
- By
- 60 days
Steps
Measure
First-byte time on five key pages.
Website Administrator 1 hour
Turn on caching
Cloudflare APO or an HTML cache rule.
Website Administrator 2 hours
Exclude forms
Contact, AIA, employment pages bypass cache.
Website Administrator 1 hour
Add purge
Cache plugin clears on publish.
Website Administrator 1 hour
Defer scripts
Unused Elementor add-ons per page.
Website Administrator 1 day
Re-test
PageSpeed on home, 450 and 250 pages.
Website Administrator 1 day
Watch field data
Search Console Core Web Vitals.
Website Administrator monthly
Why it works
Turn on full-page caching: Cloudflare's WordPress page cache (APO) or a cache rule for HTML with bypass for logged-in users and forms, plus a WordPress cache plugin that purges on publish. Then remove the render-blocking CSS and scripts Google flags (about 6 seconds in the mobile test) by deferring Elementor add-on scripts not needed on each page. Re-test the homepage, a storefront page and a curtain wall page.
Cached pages typically arrive in a fraction of a second, which fixes the field measure Google uses in search ranking and makes the site feel as solid as the products. Specifiers browse several product pages per visit, so every second saved repeats on each click.
Ready to use
ChecklistPage cache rollout
[ ] Baseline first-byte time: home, 450, 250/250x, EntryGuard, Find a Rep [ ] Cloudflare APO (or Cache Everything rule for HTML) [ ] Bypass: /contact/, /aia/, /employment-application/, /manko-cdl-application/, logged-in users [ ] Purge on publish via cache plugin [ ] Defer non-critical Elementor add-on scripts [ ] Re-test PageSpeed mobile and desktop [ ] Check Core Web Vitals in Search Console after 28 days
Risks and how to handle them
Forms or the rep map break when cached
Exclude those pages and test each form after the change.
Stale pages after updates
Purge on publish and set a short cache lifetime for HTML.
Evidence
- Google PageSpeedHomepage: real Chrome visitors fail Core Web Vitals on loading: the main content takes 3.96s to appear (LCP; the limit is 2.5s) and the server takes 3.06s before sending the first byte (TTFB); LCP has got 45% slower over the trend period. In the mobile lab test the hero headline appears at 12.2s, with 2.2 MB over 134 requests; render-blocking requests cost about 6.1s. Desktop scores 74, mobile 53.Source
- Site checkResponse headers (checked October 20, 2026): pages are served through Cloudflare with "cf-cache-status: DYNAMIC" and "x-cache: MISS", so every page view is built by the WordPress server; the homepage took about 2.4s to send its first byte in repeated requests, and the 450 Series storefront page about 1.8s.Source
- Your websiteProduct pages (for example 450 Series storefront) offer a brochure, specifications in PDF and DOC (revised January 2026), standard and accessory details as PDF and DXF, installation, maintenance and warranty documents; curtain wall pages add dead load and wind load charts. No Revit or BIM files are offered.Source