How to Improve Page Load Speed

𝗛𝗼𝘄 𝗪𝗲 𝗔𝗰𝗵𝗶𝗲𝘃𝗲𝗱 𝗮 𝗣𝗲𝗿𝗳𝗲𝗰𝘁 100/100 𝗣𝗮𝗴𝗲 𝗦𝗽𝗲𝗲𝗱 𝗳𝗼𝗿 𝗮 ₹1000𝗖𝗥+ 𝗔𝗥𝗥 𝗲𝗖𝗼𝗺𝗺𝗲𝗿𝗰𝗲 𝗕𝗿𝗮𝗻𝗱 The secret sauce? 𝗚𝗼𝗼𝗴𝗹𝗲 𝗧𝗮𝗴 𝗠𝗮𝗻𝗮𝗴𝗲𝗿 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻. Here’s the exact breakdown of how we did it - 1️⃣ 𝗟𝗮𝘇𝘆 𝗟𝗼𝗮𝗱𝗶𝗻𝗴 𝗦𝗰𝗿𝗶𝗽𝘁𝘀: We delayed non-essential scripts like chat tools and behavioral tracking until after the page loaded or user interaction, ensuring faster access to key elements, drastically improving user experience. 2️⃣ 𝗥𝗲𝗱𝘂𝗰𝗲𝗱 𝗦𝗰𝗿𝗶𝗽𝘁 𝗩𝗼𝗹𝘂𝗺𝗲: By removing unnecessary third-party scripts, we lightened the page, significantly improving overall speed and making the site more responsive. E.g. Remove the scripts of tools that we don't need anymore 3️⃣ 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿 𝗔𝗹𝗶𝗴𝗻𝗺𝗲𝗻𝘁: We collaborated with marketing, sales, and product teams to schedule tools like user behavior tracking once the page load is complete. 4️⃣ 𝗜𝗻𝗹𝗶𝗻𝗲 𝗖𝗼𝗱𝗶𝗻𝗴 𝗳𝗼𝗿 𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗦𝗰𝗿𝗶𝗽𝘁𝘀: Working with our tech team, we inlined long-term critical scripts. This helped in speeding up the First Contentful Paint to just a few seconds, giving users immediate access to key visuals. 5️⃣ 𝗧𝗮𝗴 𝗦𝗲𝗾𝘂𝗲𝗻𝗰𝗶𝗻𝗴 & 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻: The game-changer! Only the most critical tags, like conversion tracking, fired on page load. Marketing tags such as retargeting were delayed, significantly improving both speed and user engagement. 6️⃣ 𝗣𝗮𝘂𝘀𝗲𝗱 𝗨𝗻𝘂𝘀𝗲𝗱 𝗧𝗮𝗴𝘀: We paused tags that no longer contributed to key decision-making, reducing time-to-interactive and directly improving conversion rates by speeding up the user journey. 7️⃣ 𝗦𝗺𝗮𝗿𝘁𝗲𝗿 𝗧𝗮𝗴 𝗧𝗿𝗶𝗴𝗴𝗲𝗿𝘀: We set triggers to fire tags only based on specific user actions, which not only saved load time but also increased session duration, as users interacted more fluidly with the site. 8️⃣ 𝗖𝗼𝗺𝗽𝗿𝗲𝗵𝗲𝗻𝘀𝗶𝘃𝗲 𝗧𝗲𝘀𝘁𝗶𝗻𝗴: Every new script was rigorously tested before launch, ensuring peak performance and zero downtime, even during high-traffic periods. 9️⃣ 𝗥𝗼𝘂𝘁𝗶𝗻𝗲 𝗔𝘂𝗱𝗶𝘁𝘀: Regular audits every few months allowed us to remove obsolete tags, keeping performance sharp and maintaining the high page speed we achieved. 𝗞𝗲𝘆 𝘁𝗮𝗸𝗲𝗮𝘄𝗮𝘆 - Effective management of Google Tag Manager can boost conversions by up to 30% and improve page speed score by up to 20 points, boosting both user experience and bottom-line revenue. I'd love to hear your experiences and insights on leveraging GTM for page speed optimization. How has GTM transformed your marketing operations and contributed to better user experiences? . . Also a big shoutout to Gunjan Agrawal and Mandar Zope for their awesome contributions in making this happen!. . . #GrowthInsights #GoogleTagManager #PageSpeedOptimization #UserExperience #ConversionOptimization

I spent 17 hours optimizing an API endpoint to make it 15x faster. Here's a breakdown of what I did. One endpoint was crunching some heavy numbers. And it wasn't scaling well. The endpoint needed data from several services to perform the calculations. This is the high-level process I took: - Identify the bottlenecks - Fix the database queries - Fix the external API calls - Add caching as a final touch 𝗦𝗼, 𝗵𝗼𝘄 𝗱𝗼 𝘆𝗼𝘂 𝗶𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝘁𝗵𝗲 𝗯𝗼𝘁𝘁𝗹𝗲𝗻𝗲𝗰𝗸𝘀 𝗶𝗻 𝘆𝗼𝘂𝗿 𝘀𝘆𝘀𝘁𝗲𝗺? You will know what to fix if you know the slowest piece of code. The 80/20 rule works wonders here. Improving 20% of the slowest code can yield an 80% improvement. The fun doesn't stop here. Performance optimization is a continuous process and requires constant monitoring and improvements. Fixing one problem will reveal the next one. The problems I found were: - Calling the database from a loop - Calling an external service many times - Duplicate calculations with the same parameters Measuring performance is also a crucial step in the optimization process: - Logging execution times with a Timer/Stopwatch - If you have detailed application metrics, even better - Use a performance profiler tool to find slow code 𝗙𝗶𝘅𝗶𝗻𝗴 𝘀𝗹𝗼𝘄 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗾𝘂𝗲𝗿𝗶𝗲𝘀 A round trip between your application and a database or service can last 5-10ms (or more). The more round trips you have, the more it adds up. Here are a few things you can do to improve this: - Don't call the database from a loop - Return multiple results in one query 𝗖𝗼𝗻𝗰𝘂𝗿𝗿𝗲𝗻𝘁 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝗶𝘀 𝘆𝗼𝘂𝗿 𝗳𝗿𝗶𝗲𝗻𝗱 I made multiple asynchronous calls to different services, which were independent of each other. So, I called these services concurrently and aggregated the results. This simple technique helped me achieve significant performance improvement. 𝗖𝗮𝗰𝗵𝗶𝗻𝗴 𝗮𝘀 𝗮 𝗹𝗮𝘀𝘁 𝗿𝗲𝘀𝗼𝗿𝘁 Caching is an effective way to speed up an application. But it can introduce bugs when the data is stale. Is this tradeoff worth it? In my case, achieving the desired performance was critical. You also have to consider the cache expiration and eviction strategies. A few caching options in ASP .NET: - IMemoryCache (uses server RAM) - IDistributedCache (Redis, Azure Cache for Redis) In distributed systems, you can use OpenTelemetry to diagnose performance bottlenecks. Here's how: https://lnkd.in/eWr2ifKc What do you think of my process? Would you do something differently? --- Do you want to simplify your development process? Grab my free Clean Architecture template here: https://bit.ly/4ef3LuR Source: Milan Jovanović

Yesterday, an e-commerce client asked how to increase site speed without losing their marketing tracking. Here's our approach. This client is a $100M+ online retailer with a complex channel mix. Thus, they have lots of marketing pixels onsite. Our recommended approach: 1.) Remove libraries and pixels no longer needed. Audit your existing pixels and events. Disable any pixels/events that are no longer needed. Check for errors and fix any broken pixels. 2.) Tag Managers Move all 3rd party javascript (libraries/pixels) into a tag manager. Tools like GTM, Tealium, Adobe Launch benefit primarily help with data governance and standardization. However, tag managers can also minify and cache 3rd party libraries, reducing page load times. Additionally, they often have OOTB capability to set the priority (sequence) of the tags, more on this below. 3.) Server-side tagging Many ad platforms can receive events server-side vs. clientside (through javasript in the browser). Examples include Meta, Google, TikTok. This can take some of the load off the browser. There are good 3rd party tools for this, including Blotout and Elevar. Server-side tracking has the added benefit of restoring signal to the ad platforms. More conversions to the ad platform will result in better optimization and reduced ad spend. 4.) Sequencing Less-important libraries This is a biggie. If pixels aren't required for the page render, have your web-dev team defer them later in the page. This can also be done in the tag manager. Most tag managers load tags asynchronously by default. That means they load in parallel and won't block other resources from loading. Full-service performance optimization tools like Yottaa can automatically sequence the libraries and calls (very good but not cheap). In summary, I'd tackle in this order: - Remove any pixels/libraries you no longer use/need - Move all 3rd party pixels to a tag manager (GTM) - Fix broken pixels - Optimize the load order of the libraries (sequencing) - Setup server-side tracking for ad platforms if available What else would you add? #measure #digitalanalytics #marketinganalytics #ecommerce

Slashed a Webflow site's load time from 6.2s to 1.8s Client's reaction: "How did you do this without rebuilding?" The secret? 5 unconventional optimizations. Here's the full breakdown 👇 The site was beautiful but slow. Killing their Google rankings. And losing mobile visitors. The unexpected culprits: → Oversized background images → Unoptimized CMS queries → Multiple font families → Heavy custom code → Nested interactions Here's exactly what we did: 1. Images: → Converted to AVIF → Added lazy loading → Removed unused assets 2. Interactions: → Combined similar ones → Used CSS where possible → Removed scroll-based triggers 3. Code cleanup: → Removed jQuery dependencies → Merged custom scripts → Minified everything The results shocked everyone: → Mobile speed: 1.8s → Core Web Vitals: All green → Mobile conversions: +27% → Bounce rate: -41% Best part? No design changes are needed. Want the same speed gains? DM "Speed Check" for a FREE performance audit. I'll show you exactly what's slowing your site. #webflow #webperf #webdesign #ux ___ Sebastian Bimbi here, your go-to Web-dev. Daily tips & behind-the-scenes. Follow for Webflow mastery. Got questions? Ask below!

Brain Boost Drop #15 𝗪𝗵𝘆 𝗗𝗼 𝗪𝗲𝗯𝘀𝗶𝘁𝗲𝘀 𝗟𝗼𝗮𝗱 𝗦𝗹𝗼𝘄𝗹𝘆? – 𝗕𝗿𝗲𝗮𝗸𝗶𝗻𝗴 𝗗𝗼𝘄𝗻 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗕𝗼𝘁𝘁𝗹𝗲𝗻𝗲𝗰𝗸𝘀 I can’t count how many times I’ve been asked, “Why is our site so slow?” Over the years, I’ve worked on debugging countless performance issues — and in most cases, it wasn’t just one thing slowing things down. It was a combination of small bottlenecks adding up. Here are 10 common reasons websites load slowly—plus simple fixes that make a huge difference. 1️⃣ Large or Unoptimized Media Files – Compress images, use WebP or next-gen formats. 2️⃣ Too Many HTTP Requests – Combine files, use CSS sprites, and reduce plugins. 3️⃣ Inefficient Code & Scripts – Minify, defer non-critical code, and eliminate unused scripts. 4️⃣ No Caching Strategy – Implement browser or server-side caching for frequently accessed assets. 5️⃣ No CDN in Place – Use a Content Delivery Network to reduce latency. 6️⃣ Slow Server Response Time – Optimize backend queries, upgrade hosting, and implement load balancing. 7️⃣ Unoptimized Third-Party Scripts – Load asynchronously or defer until after page load. 8️⃣ Not Mobile-Optimized – Use responsive design and test for mobile performance. 9️⃣ Render-Blocking Resources – Prioritize critical CSS/JS, defer the rest. 🔟 Too Many Redirects – Fix broken links and reduce unnecessary hops. These bottlenecks are easy to miss but powerful to fix. Even one or two changes can transform user experience and reduce bounce rates. 💬 What’s the most common performance issue you’ve encountered in your projects? #WebPerformance #FrontendDevelopment #WebsiteOptimization #DeveloperInsights

4 years ago, eBay noticed something strange: Whenever they increased website speed by 100 milliseconds, “Add To Cart” count jumped by 0.5% So eBay started on a mission to make their website as fast as possible. Here’s what they did👇👇 1. 𝗥𝗲𝗱𝘂𝗰𝗲𝗱 𝗨𝗻𝗻𝗲𝗰𝗲𝘀𝘀𝗮𝗿𝘆 𝗖𝗼𝗱𝗲: They trimmed down unnecessary parts of the code used on their website, like JavaScript, CSS, HTML, and JSON. They used to add more and more code for new features, even if it wasn't needed, but they learned to clean up unused code to make things faster. 2. 𝗙𝗼𝗰𝘂𝘀𝗲𝗱 𝗼𝗻 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗖𝗼𝗻𝘁𝗲𝗻𝘁: They made sure that the most important content that users see right away loads quickly. They optimized the way data is fetched and displayed for the critical parts of the page that users see first. 3. 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗲𝗱 𝗜𝗺𝗮𝗴𝗲𝘀: Images can slow down a website, so eBay improved their images. They used a better image format, WebP, and made sure all images were properly optimized in size. This made the site faster to load. 4. 𝗣𝗿𝗲𝗱𝗶𝗰𝘁𝗲𝗱 𝗪𝗵𝗮𝘁 𝗨𝘀𝗲𝗿𝘀 𝗪𝗶𝗹𝗹 𝗗𝗼: They made their website smarter by predicting what users are likely to do next. This allowed them to load some of the necessary parts of the next page before users even click, so the page loads faster. 5. 𝗣𝗿𝗲𝗹𝗼𝗮𝗱𝗲𝗱 𝗧𝗼𝗽 𝗦𝗲𝗮𝗿𝗰𝗵 𝗥𝗲𝘀𝘂𝗹𝘁𝘀: They guessed which items users are likely to click on when they search, and they loaded those items in advance. This reduced the time it takes for users to see the search results they're interested in. 6. 𝗖𝗮𝗰𝗵𝗲𝗱 𝗦𝘂𝗴𝗴𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗮𝗻𝗱 𝗖𝗼𝗻𝘁𝗲𝗻𝘁: They saved certain information in a cache so they don't need to fetch it every time a user types something. This saved time and made suggestions and content load faster. All these improvements, even the small ones, added up over time to make eBay's website faster. As the wise man once said: Faster experiences make users happier. Follow Pratik Daga

If your landing page takes longer than 3 seconds to load, fix these 3 things. (3 secs is the standard before a user bounces) 1) Bloated scripts: Every plugin, tool, script or unnecessary line of code you run on your website adds "weight". The more it carries, the slower it will load. 2) Huge images: Resize and compress or use next-gen formats. Pro tip: Your CDNs should automagically have a way to turn all the images on your website to a next-gen format and have it load faster. It's a matter of a setting. Ask your dev about it. 3) Lazy-load what isn’t critical. After you assess your scripts from step 1, maybe there's an important script but it doesn't need to load right away. Ex. Your chatbot. Have it load a little later. This makes the most critical scripts run first and then loads the rest, making your website load fast. --- If you want to see what's slowing your website down, run a Lighthouse test (Google it or run it in Inspect on Chrome). It will give you a pretty detailed report for free. Fix the technical debt. Then worry about your hero headline. Because if the page doesn't load fast enough, it doesn't matter if you have the best-written website on the planet.