content: performance_tool_score_diffs #977

egsweeny · 2019-06-05T11:25:43Z

This pull request adds a new:

Blog Post
Guide(s) 📘
Codelab(s) 🔬

Does your content tell a user how to fix a Lighthouse audit?
Have you added the Lighthouse audit ID to your YAML?

My changes do not mention Lighthouse audits. 🙅‍♂️
I have added the Lighthouse audit IDs to my content. 👍

Does your content reference any Glitch projects?
Have you read the wiki on working with Glitch?
Have you added the Glitch project to our team page?

My changes do not contain any Glitches. 🙅‍♂️
I have read the wiki on working with Glitch. 🍰
I have added my Glitches to the team page. 👏

![hero](https://user-images.githubusercontent.com/40670445/58956350-6a544180-879e-11e9-9b8e-37f00f83fa4f.jpg)

Still a draft! :)

egsweeny · 2019-06-05T12:33:25Z

Would you like me to create a new folder so that I can add my img assets?

robdodson · 2019-06-05T17:33:46Z

yep you'll want to create a directory called:

performance-tool-score-diffs

and you can put your images inside of it. Your markdown file can be renamed to index.md.

So you should end up with:

blog/performance-tool-score-diffs/
-- index.md
-- foo.jpg

robdodson

Did an initial pass. Looks pretty good so far, but I think a few items weren't included in the PR.

src/site/content/en/blog/performance_tool_score_diffs.md

Co-Authored-By: Rob Dodson <robdodson@users.noreply.github.com>

robdodson · 2019-06-10T23:06:59Z

hey @egsweeny let me know when you're ready for another review.

…g for the post.

egsweeny · 2019-06-11T15:20:08Z

Howdy @robdodson ! I think I'm ready for another review. :) Thank you!

src/site/content/en/blog/performance-tool-score-diffs/index.md

robdodson · 2019-06-12T00:53:44Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+TMS is a ‘Think with Google’ tool that allows you to compare your FCP to that of your competitors and estimate the monetary value of improving your site’s performance.
+
+### Mobile Site Speed: Field Data, FCP Only, Site Level
+The first part of the report, the mobile site speed seconds figure === First Contentful Paint (FCP) of the origin from CrUX.


I was wondering if these === could be replaced with "equals", or something along those lines. Currently they read a tad rushed.

src/site/content/en/blog/performance-tool-score-diffs/index.md

robdodson · 2019-06-12T00:55:57Z

@mfriesenhahn are you free to give this one a look?

egsweeny · 2019-06-12T20:33:56Z

Just incorporated the final changes suggested by @robdodson ! :)

Meggin

So I'm pretty confused still about scoring. It's late afternoon, and I need to go for a run, so maybe the brain isn't working. That said, I think a white-board session explaining the table and then how it is used in each tool would really help. I'm kind of lost. But can maybe help with words once I understand what the blog post is trying to do.

Meggin · 2019-06-13T22:02:10Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+  - performance
+---
+
+Load is not a single point in time- there are multiple moments during the load experience that can affect whether a user perceives it as "fast", and if you just focus on one you might miss bad experiences that happen during the rest of the time. **This is why we generally use multiple metrics blended together to create our performance scores;** but different tools use different metrics and different weighted blends. This can be frustrating when you're looking for a source of truth about how fast your website is.


This paragraph is a little big, has some run-on sentences, and a little bit of formatting strangeness. Small changes reflected here:

Load is not a single point in time. There are multiple moments during the load experience that can affect whether a user perceives it as "fast". If you focus on only one of these moments, you might miss bad experiences that happen the rest of the time. This is why we generally use multiple metrics blended together to create our performance scores. Different tools use different metrics and different weighted blends.

Meggin · 2019-06-13T22:03:18Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+---
+
+Load is not a single point in time- there are multiple moments during the load experience that can affect whether a user perceives it as "fast", and if you just focus on one you might miss bad experiences that happen during the rest of the time. **This is why we generally use multiple metrics blended together to create our performance scores;** but different tools use different metrics and different weighted blends. This can be frustrating when you're looking for a source of truth about how fast your website is.
+


Suggestion to move sentence "This can be frustrating" to be the starting sentence of the next paragraph. And reword it a little bit:

When you're looking for a source of truth about how fast your website is, it can be frustrating seeing different performance scores from different tools.

Meggin · 2019-06-13T22:05:25Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+
+Load is not a single point in time- there are multiple moments during the load experience that can affect whether a user perceives it as "fast", and if you just focus on one you might miss bad experiences that happen during the rest of the time. **This is why we generally use multiple metrics blended together to create our performance scores;** but different tools use different metrics and different weighted blends. This can be frustrating when you're looking for a source of truth about how fast your website is.
+
+This post serves to explain the reasons that there are differences in performance scores between three Google tools: [Test My Site (TMS)](https://www.thinkwithgoogle.com/intl/en-gb/feature/testmysite), [PageSpeed Insights (PSI)](https://developers.google.com/speed/pagespeed/insights/), and [Lighthouse (LH)](https://developers.google.com/web/tools/lighthouse/). This document does **not** detail other differences in the tools, such as server run locations, network throttling presets, score variance between runs, etc.


Small nit: suggestion to replace 'document' with 'post' to be consistent.

Meggin · 2019-06-13T22:06:56Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+
+## Terminology
+
+Various terms about speed/performance are referenced in our tools. We want to start off with some clarification of how these terms are used.


I would suggest replacing the first two sentences with one that's something like:

"The terms page speed and site speed are referenced throughout these tools:"

It's short and to the point, and I think it does enough work.

Meggin · 2019-06-13T22:10:43Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+- **Page speed** refers to the speed of an individual page on your site (URL level).
+- **Site speed** refers to the speed of all of the pages on your site (origin level).
+
+It is important to note that "performance" or "speed" is not to be defined by a single metric (i.e. [First Contentful Paint (FCP)](/first-contentful-paint/), [Time to Interactive (TTI)](/interactive/), etc.). This is motivated by several considerations, including:


Suggestion to remove 'i.e.' and 'etc.'. Start off with 'such as'.

Meggin · 2019-06-13T22:21:47Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+{% endAside %}
+
+TMS uses only FCP (from both Lighthouse and from the CrUX) to provide both site and page speed scores.
+


You are introducing CrUX here, and not all developers will know what that is?

Meggin · 2019-06-13T22:23:49Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+        <td><a href="https://www.thinkwithgoogle.com/intl/en-gb/feature/testmysite">Test My Site</a></td>
+        <td>Lab & Field</td>
+        <td>FCP**</td>
+        <td>FCP**</td>


Whoah, this table scares me. Have we explained lab vs field? What do all the abbreviations mean? Asterix descriptions also are a bit vague. I completely understand how hard it is to make this table work! But I do think it might need a few gos.

Meggin · 2019-06-13T22:28:08Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+
+Site speed is the speed of **all the pages** that make up your site.
+
+<figure class="w-figure">


OK, as I move through the various tool descriptions and scoring, I continue to remain lost along the way. And a lot of that has to do with not fully understanding the table. I'm really lost here.. and trying to understand what you are trying to say. I wonder if maybe this could be solved with a chat explaining it to me, and me then word-smithing that explanation? Should I set up some time?

Meggin · 2019-06-13T22:28:38Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+
+### Site Speed Tools: Field Data, FCP Only, Site Level
+In the second part of the report, the mobile site speed seconds figure === First Contentful Paint (FCP) of the origin from CrUX. 
+


See general comment above-- I'm still lost here. Lots of abbreviations and assumptions around field and lab, etc.

Meggin · 2019-06-13T22:29:17Z

src/site/content/en/blog/performance-tool-score-diffs/index.md

+  </figcaption>
+</figure>
+
+### PSI Field Data: Field Data, FCP & FID, URL & Origin Level


Whoah all the things in the title.

egsweeny · 2019-06-14T01:52:38Z

@Meggin I'd love to set up some time to chat with you about this, to share my intentions about meaning and leveraging your brilliant wordsmithing abilities to convey it to all!

kaycebasques · 2019-12-14T02:01:49Z

@egsweeny LMK if we still need this content and we'll set aside some time in the future to address it

I backed up the content here: https://drive.google.com/a/google.com/file/d/1bVfz4awdeobcLTyWt4SA7B2bXNw8rHcA/view?usp=sharing

egsweeny added 2 commits June 5, 2019 13:24

Create blog post: performance_tool_score_diffs

7fccdc7

Still a draft! :)

Update blog post.

c602380

egsweeny marked this pull request as ready for review June 5, 2019 12:30

egsweeny requested a review from robdodson as a code owner June 5, 2019 12:30

robdodson suggested changes Jun 5, 2019

View reviewed changes

Update src/site/content/en/blog/performance_tool_score_diffs.md

28c066e

Co-Authored-By: Rob Dodson <robdodson@users.noreply.github.com>

egsweeny requested review from Meggin and mfriesenhahn as code owners June 10, 2019 15:48

googlebot added the cla: yes Contributor has signed the CLA label Jun 10, 2019

egsweeny and others added 3 commits June 10, 2019 17:48

Update src/site/content/en/blog/performance_tool_score_diffs.md

97e5508

Co-Authored-By: Rob Dodson <robdodson@users.noreply.github.com>

Update src/site/content/en/blog/performance_tool_score_diffs.md

1e972ae

Co-Authored-By: Rob Dodson <robdodson@users.noreply.github.com>

Update src/site/content/en/blog/performance_tool_score_diffs.md

ce27e5c

Co-Authored-By: Rob Dodson <robdodson@users.noreply.github.com>

egsweeny and others added 2 commits June 11, 2019 07:42

Created new directory to contain renamed index file as well as all im…

7882cbf

…g for the post.

Updated to include all suggestions from 6/5/19 review

443ef34

robdodson added 6 commits June 11, 2019 17:08

Fix hero image.

9c361b1

Fixup image styles.

68c375f

More content fixes.

7392761

More cleanup.

b66723b

Sentence case heading.

d7ab156

Abbrecviate Lighthouse.

7b72516

robdodson reviewed Jun 12, 2019

View reviewed changes

src/site/content/en/blog/performance-tool-score-diffs/index.md Outdated Show resolved Hide resolved

robdodson reviewed Jun 12, 2019

View reviewed changes

src/site/content/en/blog/performance-tool-score-diffs/index.md Outdated Show resolved Hide resolved

robdodson reviewed Jun 12, 2019

View reviewed changes

src/site/content/en/blog/performance-tool-score-diffs/index.md Outdated Show resolved Hide resolved

Update to incorporate robdodson's suggestions on 2nd review

38b42da

Meggin reviewed Jun 13, 2019

View reviewed changes

robdodson assigned Meggin Jun 17, 2019

robdodson assigned egsweeny Jun 27, 2019

robdodson changed the title ~~Create blog post: performance_tool_score_diffs~~ content: performance_tool_score_diffs Jun 27, 2019

robdodson unassigned Meggin Jun 27, 2019

robdodson mentioned this pull request Jun 28, 2019

content: How to think about speed tools #1050

Closed

7 tasks

brendankenny mentioned this pull request Nov 7, 2019

[meta] Lighthouse 6.0 Burndown GoogleChrome/lighthouse#9774

Closed

54 tasks

kaycebasques closed this Dec 14, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

content: performance_tool_score_diffs #977

content: performance_tool_score_diffs #977

egsweeny commented Jun 5, 2019 •

edited

Loading

egsweeny commented Jun 5, 2019

robdodson commented Jun 5, 2019

robdodson left a comment

robdodson commented Jun 10, 2019

egsweeny commented Jun 11, 2019

robdodson Jun 12, 2019

robdodson commented Jun 12, 2019

egsweeny commented Jun 12, 2019

Meggin left a comment

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

Meggin Jun 13, 2019

egsweeny commented Jun 14, 2019

kaycebasques commented Dec 14, 2019

		---

		Load is not a single point in time- there are multiple moments during the load experience that can affect whether a user perceives it as "fast", and if you just focus on one you might miss bad experiences that happen during the rest of the time. This is why we generally use multiple metrics blended together to create our performance scores; but different tools use different metrics and different weighted blends. This can be frustrating when you're looking for a source of truth about how fast your website is.


		Load is not a single point in time- there are multiple moments during the load experience that can affect whether a user perceives it as "fast", and if you just focus on one you might miss bad experiences that happen during the rest of the time. This is why we generally use multiple metrics blended together to create our performance scores; but different tools use different metrics and different weighted blends. This can be frustrating when you're looking for a source of truth about how fast your website is.

		This post serves to explain the reasons that there are differences in performance scores between three Google tools: [Test My Site (TMS)](https://www.thinkwithgoogle.com/intl/en-gb/feature/testmysite), [PageSpeed Insights (PSI)](https://developers.google.com/speed/pagespeed/insights/), and [Lighthouse (LH)](https://developers.google.com/web/tools/lighthouse/). This document does not detail other differences in the tools, such as server run locations, network throttling presets, score variance between runs, etc.


		## Terminology

		Various terms about speed/performance are referenced in our tools. We want to start off with some clarification of how these terms are used.

		{% endAside %}

		TMS uses only FCP (from both Lighthouse and from the CrUX) to provide both site and page speed scores.


		Site speed is the speed of all the pages that make up your site.

		<figure class="w-figure">


		### Site Speed Tools: Field Data, FCP Only, Site Level
		In the second part of the report, the mobile site speed seconds figure === First Contentful Paint (FCP) of the origin from CrUX.

content: performance_tool_score_diffs #977

content: performance_tool_score_diffs #977

Conversation

egsweeny commented Jun 5, 2019 • edited Loading

egsweeny commented Jun 5, 2019

robdodson commented Jun 5, 2019

robdodson left a comment

Choose a reason for hiding this comment

robdodson commented Jun 10, 2019

egsweeny commented Jun 11, 2019

Choose a reason for hiding this comment

robdodson commented Jun 12, 2019

egsweeny commented Jun 12, 2019

Meggin left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

egsweeny commented Jun 14, 2019

kaycebasques commented Dec 14, 2019

egsweeny commented Jun 5, 2019 •

edited

Loading