Skip to content

Commit c056b46

Browse files
aaronhansaaronhans
authored
Merge pull request #56 from ScanGov/performancedoc
Performancedoc
2 parents da3fb8f + 28acd75 commit c056b46

6 files changed

+140
-0
lines changed

‎_pages/cumulative-layout-shift.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: "Cumulative layout shift"
3+
date: 2025-02-08
4+
description: ""
5+
icon: "fa-solid fa-gauge"
6+
services: true
7+
lowercase: true
8+
keywords:
9+
topics:
10+
- Performance
11+
---
12+
13+
## Guidance
14+
15+
Core Web Vitals assessment grades cumulative layout shift as "good" when the page is making less than or equal to 0.1 seconds of unexpected shifts.
16+
17+
Cumulative layout shift (CLS) is one of the performance <a href="https://developers.google.com/search/docs/appearance/core-web-vitals">Core Web Vitals</a> metrics that help ensure passable user experience for visitors on all devices and affect a site's search engine ranking.
18+
19+
## About
20+
21+
Cumulative layout shift measures how much a page unexpectedly moves things around once they are displayed.
22+
23+
Regular interactions that change content like clicking a button are expected shifts and are not counted in the layout shift.
24+
25+
More information on the <a href="https://web.dev/articles/cls">cumulative layout shift metric from web.dev</a>
26+
27+
The data ScanGov uses to evaluate sites is provided by the <a href="https://developer.chrome.com/docs/crux">Chrome user experience report</a>. This dataset is compiled from real visitor data each domain. Sites with low traffic will not have any data available in the Chrome user experience report. In that case we run our own lighthouse audit.

‎_pages/first-contentful-paint.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: "First contentful paint"
3+
date: 2025-02-08
4+
description: ""
5+
icon: "fa-solid fa-gauge"
6+
services: true
7+
lowercase: true
8+
keywords:
9+
topics:
10+
- Performance
11+
---
12+
13+
## Guidance
14+
15+
Core Web Vitals assessment grades first contentful paint as "good" when it happens in less than or equal to 1.8 seconds.
16+
17+
First contentful paint (FCP) is one of the performance <a href="https://developers.google.com/search/docs/appearance/core-web-vitals">Core Web Vitals</a> metrics that help ensure passable user experience for visitors on all devices and affect a site's search engine ranking.
18+
19+
## About
20+
21+
First contentful paint measures how quickly the page begins to become visible.
22+
23+
Any section of the page counts for this measurement so if the header is displayed while the rest of the page is still blank this is considered complete.
24+
25+
More information on the <a href="https://web.dev/articles/fcp">first contentful paint metric from web.dev</a>
26+
27+
The data ScanGov uses to evaluate sites is provided by the <a href="https://developer.chrome.com/docs/crux">Chrome user experience report</a>. This dataset is compiled from real visitor data each domain. Sites with low traffic will not have any data available in the Chrome user experience report. In that case we run our own lighthouse audit.

‎_pages/interaction-to-next-paint.md

+25
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
title: "Interaction to next paint"
3+
date: 2025-02-08
4+
description: ""
5+
icon: "fa-solid fa-gauge"
6+
services: true
7+
lowercase: true
8+
keywords:
9+
topics:
10+
- Performance
11+
---
12+
13+
## Guidance
14+
15+
Core Web Vitals assessment grades a successful interaction to next paint as less than or equal to 0.2 seconds.
16+
17+
Interaction to next paint (INP) is one of the performance <a href="https://developers.google.com/search/docs/appearance/core-web-vitals">Core Web Vitals</a> metrics that help ensure passable user experience for visitors on all devices and affect a site's search engine ranking.
18+
19+
## About
20+
21+
Interaction to next paint measures page interaction latency. It can be confusing and frustrating for visitors when clicking on elements in your web application does not produce an immediate response.
22+
23+
More information on Interaction to next paint (INP) <a href="https://web.dev/articles/inp">on web.dev</a>
24+
25+
The data ScanGov uses to evaluate sites is provided by the <a href="https://developer.chrome.com/docs/crux">Chrome user experience report</a>. This dataset is compiled from real visitor data each domain. Sites with low traffic will not have any data available in the Chrome user experience report. In that case we run our own lighthouse audit.

‎_pages/largest-contentful-paint.md

+25
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
title: "Largest contentful paint"
3+
date: 2025-02-08
4+
description: "How fast the majority of a page is rendered"
5+
icon: "fa-solid fa-gauge"
6+
services: true
7+
lowercase: true
8+
keywords:
9+
topics:
10+
- Performance
11+
---
12+
13+
## Guidance
14+
15+
Core Web Vitals assessment grades largest contentful paint as "good" when it happens in less than or equal to 2.5 seconds.
16+
17+
Largest contentful paint (LCP) is one of the performance <a href="https://developers.google.com/search/docs/appearance/core-web-vitals">Core Web Vitals</a> metrics that help ensure passable user experience for visitors on all devices and affect a site's search engine ranking.
18+
19+
## About
20+
21+
Largest contentful paint measures how quickly largest content block takes to become visible.
22+
23+
More information on the <a href="https://web.dev/articles/lcp">largest contentful paint metric from web.dev</a>
24+
25+
The data ScanGov uses to evaluate sites is provided by the <a href="https://developer.chrome.com/docs/crux">Chrome user experience report</a>. This dataset is compiled from real visitor data each domain. Sites with low traffic will not have any data available in the Chrome user experience report. In that case we run our own lighthouse audit.

‎_pages/time-to-first-byte.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: "Time to first byte"
3+
date: 2025-02-08
4+
description: ""
5+
icon: "fa-solid fa-gauge"
6+
services: true
7+
lowercase: true
8+
keywords:
9+
topics:
10+
- Performance
11+
---
12+
13+
## Guidance
14+
15+
Core Web Vitals assessment grades a successful time to first byte response as less than or equal to 0.8 seconds.
16+
17+
Time to first byte (TTFB) is one of the performance <a href="https://developers.google.com/search/docs/appearance/core-web-vitals">Core Web Vitals</a> metrics that help ensure passable user experience for visitors on all devices and affect a site's search engine ranking.
18+
19+
## About
20+
21+
Time to first byte measures how fast your server is responds.
22+
23+
This is the first step in the performance pipeline. If this is not fast it is difficult to pass other metrics that depend on it.
24+
25+
More information on the <a href="https://web.dev/articles/ttfb">time to first byte metric from web.dev</a>
26+
27+
The data ScanGov uses to evaluate sites is provided by the <a href="https://developer.chrome.com/docs/crux">Chrome user experience report</a>. This dataset is compiled from real visitor data each domain. Sites with low traffic will not have any data available in the Chrome user experience report. In that case we run our own lighthouse audit.

‎_topics/performance.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: "Performance"
3+
date: 2025-02-08
4+
modified:
5+
author: ScanGov
6+
description: "Site performances resources and support."
7+
icon: "fa-solid fa-gauge"
8+
lowercase: true
9+
---

0 commit comments

Comments
 (0)