Answer Quest sells web design and development, so its own homepage is its first portfolio piece. In Google's phone test that page takes 9.5 seconds to show its main content, against a 2.5 second target, even though the server replies in 45 ms. The delay is not hosting. It is 755 KB of JavaScript on a page with only 228 elements, of which Google Tag Manager alone is 605 KB, plus 562 KB of images and 251 KB of fonts. Desktop scores 83, so the problem shows mainly on phones, where a training manager is most likely to open a link sent by a colleague.
First action
Open the tag container and list every tag in it with the person who last looked at its data.
How to measure it
Mobile Largest Contentful Paint (lab)
- Now
- –
- Target
- Under 2.5 seconds
- By
- 30 days
Steps
Record the baseline
Save the current PageSpeed mobile and desktop reports for the homepage and the contact page as PDFs.
Web developer 1 hour
Audit the tag container
List each tag, what it measures and who uses it. Remove anything nobody reads; 605 KB for a brochure page means unused tags.
Web developer half a day
Delay what remains
Load the remaining measurement script after the page is interactive, or on first scroll or click.
Web developer half a day
Fix the images
Resize to the displayed size, convert to a modern format and lazy-load anything below the first screen.
Web developer half a day
Slim the fonts
Keep two weights, host them on the site and preload the one used in the hero text block.
Web developer 2 hours
Unlock zoom and tidy headings
Remove the zoom limit from the viewport tag, put headings in order and enlarge tap targets in the menu.
Web developer 2 hours
Re-test and publish
Run PageSpeed again, and write a short before-and-after case study with both report links.
Owner 1 day
Why it works
Treat the homepage as a one-week client project. Strip the tag container back to the single measurement tool the firm actually reads, load it after the page is usable, compress and resize the hero and logo images, serve two font weights from the site itself instead of six font requests, and remove the pinch-zoom lock. Re-test on PageSpeed after each change and keep a before-and-after record. When the mobile score is above 90, publish the record as the first web design case study: the firm's own site, with numbers a prospect can check for themselves.
Google estimates about 2.6 seconds of saving from unused JavaScript and 1.3 seconds from image delivery on this page, so most of the gap is covered by two fixes. A web design buyer can run the same public test on a supplier's site in a minute, and a fast, checkable result is proof that needs no client permission to publish.
Ready to use
ChecklistHomepage speed checklist
[ ] Baseline PageSpeed reports saved (mobile and desktop) [ ] Tag container audited; unused tags removed [ ] One measurement tool kept, loaded after interaction [ ] Hero and logo images resized and converted [ ] Two font weights, self-hosted, hero font preloaded [ ] Viewport zoom limit removed [ ] Headings in order; menu tap targets enlarged [ ] Mobile main content under 2.5 seconds in the lab test [ ] Before-and-after case study published
Risks and how to handle them
Removing a tag breaks reporting someone relies on
Export the container first and pause tags for a week before deleting them.
Lab numbers differ from what real visitors see
Google has no field data for the site yet, so also test on a mid-range phone over mobile data.
Evidence
- PageSpeedGoogle PageSpeed lab test of the homepage (November 15, 2026): mobile performance 64 out of 100, desktop 83. On the simulated phone the main content (the hero text block) takes 9.5 seconds to appear against Google's 2.5 second target, although the server answers in 45 ms. The page weighs 1,612 KB in 33 requests: 755 KB of JavaScript, 562 KB of images and 251 KB of fonts. Estimated savings: about 514 KB of unused JavaScript (2.6 seconds) and about 305 KB from image delivery (1.3 seconds). Google holds no real-visitor data for this site, so these are lab numbers only.Source
- PageSpeedThird-party load on the homepage (PageSpeed, November 15, 2026): Google Tag Manager accounts for 605 KB across 4 requests and 316 ms of blocking time; Google Fonts adds 161 KB in 6 requests. Three measurement tools were detected (Google Analytics, Google Tag Manager and Matomo) on a page with only 228 elements.Source
- PageSpeedPageSpeed accessibility score 90 out of 100 with three flagged issues: the viewport tag disables or limits pinch-zoom, headings are not in sequential order, and touch targets are too small or too close together. SEO and best-practices scores are both 100.Source
- Search resultsPages of answerquest.com shown in web search (November 16, 2026): Welcome, Contact, Student Files, Microsoft Office: Word Training, Microsoft Office: Outlook Training and four legal pages. The homepage snippet lists expert technical writing, comprehensive training programs, and state-of-the-art web design and development services, and says the firm serves clients beyond Baltimore and the Mid-Atlantic region across the United States. Search summaries also mention web maintenance and WordPress consulting. No separate page for technical writing, web design, instructional design or soft-skills training appeared in the results.Source