Request Metrics

Stillwater, MN, USA
2020
May 7, 2021   |  By Request Metrics
First Contentful Paint, or FCP, measures the time take to render the first element of a webpage. It’s a modern, user-centric measurement of how fast users see a response from your website. Here’s everything you need to know about the metric and how to use it. FCP is one of the Core Web Vital performance metrics that measure user’s perceived performance of websites. These metrics are incredibly important to delivering fast user experiences, and avoiding SEO performance penalties.
May 3, 2021   |  By Request Metrics
This is the complete guide to the metrics, methods, and measurements of web performance in 2021. If you run a website, this guide has all the fundamental ideas you need to understand to build a fast website for your users, and for search engines.
Dec 3, 2020   |  By Request Metrics
Earlier this month, David’s heartfelt posting about leaving Mozilla made the front page of Hacker News. Traffic increased by 800% to his already-busy website, which slowed and eventually failed under the pressure. Request Metrics monitors performance and uptime for David’s blog, and our metrics tell an interesting story. Here’s what happened, why, and what you can do to prepare your site for traffic surges.
Dec 3, 2020   |  By Request Metrics
Web performance used to be easy. You’d time how long a page takes to load, easy. But the rise of client-side JavaScript has introduced bold new ways for websites to be frustratingly slow. Measuring this new slowness will take new metrics. Google calls them the Core Web Vitals. Each of the Core Web Vitals measures a different aspect of how a web application responds. This post will take a look at each of these metrics, what they measure, and how to use them.
Nov 17, 2020   |  By Request Metrics
Google Lighthouse helps you identify page performance issues. It generates an overall performance “score” to make you feel good (or bad) about your site’s speed. This score can be useful, but has some limitations. Lighthouse is an automated tool for assessing web page quality. It generates metrics for performance, SEO, accessability and more. Google has been promoting it as THE way to measure website quality.
Nov 10, 2020   |  By Request Metrics
Grocery shopping is tedious and time consuming. In search of a more streamlined experience, I decided to try Instacart. Unfortunately, using their site is also tedious and time consuming.
Sep 29, 2020   |  By Request Metrics
I hate slow websites. They are annoying to use and frustrating to work on. But what does it mean to be “slow”? It used to be waiting for document load. Then waiting for page ready. But with so many asynchronous patterns in use today, how do we even define what “slow” is? The W3C has been working on this with the new Event Timing and Element Timing API, and has defined some new Web Vital metrics to describe the different ways that slow performance can impact a webpage.
Sep 15, 2020   |  By Request Metrics
How is Google so fast? It’s so fast we take it for granted. It feels instant from the time you search to when results are displayed. What can we learn about the techniques they use to make their site so fast?
Sep 8, 2020   |  By Request Metrics
First Input Delay (FID) measures how long the browser took to respond to the first user input event. It’s one of several Web Vital metrics that measure how real users perceive the performance of modern web applications. New measurements like First Input Delay are increasingly important as JavaScript and SPA’s do more work on the client side.
Aug 25, 2020   |  By Request Metrics
Google has long used website performance as a ranking criteria for search results. Despite the importance of page experience for SEO, many sites still suffer unacceptable load times. Poor performance is often a confluence of factors: slow time to first byte, hundreds of resource requests, and way too much JavaScript.
May 13, 2020   |  By Request Metrics
Javascript build chains have gotten outrageously complicated. Let's create one that isn't. Request Metrics monitors how real users experience the performance of your production websites. We need a JavaScript agent to pull performance data out of the browser. Watch as I calmly Bob Ross my way to a Webpack-free Typescript build pipeline with just a few NPM packages.
May 11, 2020   |  By Request Metrics
Users are so annoying! There they go, leaving the page before we can save the data to the API. Back in the old days, we would attach a `window.unload` handler and try to send an AJAX request, but this was slow and unreliable. Enter the Beacon API to give us a better way. The Beacon provides a reliable way to send a small amount of data *after* the page has been unloaded. It's not bound to the lifetime of the page and it doesn't slow down the user.
May 7, 2020   |  By Request Metrics
Request Metrics is a performance analytics tool. As such, we need to build a data ingestion pipeline that will consume performance data and process it. One common approach to ingest is to shove incoming data into a queue. We like simple things, and figuring out fancy distributed queues is anything but. So we're going to eschew best practices and use NGINX as our queue!
Apr 30, 2020   |  By Request Metrics
Request Metrics won’t be very successful if users can’t sign up! We recently completed cookie based user authentication and distributed session using Redis in ASP.NET Core but neglected initial sign up. Now we finally go back and write some boring forms and CRUD logic. A rich set of internal admin tools helps with customer support, system monitoring and visibility. We’ll start our suite of tools with a user admin page that lists all users in the system.
Apr 27, 2020   |  By Request Metrics
We need distributed session. Spoiler: We DON'T roll it ourselves. In-memory sessions stop working as soon as there is more than one server. Most production environments have more than one server so the session issue needs to be dealt with. There are two options for sessions in a web farm. First, a load balancer can be used to lock each user on a specific box. This lets us continue to use in-memory sessions. The second is switching from in-memory to distributed session storage.
Apr 22, 2020   |  By Request Metrics
Core Identity is the officially encouraged method of authenticating users in ASP.NET Core. As you might have guessed, we're not fans of the heavy handed, black box approach needed to make Core Identity "Just work". We want to use as much of the existing ASP.NET Authorization framework as we can while avoiding Core Identity. Thankfully, ASP.NET Supports cookie authorization without Core Identity!
Apr 20, 2020   |  By Request Metrics
It's time to think about the data model for Request Metrics. We plan to store all customer records in Redis. This requires some thought because Redis is not a relational database. The first thing we need is a user. We'd like to work on authentication soon and we won't get far without a user to login with.
Apr 15, 2020   |  By Request Metrics
We've started writing code for Request Metrics. That code needs to be tested. We need a unit test framework for our .NET Core solution. We've used various frameworks on our .NET projects over the years, but enough has changed in .NET Core to require a small investigation into unit testing options. Ultimately, we settled on NUnit because of its good balance between simplicity and features.
Apr 13, 2020   |  By Request Metrics
We thought we were done with infrastructure work. We were wrong. Just as we've started work on application code, it turns out our server configuration needs a couple changes. Our application loads its environment config based off of an environment variable. We need to ensure this variable is actually set on the server. We also want to fix our Ansible playbook which fails when run on fresh servers.
Apr 7, 2020   |  By Request Metrics
We've finally finished screwing around with basic groundwork. Today we start writing actually useful application code! First, can we connect to Redis? Connecting to Redis implies some connection strings, so we'll create a basic environment based configuration while we're thinking about it.

The easiest way to monitor your web performance. Request Metrics records how real users experience your website and shows you simplified metrics and alerting. And at a price that's easy on your budget.

Request Metrics is website performance monitoring, simplified for small teams. It's not a expensive APM "solution" or a complex query language to learn. Request Metrics is simply the key metrics you need to know to keep your website running fast and your customers happy.

Request Metrics was developed by TrackJS partners Todd Gardner, Eric Brandes, and Jordan Griffin. It was developed "in the open", with coding sessions and planning meetings recorded and broadcast on YouTube. They can be found at https://requestmetrics.com/building.

Our Features:

  • Monitor Performance From Real Users: We gather metrics from real users visiting your website and aggregate their experience to show you the performance that really matters.
  • Measure Your Performance Over Time: We rollup your performance statistics to minutes, hours, and days so you can understand how you compare to last week, last month, or last year.
  • Know When Your Website Slows Down: When something is slowing down and your users are frustrated, we'll let you know with a detailed alert report about what's happening and the impact.
  • Worth The Price: No suite of tools to deploy, training to attend, or budget approvals. We show you the most important performance metrics you need, simplified, at a price that fits any team's budget.

Your Website, Faster.