DebugBear Change Alert

Performance regression detected on infinitalab.com

● Regression
Project: DebugBear #104066
Detected: 20 Jul 2026
Scope: mobile pages
Prepared by: Baivab, Growth

Summary: A tracking and analytics rollout has been added to the site this week (Google Tag Manager, Amplitude session-replay, Facebook Pixel, plus Font Awesome icons). It is adding significant JavaScript weight to mobile pages and has measurably slowed them down. This works against the mobile performance issues already flagged, mobile just got heavier rather than lighter. Flagging in case the change was not intended for production.

What changed on 20 Jul

Blog Listing · Mobile+637 KB, LCP worse

JavaScript added (+522 KB)

• Google Tag Manager (gtag.js) +186 KB

• Amplitude session-replay plugin +140 KB (new)

• Facebook Pixel (fbevents.js) +103 KB

• Amplitude analytics browser +59 KB (new), plus 2 more

Fonts added (+115 KB)

• Font Awesome brand icons (fa-brands-400.woff2) +115 KB (new)

Impact on load

Largest Contentful Paint10.1s → 14.3s (worse)

Load duration6.4s → 9.9s (worse)

Industry Detail · MobileNew console errors

Two HTTP 429 "Too Many Requests" errors while loading static assets:

• infinitalab.com/_static/

• infinitalab.com custom-css asset

Likely the server rate-limiting its own asset requests, or the test tripped a rate limit. Worth confirming it is not affecting real users.

This week's pattern

The same analytics rollout has been landing across pages over several days:

Date	Page	Change
18 Jul	Material Detail (mobile)	Best Practices 37 → 33, low-resolution images
19 Jul	Services Detail (mobile)	+257 KB JavaScript (Amplitude session-replay)
20 Jul	Blog Listing (mobile)	+637 KB total, LCP 10.1s → 14.3s
20 Jul	Industry Detail (mobile)	New 429 console errors

Recommendation

Confirm the tracking rollout is intended, then load it efficiently. If GTM, Amplitude session-replay and the Facebook Pixel are meant to be live, load them asynchronously and deferred, and reconsider Amplitude session-replay on mobile since it is heavy. Combined with the existing ~1.2 MB mobile JS bundle, these additions push already-slow mobile pages further past acceptable load times. Also investigate the 429 errors on static assets so they do not reach real users.

Source: DebugBear change alerts and lab tests, project 104066 (infinitalab.com), 18-20 Jul 2026. Mobile emulation: Slow 4G, Moto G Power. Lab results vary run to run. See the full DebugBear analysis report for the complete page-by-page breakdown.