> Canonical URL: https://codingcat.dev/post/better-performance-through-analysis

# Better Performance through analysis

✏️ Blog PostAugust 17, 2019[![](/logos/firebase/firebase-symbol.png)![](/logos/firebase/firebase-symbol.png)Firebase](/topic/firebase)[#DevOps](/topic/devops)[#AI & Agents](/topic/ai)[![](/logos/tags/github-symbol-light.svg)![](/logos/tags/github-symbol-dark.svg)GitHub](/topic/github)[#Security](/topic/security)

# Better Performance through analysis

![CodingCat.dev tutorial cover image](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/df6dd08d0bb9e547c94b914020c41dcb4bdef7bf-1920x1080.png?w=1920&q=82&fit=max&auto=format)[![Alex Patterson](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/a606dfaa381aab08ddbe16a33fe1d3e1fb37c927-400x400.jpg?w=96&h=96&q=82&fit=max&auto=format)Alex Patterson](/author/alex-patterson)

> Please note I wrote this on my phone driving 6 hours, so I hope to update in more detail. Fun fact I now know how to do git remote recursive from Android ????

The current web standard for initial page load is 2.0 seconds. This is only part of the performance story. Let's dive in a little deeper and see how else we can improve performance. In terms of data reduction and user experience, sometimes these things are not as noticeable.

## Web.dev

[Web.dev learning](https://web.dev/learn) is one of the best sources to increase performance on your site.As you can see in the video, they have several subjects to help improve your sites performance.I actually find myself using the [measure](https://web.dev/measure) feature prior to diving into the learning section. But I never was good at "hitting the books" in school, I am a visual hands on learner ????.It is nice to repeat the lighthouse metrics to see what you have learned and the trends over time.

![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/a2b11ab1345d90eb31b39b08448388b8d9f1309f-1080x1913.jpg?w=1080&q=82&fit=max&auto=format)

## Firebase performance monitoring

Firebase Performance Monitoring [docs](https://firebase.google.com/docs/perf-mon) have the best information possible. With that said there are three key elements:

- Automatically measure app startup time, HTTP/S network requests, and more
- Gain insight into situations where app performance could be improved
- Customize Performance Monitoring for your app

The awesome part of Firebase is that it is a very small amount of code that gives you all of this great info!Here you can see a great overview

![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/3472870be187d6ab01d370a93d604ab56fe772ef-1152x2048.jpg?w=1152&q=82&fit=max&auto=format)

You can see all the pages and how many samples determine the average performance.

![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/c584140af13e11d8e02620a4711f71553aceec1e-1459x2048.jpg?w=1459&q=82&fit=max&auto=format)

## Why 2 seconds

Google ranks search results higher based on many inputs to the algorithm, speed is one of the most important factors! Now if you want to go beyond that checkout [Google's Performance blog](https://developers.google.com/web/fundamentals/performance/why-performance-matters/).

## User perception matters

You really need to make all pages feel like less than one second, why? Humans can't perceive things much faster than one second, but past that they start to think things are wrong. Google cares about the user and uses the [RAIL method](https://developers.google.com/web/fundamentals/performance/rail).

- **Response** - How quickly browser reacts
- **Animation** - effects that make a site look good
- **Idle** - Settling down so browser does not have to process
- **Load** - How quick does this page load

## Additional tools

As Google's post points out [Chrome DevTools](https://developers.google.com/web/fundamentals/performance/rail#devtools) The developer tools built into Google Chrome. Provides in-depth analysis on everything that happens while your page loads or runs. [Lighthouse](https://developers.google.com/web/fundamentals/performance/rail#lighthouse) Available in Chrome DevTools, as a Chrome Extension, as a Node.js module, and within WebPageTest. You give it a URL, it simulates a mid-range device with a slow 3G connection, runs a series of audits on the page, and then gives you a report on load performance, as well as suggestions on how to improve. Also provides audits to improve accessibility, make the page easier to maintain, qualify as a Progressive Web App, and more. [WebPageTest](https://developers.google.com/web/fundamentals/performance/rail#webpagetest) Available at webpagetest.org/easy. You give it a URL, it loads the page on a real Moto G4 device with a slow 3G connection, and then gives you a detailed report on the page's load performance. You can also configure it to include a Lighthouse audit.

## Difference on what you test

If the majority of your users are on desktop, you probably care more about testing for desktop. However, if you are looking to build a broader user base, especially in developing world's, you better check low end mobile results!

### Desktop for AJonP

I try to get an all A rating, but this shows even smaller items that you can fix.

![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/8b539dc9c54c469feca97bf62f0a53c9b1149276-1080x2160.png?w=1080&q=82&fit=max&auto=format)

It allows you to really dig down into the details.

![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/1ceedd84ec1bf1d24459d362acd3326c6bbc6393-1080x2160.png?w=1080&q=82&fit=max&auto=format)

### Mobile low-end for AJonP

An example where I can improve performance still on low end devices.

![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/7c6cd959ffa934ece8939c182573f193ed689a02-1080x2160.png?w=1080&q=82&fit=max&auto=format)![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/18272bb33f1aea05189e3dc9082471508f68d1b1-1080x2160.png?w=1080&q=82&fit=max&auto=format)

## Resources, Links & Official Documentation

- [**Firebase Documentation:**](https://firebase.google.com/docs) Firestore, Data Connect, Authentication, App Check, and Cloud Functions
- [**GitHub Actions CI/CD Documentation:**](https://docs.github.com/en/actions) Automated deployment pipelines, secrets management, and runners

## Related CodingCat.dev Tutorials & Podcast Episodes

- [**What the F*ck is Firebase Now?**](/post/what-the-f-ck-is-firebase-now): The Firebase platform is evolving with a focus on generative AI, deeper integration with Google Cloud, and enhanced web development capabilities, requiring deve...
- [**Firebase Multisite Hosting**](/post/firebase-multisite-hosting): Creation of multiple sites within Hugo (main and amp), as well as multiple sites written in Angular (admin and app).
- [**5 ways to use Gemini text-to-speech (TTS) in your apps with Firebase AI Logic: Web Architecture & Implementation Guide**](/post/firebase-2026-09-ai-logic-text-to-speech): Hands-on web engineering breakdown of "5 ways to use Gemini text-to-speech (TTS) in your apps with Firebase AI Logic" (2026-09-09). Learn how to integrate Fireb...

## Frequently Asked Questions (FAQ)

### What are the main takeaways from Better Performance through analysis?

Example of how to use Web.dev to maintain a timeline of performance, while running firebase performance for constant monitoring. Better Performance through analysis explores practical patterns for Firebase, DevOps in modern software engineering. Throughout this post, Alex Patterson breaks down real-world implementation details for Firebase, DevOps so developers can apply these patterns directly in production.

### How do you implement Firebase best practices in production?

When adopting Firebase and DevOps in a production stack, start by validating your configuration against the [**Firebase Documentation**](https://firebase.google.com/docs) (Firestore, Data Connect, Authentication, App Check, and Cloud Functions). Focus on incremental adoption, automated testing, and observability so your team can measure performance and developer velocity improvements at each stage.

### Where can I watch the full Better Performance through analysis walkthrough and find related code resources?

You can explore the complete write-up and code examples right here on CodingCat.dev, and subscribe to the [**CodingCat.dev YouTube channel**](https://www.youtube.com/@CodingCatDev?sub_confirmation=1) for weekly video tutorials. For a deeper dive into Firebase, check out our related guide: [**What the F*ck is Firebase Now?**](/post/what-the-f-ck-is-firebase-now).

✏️ Visual Architecture Diagram

## how this post connects together.

Follow AJ from first principles to production-ready architecture.

Let’s build it!✏️ Visual Diagram: Better Performance through analysis✓ Good PatternVISUAL DIAGRAM[Diagram Walkthrough]Step-by-step diagram breakdown for Better Performance through analysis: start with Better Performance thr, implement Hands-On Implementation, and ship to production.AAA Contrast Verified▶ Watch on @CodingCatDev YouTubeRelated Blog Post & Video

## Watch the Related Video Deep Dive: Sanity Knowledge Bases

Eliminate query-time guessing in your AI agents. Learn how Sanity Context Knowledge Bases compile structured datasets, crawled documentation websites, and uploaded files ahead of time, resolve conflicting facts, and serve a compact outline over Context MCP.

[View Full Page →](/post/sanity-knowledge-bases)![](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/38b0f021c51d97043c8a1ebf31d505a0ea877b7c-2752x1536.jpg?rect=11,0,2731,1536&w=1920&h=1080&q=82&fit=max&auto=format)[@CodingCatDev62.5K / 100K Subscribers Goal](https://www.youtube.com/@codingcatdev?sub_confirmation=1)[Subscribe on YouTube→](https://www.youtube.com/@codingcatdev?sub_confirmation=1)[Watch on YouTube App ↗](https://www.youtube.com/watch?v=jm5Vq60qYTk&list=UUnKZ8gEb78zXKMi1ns-IQ2g)

## related deep dives.

[All Blog Posts&rarr;](/blog)[![PHP2Shell (CVE-2026-109618): How AI Found a Decade-Old Bug in 70% of the Web](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/e83065d0a4e2f841ce64d3f4aea8ddbbf07e5cb9-1376x768.jpg?w=1376&q=82&fit=max&auto=format)](/post/php2shell-cve-2026-109618-ai-php-security-scramble)October 22, 2026[![](/logos/tags/php-symbol-light.svg)![](/logos/tags/php-symbol-dark.svg)PHP](/topic/php)[#Security](/topic/security)[#AI & Agents](/topic/ai)[+5](/post/php2shell-cve-2026-109618-ai-php-security-scramble)

### [PHP2Shell (CVE-2026-109618): How AI Found a Decade-Old Bug in 70% of the Web](/post/php2shell-cve-2026-109618-ai-php-security-scramble)

Two critical pre-authentication RCE flaws in PHP (CVE-2026-109618 and CVE-2026-109619), uncovered by AI models from OpenAI and Google Gemini, sparked a global patching scramble across 70% of the web. Here is how PHP2Shell works and how to patch your servers.

[![Alex Patterson](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/a606dfaa381aab08ddbe16a33fe1d3e1fb37c927-400x400.jpg?w=96&h=96&q=82&fit=max&auto=format)Alex Patterson](/author/alex-patterson)[![Sanity Knowledge Bases](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/38b0f021c51d97043c8a1ebf31d505a0ea877b7c-2752x1536.jpg?w=1920&q=82&fit=max&auto=format)](/post/sanity-knowledge-bases)October 17, 2026[![](/logos/tags/mcp-symbol-light.svg)![](/logos/tags/mcp-symbol-dark.svg)MCP](/topic/mcp)[#AI & Agents](/topic/ai)[![](/logos/sanity/Sanity-Symbol--black_on_transparent.svg)![](/logos/sanity/Sanity-Symbol--white_on_transparent.svg)Sanity](/topic/sanity)[+5](/post/sanity-knowledge-bases)

### [Sanity Knowledge Bases](/post/sanity-knowledge-bases)

Eliminate query-time guessing in your AI agents. Learn how Sanity Context Knowledge Bases compile structured datasets, crawled documentation websites, and uploaded files ahead of time, resolve conflicting facts, and serve a compact outline over Context MCP.

[![Alex Patterson](https://cdn.sanity.io/media-libraries/mlttp0BZbCpV/images/a606dfaa381aab08ddbe16a33fe1d3e1fb37c927-400x400.jpg?w=96&h=96&q=82&fit=max&auto=format)Alex Patterson](/author/alex-patterson)