Together's homepage leads with "Faster inference 2x", yet Google's Chrome data shows real visitors wait 4.5 s for the main content and 236 ms for taps, failing both tests, and the site has slowed 39% in a year. The page is 5.2 MB, and 2.7 MB of that comes from 22 third-party services; Google Tag Manager alone blocks the browser for about a second. The new ABM & Campaign Manager becomes the business owner of the demand gen and ABM stack and will add more landing pages and tests, so this is the moment to set a budget before more tags go on.
First action
Export the Google Tag Manager container and list every tag with its owner and last use.
How to measure it
Homepage LCP for real visitors
- Now
- –
- Target
- under 2.5 s
- By
- 60 days
Steps
List tags
Every tag, owner and purpose.
GTM Engineer 2 days
Cut and delay
Remove unused tags; load the rest after interaction.
GTM Engineer 1 week
Trim JavaScript
Drop unused scripts and heavy embeds from the homepage.
Webflow developer 1 week
Cache and lazy-load
Long cache lifetimes; load lower sections on scroll.
Webflow developer 3 days
Set a budget
Page weight and third-party limits for new pages.
Senior ABM & Campaign Manager 1 day
Re-test
PageSpeed now, Chrome UX Report after 28 days.
Webflow developer 1 month
Measure
Landing-page conversion before and after.
Marketing Operations monthly
Why it works
Audit every tag in Google Tag Manager with the GTM Engineer: keep one analytics tool, one ad pixel per network and the ABM tools that feed Salesforce, and remove or delay the rest until after the page is interactive. Ship the homepage with only the JavaScript it uses (936 KB is unused), set long cache lifetimes on Webflow assets, and load the model grid and research cards when they scroll into view. Set a performance budget (for example 1.5 MB and under 10 third parties on landing pages) that every new campaign tool must fit. Re-run PageSpeed and watch the Chrome UX Report for 28 days.
Developers judge an infrastructure company by how its own site performs, and slow pages lose paid and ABM traffic before it converts. The fix mostly removes things, so it is cheap and lifts every campaign at once.
Ready to use
ChecklistHomepage speed checklist
[ ] Export the Tag Manager container; list every tag with owner [ ] One analytics tool, one pixel per ad network [ ] Delay non-essential tags until after interaction [ ] Remove unused JavaScript (936 KB flagged) [ ] Long cache lifetimes on site assets [ ] Lazy-load model grid and research cards [ ] Budget: 1.5 MB, fewer than 10 third parties per landing page [ ] Re-run PageSpeed; check Chrome UX Report after 28 days
Risks and how to handle them
Removing a tag breaks attribution
Check each tag's reports with its owner before removal.
Webflow limits
Move heavy widgets to lightweight embeds or load them on demand.
Evidence
- PageSpeed testGoogle PageSpeed for the together.ai homepage (October 21, 2026). Real Chrome visitors (Chrome UX Report, 75th percentile): main content appears in 4.5 s and taps respond in 236 ms, so the page fails Core Web Vitals on load and responsiveness (good is 2.5 s and 200 ms); site-wide, time to main content is 2.9 s and 39% slower than a year ago. Lab test on mobile: performance score 34, 5.2 MB and 193 requests, 2.7 MB of it from 22 third-party services; Google Tag Manager alone is 856 KB and blocks the main thread for about 1 s; 936 KB of JavaScript is unused.Source
- Your websiteHomepage (October 21, 2026): "Build what's next on the AI Native Cloud"; headline claims "Faster inference 2x", "Lower cost 60%" and "Faster pre-training 90%"; banners for Together Post-Training, Together Link and on-demand B200s. The homepage model grid leads with Kimi K3, Qwen3.8 and GLM-5.3, while the Model Shaping menu still features Kimi K2.7 Code, GLM 5.1 FP4 and Llama 4 Maverick.Source
- HiringSenior ABM & Campaign Manager (Demand Generation, San Francisco, posted September 8, 2026): owns ABM and integrated campaigns for "AI-native and digital-native companies running inference at scale"; runs "continuous testing and experimentation across channels — from ad creative and landing pages to targeting and channel mix"; is "the business owner of our demand gen and ABM stack" with RevOps; owns "account penetration and pipeline contribution against new logo goals".Source
- HiringRevenue systems and sales: a GTM Engineer to build "signal-based workflows", "dynamic scoring models" and "centraliz[e] selling signals from multiple data sources" across Salesforce, HubSpot, Snowflake and Clay, and lead Salesforce CPQ; a Sales Development Engineer to "Convert users of the Together platform to broader commercial opportunities alongside Account Executives"; Strategic Account Executives in San Francisco, New York and London (EMEA inference).Source