https://github.com/git/git/pull/804/files
59
Performance
99
Accessibility
59
Performance
99
Accessibility
0–49 50–89 90–100
59
Performance
Metrics
First Contentful Paint
2.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
5.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
7.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive
7.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Eliminate render-blocking resources
1.43 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
URL
Transfer Size
Potential Savings
/assets/light-0eace2597ca3.css
(github.githubassets.com)
4.3 KiB
770 ms
/assets/dark-a167e256da9c.css
(github.githubassets.com)
4.5 KiB
150 ms
/assets/primer-08e422afeb43.css
(github.githubassets.com)
49.9 KiB
150 ms
/assets/global-fcad22128422.css
(github.githubassets.com)
43.9 KiB
300 ms
/assets/github-2f3974e4587d.css
(github.githubassets.com)
24.4 KiB
150 ms
Remove unused CSS
0.6 s
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
URL
Transfer Size
Potential Savings
/assets/primer-08e422afeb43.css
(github.githubassets.com)
49.9 KiB
45.5 KiB
/assets/global-fcad22128422.css
(github.githubassets.com)
43.9 KiB
40.7 KiB
/assets/github-2f3974e4587d.css
(github.githubassets.com)
24.4 KiB
24.1 KiB
Remove unused JavaScript
0.6 s
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
URL
Transfer Size
Potential Savings
/assets/behaviors-1e4a69ad752e.js
(github.githubassets.com)
64.7 KiB
49.9 KiB
/assets/react-lib-1fbfc5be2c18.js
(github.githubassets.com)
59.4 KiB
39.1 KiB
Reduce initial server response time
0.56 s
Keep the server response time for the main document short because all other requests depend on it. Learn more.
URL
Time Spent
…804/files
(github.com)
660 ms
DiagnosticsMore information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid an excessive DOM size 4,000 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Statistic
Element
Value
Total DOM Elements
NaN
Maximum DOM Depth
<span class="d-md-inline-block d-none">
42
Maximum Child Elements
<tbody>
185

  

    

      
        

          
          
            Avoid chaining critical requests
            9 chains found
          
          

    
      
      
    
  

        

      
      
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

      

    

    
    

      

        Maximum critical path latency: 800 ms
      

    

    

      
Initial Navigation

      
      
    
        

          

          
          

          
…804/files
(github.com)

        

      
        

          

          
          

          
/assets/light-0eace2597ca3.css
(github.githubassets.com)
 - 40 ms, 4.32 KiB
        

      
        

          

          
          

          
/assets/dark-a167e256da9c.css
(github.githubassets.com)
 - 70 ms, 4.54 KiB
        

      
        

          

          
          

          
/assets/primer-primitives-971c6be3ec9f.css
(github.githubassets.com)
 - 60 ms, 1.84 KiB
        

      
        

          

          
          

          
/assets/primer-08e422afeb43.css
(github.githubassets.com)
 - 110 ms, 49.85 KiB
        

      
        

          

          
          

          
/assets/global-fcad22128422.css
(github.githubassets.com)
 - 110 ms, 43.91 KiB
        

      
        

          

          
          

          
/assets/github-2f3974e4587d.css
(github.githubassets.com)
 - 60 ms, 24.45 KiB
        

      
        

          

          
          

          
/assets/repository-b6b0e69bbb90.css
(github.githubassets.com)
 - 20 ms, 5.77 KiB
        

      
        

          

          
          

          
/assets/code-aed6ab8a6a15.css
(github.githubassets.com)
 - 20 ms, 6.64 KiB
        

      
        

          

          
          

          
/assets/pull-requests-0e99259b6ecf.css
(github.githubassets.com)
 - 20 ms, 2.57 KiB
        

      

  

  

    

      
        

          
          
            Keep request counts low and transfer sizes small
            100 requests • 1,002 KiB
          
          

    
      
      
    
  

        

      
      
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

      

    
Resource Type
Requests
Transfer Size
Total
100
1,001.9 KiB
Script
73
721.2 KiB
Stylesheet
9
143.9 KiB
Document
1
84.8 KiB
Other
14
43.9 KiB
Image
3
8 KiB
Media
0
0 KiB
Font
0
0 KiB
Third-party
88
889.8 KiB

  

    

      
        

          
          
            Largest Contentful Paint element
            1 element found
          
          

    
      
      
    
  

        

      
      
This is the largest contentful element painted within the viewport. Learn More

      

    
Element
improve git-diff documentation and A...B handling #804
<h1 class="gh-header-title mb-2 lh-condensed f1 mr-0 flex-auto wb-break-word">

  

    

      
        

          
          
            Avoid long main-thread tasks
            5 long tasks found
          
          

    
      
      
    
  

        

      
      
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

      

    
  
  

    
  


URL
Start Time
Duration
/assets/chunk-app_components_diffs_deferred-diff-lines-eleme….js
(github.githubassets.com)
8,318 ms
125 ms
/assets/behaviors-1e4a69ad752e.js
(github.githubassets.com)
6,764 ms
84 ms
…804/files
(github.com)
1,398 ms
75 ms
/assets/vendors-node_modules_github_file-attachment-element_….js
(github.githubassets.com)
4,211 ms
53 ms
/assets/chunk-app_components_diffs_deferred-diff-lines-eleme….js
(github.githubassets.com)
8,265 ms
53 ms

  

    

      
        

          
          
            Avoid non-composited animations
            541 animated elements found
          
          

    
      
      
    
  

        

      
      
Animations which are not composited can be janky and increase CLS. Learn more

      

    
Element
++
<span class="pl-c1">
Unsupported CSS Property: color
nr
<span class="pl-c1">
Unsupported CSS Property: color
	 * rev->pending.objects and rev->cmdline.rev are parallel.
<span class="pl-c">
Unsupported CSS Property: color
	test_tick &&
<span class="pl-s">
Unsupported CSS Property: color
"git diff [<options>] [<commit>] [--] [<path>...]\n"
<span class="pl-s">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
get_commit_tree
<span class="pl-en">
Unsupported CSS Property: color
rev_info
<span class="pl-smi">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
name
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
flags
<span class="pl-c1">
Unsupported CSS Property: color
/*
<span class="pl-c">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
	test_i18ngrep "usage" err
<span class="pl-s">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
blob_path
<span class="pl-en">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
>
<span class="pl-c1">
Unsupported CSS Property: color
break
<span class="pl-k">
Unsupported CSS Property: color
case
<span class="pl-k">
Unsupported CSS Property: color
bitmap
<span class="pl-smi">
Unsupported CSS Property: color
#define
<span class="pl-k">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
 *  - its skip is non-NULL and marks *all* rev->pending.objects[i]
<span class="pl-c">
Unsupported CSS Property: color
char
<span class="pl-smi">
Unsupported CSS Property: color
usage
<span class="pl-en">
Unsupported CSS Property: color
	 * Use the whence fields to find merge bases and left and
<span class="pl-c">
Unsupported CSS Property: color
	test_i18ngrep "usage" err
<span class="pl-s">
Unsupported CSS Property: color
REV_CMD_MERGE_BASE
<span class="pl-c1">
Unsupported CSS Property: color
1
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
	git add c &&
<span class="pl-s">
Unsupported CSS Property: color
SYMMETRIC_LEFT
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
static
<span class="pl-k">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
nr
<span class="pl-c1">
Unsupported CSS Property: color
		 * random if there are more than one.
<span class="pl-c">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
#include
<span class="pl-k">
Unsupported CSS Property: color
char
<span class="pl-smi">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
++
<span class="pl-c1">
Unsupported CSS Property: color
return
<span class="pl-k">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
skip
<span class="pl-c1">
Unsupported CSS Property: color
#include
<span class="pl-k">
Unsupported CSS Property: color
	 *
<span class="pl-c">
Unsupported CSS Property: color
'diff with two ranges'
<span class="pl-s">
Unsupported CSS Property: color
flags
<span class="pl-c1">
Unsupported CSS Property: color
for
<span class="pl-k">
Unsupported CSS Property: color
	 */
<span class="pl-c">
Unsupported CSS Property: color
# We put files into a few commits so that we can verify the
<span class="pl-c">
Unsupported CSS Property: color
<
<span class="pl-c1">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
run_diff_files
<span class="pl-en">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
type
<span class="pl-c1">
Unsupported CSS Property: color
pending
<span class="pl-c1">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
right
<span class="pl-c1">
Unsupported CSS Property: color
else
<span class="pl-k">
Unsupported CSS Property: color
"ewah/ewok.h"
<span class="pl-s">
Unsupported CSS Property: color
object_array_entry
<span class="pl-smi">
Unsupported CSS Property: color
#  - criss-cross merge ie 2 merge bases (br1...master);
<span class="pl-c">
Unsupported CSS Property: color
USE_THE_INDEX_COMPATIBILITY_MACROS
<span class="pl-c1">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
	 * NB: REV_CMD_LEFT, REV_CMD_RIGHT are also used for A..B,
<span class="pl-c">
Unsupported CSS Property: color
builtin_diff_index
<span class="pl-en">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
"lockfile.h"
<span class="pl-s">
Unsupported CSS Property: color
base
<span class="pl-c1">
Unsupported CSS Property: color
# It should have one of those two, which comes out
<span class="pl-c">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
case
<span class="pl-k">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
object_array_entry
<span class="pl-smi">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
#    / \ /
<span class="pl-c">
Unsupported CSS Property: color
	git checkout br1 &&
<span class="pl-s">
Unsupported CSS Property: color
==
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
#!/bin/sh
<span class="pl-c">
Unsupported CSS Property: color
#include
<span class="pl-k">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
_
<span class="pl-en">
Unsupported CSS Property: color
	 * Forbid any additional revs for both A...B and A..B.
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
OBJ_TREE
<span class="pl-c1">
Unsupported CSS Property: color
case
<span class="pl-k">
Unsupported CSS Property: color
whence
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
++
<span class="pl-c1">
Unsupported CSS Property: color
warn
<span class="pl-c1">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
# The output (in tmp) can have +b or +c depending
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
	git diff commit-D...br1 >tmp &&
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
skip
<span class="pl-c1">
Unsupported CSS Property: color
	test_line_count = 7 tmp &&
<span class="pl-s">
Unsupported CSS Property: color
"   or: git diff [<options>] --cached [<commit>] [--] [<path>...]\n"
<span class="pl-s">
Unsupported CSS Property: color
#include
<span class="pl-k">
Unsupported CSS Property: color
COMMON_DIFF_OPTIONS_HELP
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
nr
<span class="pl-c1">
Unsupported CSS Property: color
right
<span class="pl-c1">
Unsupported CSS Property: color
static
<span class="pl-k">
Unsupported CSS Property: color
 * everything we need to know to handle them correctly.  As a bonus,
<span class="pl-c">
Unsupported CSS Property: color
/* unmark the base we want */
<span class="pl-c">
Unsupported CSS Property: color
		 */
<span class="pl-c">
Unsupported CSS Property: color
'diff with too many symmetric differences'
<span class="pl-s">
Unsupported CSS Property: color
bitmap_new
<span class="pl-en">
Unsupported CSS Property: color
	 * depend on the order that revisions are parsed.  If there
<span class="pl-c">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
1
<span class="pl-c1">
Unsupported CSS Property: color
continue
<span class="pl-k">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
usage
<span class="pl-en">
Unsupported CSS Property: color
'diff with ranges and extra arg'
<span class="pl-s">
Unsupported CSS Property: color
"   or: git diff [<options>] --no-index [--] <path> <path>]\n"
<span class="pl-s">
Unsupported CSS Property: color
return
<span class="pl-k">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
warn
<span class="pl-c1">
Unsupported CSS Property: color
OBJ_BLOB
<span class="pl-c1">
Unsupported CSS Property: color
const
<span class="pl-k">
Unsupported CSS Property: color
base
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
	 * could even get "git diff A...B C...E", for instance.
<span class="pl-c">
Unsupported CSS Property: color
switch
<span class="pl-k">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
	git checkout -b br2 commit-C &&
<span class="pl-s">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
	content="$(git diff HEAD^ HEAD | tail -n 1)"
<span class="pl-s">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
 * If there is no symmetric diff argument, sym->skip is NULL and
<span class="pl-c">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
	test_i18ngrep "usage" err
<span class="pl-s">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
case
<span class="pl-k">
Unsupported CSS Property: color
 *    warning about multiple merge bases.
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
#    \ / \
<span class="pl-c">
Unsupported CSS Property: color
symdiff_prepare
<span class="pl-en">
Unsupported CSS Property: color
builtin_diff_combined
<span class="pl-en">
Unsupported CSS Property: color
-1
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
char
<span class="pl-smi">
Unsupported CSS Property: color
	 */
<span class="pl-c">
Unsupported CSS Property: color
<
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
		 * diff A...B where there is at least one merge base
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
 *    chosen merge base and right side are NOT marked.
<span class="pl-c">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
'diff with symmetric difference and extraneous arg'
<span class="pl-s">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
bitmap_set
<span class="pl-en">
Unsupported CSS Property: color
/*
<span class="pl-c">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
	EOF
<span class="pl-s">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
		 * merge-base, ent.objects[ents-2] == A, and
<span class="pl-c">
Unsupported CSS Property: color
static
<span class="pl-k">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
pending
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
commit
<span class="pl-smi">
Unsupported CSS Property: color
	 * right parts of symmetric difference, so that we do not
<span class="pl-c">
Unsupported CSS Property: color
1
<span class="pl-c1">
Unsupported CSS Property: color
/*
<span class="pl-c">
Unsupported CSS Property: color
symdiff
<span class="pl-smi">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
nr
<span class="pl-c1">
Unsupported CSS Property: color
/* do mark all bases */
<span class="pl-c">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
#       ---F   <-- br2
<span class="pl-c">
Unsupported CSS Property: color
break
<span class="pl-k">
Unsupported CSS Property: color
REV_CMD_LEFT
<span class="pl-c1">
Unsupported CSS Property: color
	git commit -m F &&
<span class="pl-s">
Unsupported CSS Property: color
# to seven lines.
<span class="pl-c">
Unsupported CSS Property: color
.
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
# on which merge base (commit B or C) is picked.
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
#include
<span class="pl-k">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
else
<span class="pl-k">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
#     B---E   <-- master
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
REV_CMD_REF
<span class="pl-c1">
Unsupported CSS Property: color
right
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
'diff with one merge base'
<span class="pl-s">
Unsupported CSS Property: color
bitmap_unset
<span class="pl-en">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
_
<span class="pl-en">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
void
<span class="pl-smi">
Unsupported CSS Property: color
	test_cmp expect actual
<span class="pl-s">
Unsupported CSS Property: color
<
<span class="pl-c1">
Unsupported CSS Property: color
skip
<span class="pl-c1">
Unsupported CSS Property: color
 *
<span class="pl-c">
Unsupported CSS Property: color
# build these situations:
<span class="pl-c">
Unsupported CSS Property: color
	git commit -m C &&
<span class="pl-s">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
	test_line_count = 1 err
<span class="pl-s">
Unsupported CSS Property: color
else
<span class="pl-k">
Unsupported CSS Property: color
rev
<span class="pl-c1">
Unsupported CSS Property: color
	git checkout --orphan br3 &&
<span class="pl-s">
Unsupported CSS Property: color
-1
<span class="pl-c1">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
REV_CMD_RIGHT
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
2
<span class="pl-c1">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
name
<span class="pl-c1">
Unsupported CSS Property: color
item
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
	 * at random.
<span class="pl-c">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
'diff with two merge bases'
<span class="pl-s">
Unsupported CSS Property: color
>
<span class="pl-c1">
Unsupported CSS Property: color
/* don't mark B */
<span class="pl-c">
Unsupported CSS Property: color
name
<span class="pl-c1">
Unsupported CSS Property: color
left
<span class="pl-c1">
Unsupported CSS Property: color
	 * are any revs that aren't from these sources, we have a
<span class="pl-c">
Unsupported CSS Property: color
1
<span class="pl-c1">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
const
<span class="pl-k">
Unsupported CSS Property: color
2
<span class="pl-c1">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
"   or: git diff [<options>] <commit>...<commit>] [--] [<path>...]\n"
<span class="pl-s">
Unsupported CSS Property: color
		 * base and B.  Note that we pick one merge base at
<span class="pl-c">
Unsupported CSS Property: color
"cache.h"
<span class="pl-s">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
const
<span class="pl-k">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
 *    which there might be many, and A in A...B).  Note that the
<span class="pl-c">
Unsupported CSS Property: color
2
<span class="pl-c1">
Unsupported CSS Property: color
symdiff
<span class="pl-smi">
Unsupported CSS Property: color
 *  - warn is set if there are multiple merge bases.
<span class="pl-c">
Unsupported CSS Property: color
	tail -n 1 tmp >actual &&
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
bitmap_get
<span class="pl-en">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
bitmap
<span class="pl-smi">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
else
<span class="pl-k">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
else
<span class="pl-k">
Unsupported CSS Property: color
case
<span class="pl-k">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
		 * ent.objects[ents-1] == B.  Show diff between the
<span class="pl-c">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
NULL
<span class="pl-c1">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
symdiff
<span class="pl-smi">
Unsupported CSS Property: color
	test_i18ngrep "fatal: br2...br3: no merge base" err
<span class="pl-s">
Unsupported CSS Property: color
	 * We could get N tree-ish in the rev.pending_objects list.
<span class="pl-c">
Unsupported CSS Property: color
object_array_entry
<span class="pl-smi">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
cmdline
<span class="pl-c1">
Unsupported CSS Property: color
object
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
REV_CMD_REV
<span class="pl-c1">
Unsupported CSS Property: color
flags
<span class="pl-c1">
Unsupported CSS Property: color
die
<span class="pl-en">
Unsupported CSS Property: color
pending
<span class="pl-c1">
Unsupported CSS Property: color
# output as well.
<span class="pl-c">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
case
<span class="pl-k">
Unsupported CSS Property: color
	git tag commit-C &&
<span class="pl-s">
Unsupported CSS Property: color
object
<span class="pl-smi">
Unsupported CSS Property: color
pending
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
&&
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
	 * If we don't have just one merge base, we pick one
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
#!
<span class="pl-c">
Unsupported CSS Property: color
NULL
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
const
<span class="pl-k">
Unsupported CSS Property: color
 * For an actual symmetric diff, *symdiff is set this way:
<span class="pl-c">
Unsupported CSS Property: color
'behavior of diff with symmetric-diff setups'
<span class="pl-s">
Unsupported CSS Property: color
	 * "git diff C A...B" or "git diff A...B C" case.  Or we
<span class="pl-c">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
 * sym->warn is cleared.  The remaining fields are not set.
<span class="pl-c">
Unsupported CSS Property: color
	git tag commit-D &&
<span class="pl-s">
Unsupported CSS Property: color
left
<span class="pl-c1">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
pending
<span class="pl-c1">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
REV_CMD_PARENTS_ONLY
<span class="pl-c1">
Unsupported CSS Property: color
	git commit -m H
<span class="pl-s">
Unsupported CSS Property: color
 */
<span class="pl-c">
Unsupported CSS Property: color
cmdline
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
'diff with no merge bases'
<span class="pl-s">
Unsupported CSS Property: color
	test_i18ngrep "usage" err
<span class="pl-s">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
	git commit -m B &&
<span class="pl-s">
Unsupported CSS Property: color
 *  - base, left, and right point to the names to use in a
<span class="pl-c">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
#     C---D--G   <-- br1
<span class="pl-c">
Unsupported CSS Property: color
	test_must_fail git diff master br1...master >tmp 2>err &&
<span class="pl-s">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
	git checkout master &&
<span class="pl-s">
Unsupported CSS Property: color
==
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
UNINTERESTING
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
DIFF_NO_INDEX_IMPLICIT
<span class="pl-c1">
Unsupported CSS Property: color
	git add f &&
<span class="pl-s">
Unsupported CSS Property: color
"%s...%s: no merge base"
<span class="pl-s">
Unsupported CSS Property: color
builtin_diff_tree
<span class="pl-en">
Unsupported CSS Property: color
==
<span class="pl-c1">
Unsupported CSS Property: color
#include
<span class="pl-k">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
	echo f >f &&
<span class="pl-s">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
		 * between A and B.  We have ent.objects[0] ==
<span class="pl-c">
Unsupported CSS Property: color
	echo c >c &&
<span class="pl-s">
Unsupported CSS Property: color
#define
<span class="pl-k">
Unsupported CSS Property: color
/*
<span class="pl-c">
Unsupported CSS Property: color
	git add b &&
<span class="pl-s">
Unsupported CSS Property: color
	 * so we must check for SYMMETRIC_LEFT too.  The two arrays
<span class="pl-c">
Unsupported CSS Property: color
symdiff_prepare
<span class="pl-en">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
 * weed out all bogus range-based revision specifications, e.g.,
<span class="pl-c">
Unsupported CSS Property: color
bitmap_free
<span class="pl-en">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
nr
<span class="pl-c1">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
==
<span class="pl-c1">
Unsupported CSS Property: color
	git commit --fixup B B.t &&
<span class="pl-s">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
nr
<span class="pl-c1">
Unsupported CSS Property: color
/*
<span class="pl-c">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
left
<span class="pl-c1">
Unsupported CSS Property: color
right
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
	write_script show.sh <<-\EOF &&
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
 *
<span class="pl-c">
Unsupported CSS Property: color
else
<span class="pl-k">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
1
<span class="pl-c1">
Unsupported CSS Property: color
#  H  <-- br3
<span class="pl-c">
Unsupported CSS Property: color
 *    indices that the caller should ignore (extra merge bases, of
<span class="pl-c">
Unsupported CSS Property: color
"color.h"
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
char
<span class="pl-smi">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
->
<span class="pl-c1">
Unsupported CSS Property: color
	test_must_fail git diff master br1..master commit-D >tmp 2>err &&
<span class="pl-s">
Unsupported CSS Property: color
 * "git diff A..B C..D" or "git diff A..B C" get rejected.
<span class="pl-c">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
	test_must_fail git diff br2...br3 >tmp 2>err &&
<span class="pl-s">
Unsupported CSS Property: color
#  - disjoint subgraph (orphan branch, br3...master).
<span class="pl-c">
Unsupported CSS Property: color
 *
<span class="pl-c">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
++
<span class="pl-c1">
Unsupported CSS Property: color
int
<span class="pl-smi">
Unsupported CSS Property: color
==
<span class="pl-c1">
Unsupported CSS Property: color
-
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
"   or: git diff [<options>] <commit> [<commit>...] <commit> [--] [<path>...]\n"
<span class="pl-s">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
cmd_diff
<span class="pl-en">
Unsupported CSS Property: color
const
<span class="pl-k">
Unsupported CSS Property: color
if
<span class="pl-k">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
skip
<span class="pl-c1">
Unsupported CSS Property: color
NULL
<span class="pl-c1">
Unsupported CSS Property: color
object
<span class="pl-smi">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
"config.h"
<span class="pl-s">
Unsupported CSS Property: color
 * Check for symmetric-difference arguments, and if present, arrange
<span class="pl-c">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
builtin_diff_tree
<span class="pl-en">
Unsupported CSS Property: color
"git diff [<options>] [<commit> [<commit>]] [--] [<path>...]"
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
	git merge -m E commit-C &&
<span class="pl-s">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
	git diff br1...master >tmp 2>err &&
<span class="pl-s">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
usage
<span class="pl-en">
Unsupported CSS Property: color
/* do mark A */
<span class="pl-c">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
	echo b >b &&
<span class="pl-s">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
	git merge -m G br2 &&
<span class="pl-s">
Unsupported CSS Property: color
	test_must_fail git diff master br1..master br2..br3 >tmp 2>err &&
<span class="pl-s">
Unsupported CSS Property: color
	echo +f >expect &&
<span class="pl-s">
Unsupported CSS Property: color
	test_must_fail git diff br1...master br2...br3 >tmp 2>err &&
<span class="pl-s">
Unsupported CSS Property: color
#  - normal merge with one merge base (br1...b2r);
<span class="pl-c">
Unsupported CSS Property: color
continue
<span class="pl-k">
Unsupported CSS Property: color
&&
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
	git commit --allow-empty -m A &&
<span class="pl-s">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
"   or: git diff [<options>] <blob> <blob>]\n"
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
char
<span class="pl-smi">
Unsupported CSS Property: color
continue
<span class="pl-k">
Unsupported CSS Property: color
add_object_array
<span class="pl-en">
Unsupported CSS Property: color
==
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
struct
<span class="pl-k">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
nr
<span class="pl-c1">
Unsupported CSS Property: color
for
<span class="pl-k">
Unsupported CSS Property: color
item
<span class="pl-c1">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
	 *
<span class="pl-c">
Unsupported CSS Property: color
objects
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
item
<span class="pl-c1">
Unsupported CSS Property: color
"%s...%s: multiple merge bases, using %s"
<span class="pl-s">
Unsupported CSS Property: color
left
<span class="pl-c1">
Unsupported CSS Property: color
skip
<span class="pl-c1">
Unsupported CSS Property: color
warning
<span class="pl-en">
Unsupported CSS Property: color
	git merge -m D master &&
<span class="pl-s">
Unsupported CSS Property: color
0
<span class="pl-c1">
Unsupported CSS Property: color
type
<span class="pl-c1">
Unsupported CSS Property: color
usage
<span class="pl-en">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
continue
<span class="pl-k">
Unsupported CSS Property: color
==
<span class="pl-c1">
Unsupported CSS Property: color
-1
<span class="pl-c1">
Unsupported CSS Property: color
	echo "$subject: $content"
<span class="pl-s">
Unsupported CSS Property: color
	git checkout -b br1 HEAD^ &&
<span class="pl-s">
Unsupported CSS Property: color
'
<span class="pl-pds">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
warn
<span class="pl-c1">
Unsupported CSS Property: color
	content="$(git diff HEAD^! | tail -n 1)"
<span class="pl-s">
Unsupported CSS Property: color
#   A   X
<span class="pl-c">
Unsupported CSS Property: color
"commit.h"
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
pending
<span class="pl-c1">
Unsupported CSS Property: color
&
<span class="pl-c1">
Unsupported CSS Property: color
#
<span class="pl-c">
Unsupported CSS Property: color
*
<span class="pl-c1">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
base
<span class="pl-c1">
Unsupported CSS Property: color
	subject="$(git show -s --format=%s HEAD)"
<span class="pl-s">
Unsupported CSS Property: color
'
<span class="pl-s">
Unsupported CSS Property: color
=
<span class="pl-c1">
Unsupported CSS Property: color
#      \    /
<span class="pl-c">
Unsupported CSS Property: color
warn
<span class="pl-c1">
Unsupported CSS Property: color

  

    
      

        

          Passed audits
          (25)
          
          
        

        

      
    
      
      
    
  

    
  

    

      
        

          
          
            Properly size images
            
          
          

    
      
      
    
  

        

      
      
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

      

    

  

    

      
        

          
          
            Defer offscreen images
            Potential savings of 2 KiB
          
          

    
      
      
    
  

        

      
      
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

      

    
  
  

    
  


URL
Resource Size
Potential Savings
/assets/split-b930d4a1df45.svg
(github.githubassets.com)
2.3 KiB
2.3 KiB

  

    

      
        

          
          
            Minify CSS
            
          
          

    
      
      
    
  

        

      
      
Minifying CSS files can reduce network payload sizes. Learn more.

      

    

  

    

      
        

          
          
            Minify JavaScript
            
          
          

    
      
      
    
  

        

      
      
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

      

    

  

    

      
        

          
          
            Efficiently encode images
            
          
          

    
      
      
    
  

        

      
      
Optimized images load faster and consume less cellular data. Learn more.

      

    

  

    

      
        

          
          
            Serve images in next-gen formats
            
          
          

    
      
      
    
  

        

      
      
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

      

    

  

    

      
        

          
          
            Enable text compression
            
          
          

    
      
      
    
  

        

      
      
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

      

    

  

    

      
        

          
          
            Preconnect to required origins
            
          
          

    
      
      
    
  

        

      
      
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

      

    

  

    

      
        

          
          
            Avoid multiple page redirects
            
          
          

    
      
      
    
  

        

      
      
Redirects introduce additional delays before the page can be loaded. Learn more.

      

    

  

    

      
        

          
          
            Preload key requests
            
          
          

    
      
      
    
  

        

      
      
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.

      

    

  

    

      
        

          
          
            Use HTTP/2
            
          
          

    
      
      
    
  

        

      
      
HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.

      

    

  

    

      
        

          
          
            Use video formats for animated content
            
          
          

    
      
      
    
  

        

      
      
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

      

    

  

    

      
        

          
          
            Remove duplicate modules in JavaScript bundles
            
          
          

    
      
      
    
  

        

      
      
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. 

      

    

  

    

      
        

          
          
            Avoid serving legacy JavaScript to modern browsers
            Potential savings of 0 KiB
          
          

    
      
      
    
  

        

      
      
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More

      

    
  
  

    
  


URL
Potential Savings
/assets/vendors-node_modules_virtualized-list_es_index_js-no….js
(github.githubassets.com)
0.1 KiB
/assets/vendors-node_modules_virtualized-list_es_index_js-no….js:1:362
(github.githubassets.com)
@babel/plugin-transform-classes

  

    

      
        

          
          
            Avoids enormous network payloads
            Total size was 1,002 KiB
          
          

    
      
      
    
  

        

      
      
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

      

    
  
  

    
  


URL
Transfer Size
/assets/vendors-node_modules_primer_octicons-react_dist_inde….js
(github.githubassets.com)
141.2 KiB
…804/files
(github.com)
84.8 KiB
/assets/behaviors-1e4a69ad752e.js
(github.githubassets.com)
64.7 KiB
/assets/react-lib-1fbfc5be2c18.js
(github.githubassets.com)
59.4 KiB
/assets/primer-08e422afeb43.css
(github.githubassets.com)
49.9 KiB
/assets/global-fcad22128422.css
(github.githubassets.com)
43.9 KiB
/assets/vendors-node_modules_github_file-attachment-element_….js
(github.githubassets.com)
25.5 KiB
/assets/github-2f3974e4587d.css
(github.githubassets.com)
24.4 KiB
/assets/diffs-d287393b3d9c.js
(github.githubassets.com)
21.4 KiB
/assets/vendors-node_modules_github_turbo_dist_turbo_es2017-….js
(github.githubassets.com)
20.9 KiB

  

    

      
        

          
          
            Uses efficient cache policy on static assets
            1 resource found
          
          

    
      
      
    
  

        

      
      
A long cache lifetime can speed up repeat visits to your page. Learn more.

      

    
  
  

    
  


URL
Cache TTL
Transfer Size
/in/46807?s=48&v=4
(avatars.githubusercontent.com)
5 m
3 KiB

  

    

      
        

          
          
            User Timing marks and measures
            
          
          

    
      
      
    
  

        

      
      
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

      

    

  

    

      
        

          
          
            JavaScript execution time
            0.3 s
          
          

    
      
      
    
  

        

      
      
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

      

    
  
  

    
  


URL
Total CPU Time
Script Evaluation
Script Parse
…804/files
(github.com)
377 ms
9 ms
1 ms
/assets/chunk-app_components_diffs_deferred-diff-lines-eleme….js
(github.githubassets.com)
177 ms
43 ms
0 ms
Unattributable
170 ms
3 ms
0 ms
/assets/vendors-node_modules_github_file-attachment-element_….js
(github.githubassets.com)
132 ms
94 ms
1 ms
/assets/github-elements-458e6ff8e072.js
(github.githubassets.com)
100 ms
46 ms
0 ms
/assets/diffs-d287393b3d9c.js
(github.githubassets.com)
78 ms
24 ms
1 ms
/assets/behaviors-1e4a69ad752e.js
(github.githubassets.com)
65 ms
59 ms
2 ms

  

    

      
        

          
          
            Minimizes main-thread work
            1.4 s
          
          

    
      
      
    
  

        

      
      
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

      

    
Category
Time Spent
Script Evaluation
455 ms
Style & Layout
407 ms
Other
388 ms
Parse HTML & CSS
52 ms
Script Parsing & Compilation
27 ms
Rendering
17 ms
Garbage Collection
8 ms

  

    

      
        

          
          
            All text remains visible during webfont loads
            
          
          

    
      
      
    
  

        

      
      
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

      

    

  

    

      
        

          
          
            Minimize third-party usage
            
          
          

    
      
      
    
  

        

      
      
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

      

    

  

    

      
        

          
          
            Avoid large layout shifts
            
          
          

    
      
      
    
  

        

      
      
These DOM elements contribute most to the CLS of the page.

      

    

  

    

      
        

          
          
            Uses passive listeners to improve scrolling performance
            
          
          

    
      
      
    
  

        

      
      
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

      

    

  

    

      
        

          
          
            Avoids document.write()
            
          
          

    
      
      
    
  

        

      
      
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

      

    

  

    

      
        

          
          
            Avoids large JavaScript libraries with smaller alternatives
            0 large libraries found
          
          

    
      
      
    
  

        

      
      
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size. Learn more.

      

    

  

    

  
    
    

      
        
        
      
    

    
99

    
    
Accessibility

  


    
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.

  
NavigationThese are opportunities to improve keyboard navigation in your application.

    

      
        

          
          
            Heading elements are not in a sequentially-descending order
            
          
          

    
      
      
    
  

        

      
      
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.

      

    
Failing Elements
 gitgitgadget-git bot 
<h3 class="f5 text-normal" style="flex: 1 1 auto">

  

    
      

        

          Additional items to manually check
          (10)
          
          
        These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.

        

      
    
      
      
    
  

    
  

    

      
        

          
          
            The page has a logical tab order
            
          
          

    
      
      
    
  

        

      
      
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.

      

    

  

    

      
        

          
          
            Interactive controls are keyboard focusable
            
          
          

    
      
      
    
  

        

      
      
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.

      

    

  

    

      
        

          
          
            Interactive elements indicate their purpose and state
            
          
          

    
      
      
    
  

        

      
      
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.

      

    

  

    

      
        

          
          
            The user's focus is directed to new content added to the page
            
          
          

    
      
      
    
  

        

      
      
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.

      

    

  

    

      
        

          
          
            User focus is not accidentally trapped in a region
            
          
          

    
      
      
    
  

        

      
      
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.

      

    

  

    

      
        

          
          
            Custom controls have associated labels
            
          
          

    
      
      
    
  

        

      
      
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.

      

    

  

    

      
        

          
          
            Custom controls have ARIA roles
            
          
          

    
      
      
    
  

        

      
      
Custom interactive controls have appropriate ARIA roles. Learn more.

      

    

  

    

      
        

          
          
            Visual order on the page follows DOM order
            
          
          

    
      
      
    
  

        

      
      
DOM order matches the visual order, improving navigation for assistive technology. Learn more.

      

    

  

    

      
        

          
          
            Offscreen content is hidden from assistive technology
            
          
          

    
      
      
    
  

        

      
      
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.

      

    

  

    

      
        

          
          
            HTML5 landmark elements are used to improve navigation
            
          
          

    
      
      
    
  

        

      
      
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.

      

    

  

    
      

        

          Passed audits
          (25)
          
          
        

        

      
    
      
      
    
  

    
  

    

      
        

          
          
            [aria-*] attributes match their roles
            
          
          

    
      
      
    
  

        

      
      
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.

      

    

  

    

      
        

          
          
            [aria-hidden="true"] is not present on the document <body>
            
          
          

    
      
      
    
  

        

      
      
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.

      

    

  

    

      
        

          
          
            [aria-hidden="true"] elements do not contain focusable descendents
            
          
          

    
      
      
    
  

        

      
      
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.

      

    

  

    

      
        

          
          
            [role]s have all required [aria-*] attributes
            
          
          

    
      
      
    
  

        

      
      
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.

      

    

  

    

      
        

          
          
            Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
            
          
          

    
      
      
    
  

        

      
      
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.

      

    

  

    

      
        

          
          
            [role]s are contained by their required parent element
            
          
          

    
      
      
    
  

        

      
      
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.

      

    

  

    

      
        

          
          
            [role] values are valid
            
          
          

    
      
      
    
  

        

      
      
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.

      

    

  

    

      
        

          
          
            [aria-*] attributes have valid values
            
          
          

    
      
      
    
  

        

      
      
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.

      

    

  

    

      
        

          
          
            [aria-*] attributes are valid and not misspelled
            
          
          

    
      
      
    
  

        

      
      
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.

      

    

  

    

      
        

          
          
            Buttons have an accessible name
            
          
          

    
      
      
    
  

        

      
      
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.

      

    

  

    

      
        

          
          
            The page contains a heading, skip link, or landmark region
            
          
          

    
      
      
    
  

        

      
      
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.

      

    

  

    

      
        

          
          
            Background and foreground colors have a sufficient contrast ratio
            
          
          

    
      
      
    
  

        

      
      
Low-contrast text is difficult or impossible for many users to read. Learn more.

      

    

  

    

      
        

          
          
            Document has a <title> element
            
          
          

    
      
      
    
  

        

      
      
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.

      

    

  

    

      
        

          
          
            [id] attributes on active, focusable elements are unique
            
          
          

    
      
      
    
  

        

      
      
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.

      

    

  

    

      
        

          
          
            ARIA IDs are unique
            
          
          

    
      
      
    
  

        

      
      
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.

      

    

  

    

      
        

          
          
            <html> element has a [lang] attribute
            
          
          

    
      
      
    
  

        

      
      
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.

      

    

  

    

      
        

          
          
            <html> element has a valid value for its [lang] attribute
            
          
          

    
      
      
    
  

        

      
      
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.

      

    

  

    

      
        

          
          
            Image elements have [alt] attributes
            
          
          

    
      
      
    
  

        

      
      
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

      

    

  

    

      
        

          
          
            Links have a discernible name
            
          
          

    
      
      
    
  

        

      
      
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.

      

    

  

    

      
        

          
          
            Lists contain only <li> elements and script supporting elements (<script> and <template>).
            
          
          

    
      
      
    
  

        

      
      
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.

      

    

  

    

      
        

          
          
            List items (<li>) are contained within <ul> or <ol> parent elements
            
          
          

    
      
      
    
  

        

      
      
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.

      

    

  

    

      
        

          
          
            [user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
            
          
          

    
      
      
    
  

        

      
      
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.

      

    

  

    

      
        

          
          
            No element has a [tabindex] value greater than 0
            
          
          

    
      
      
    
  

        

      
      
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.

      

    

  

    

      
        

          
          
            Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
            
          
          

    
      
      
    
  

        

      
      
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.

      

    

  

    

      
        

          
          
            <th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
            
          
          

    
      
      
    
  

        

      
      
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.

      

    

  

    
      

        

          Not applicable
          (15)
          
          
        

        

      
    
      
      
    
  

    
  

    

      
        

          
          
            [accesskey] values are unique
            
          
          

    
      
      
    
  

        

      
      
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.

      

    

  

    

      
        

          
          
            ARIA input fields have accessible names
            
          
          

    
      
      
    
  

        

      
      
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

      

    

  

    

      
        

          
          
            ARIA toggle fields have accessible names
            
          
          

    
      
      
    
  

        

      
      
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

      

    

  

    

      
        

          
          
            <dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
            
          
          

    
      
      
    
  

        

      
      
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.

      

    

  

    

      
        

          
          
            Definition list items are wrapped in <dl> elements
            
          
          

    
      
      
    
  

        

      
      
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.

      

    

  

    

      
        

          
          
            No form fields have multiple labels
            
          
          

    
      
      
    
  

        

      
      
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.

      

    

  

    

      
        

          
          
            <frame> or <iframe> elements have a title
            
          
          

    
      
      
    
  

        

      
      
Screen reader users rely on frame titles to describe the contents of frames. Learn more.

      

    

  

    

      
        

          
          
            <input type="image"> elements have [alt] text
            
          
          

    
      
      
    
  

        

      
      
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.

      

    

  

    

      
        

          
          
            Form elements have associated labels
            
          
          

    
      
      
    
  

        

      
      
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

      

    

  

    

      
        

          
          
            Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.
            
          
          

    
      
      
    
  

        

      
      
A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.

      

    

  

    

      
        

          
          
            The document does not use <meta http-equiv="refresh">
            
          
          

    
      
      
    
  

        

      
      
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.

      

    

  

    

      
        

          
          
            <object> elements have [alt] text
            
          
          

    
      
      
    
  

        

      
      
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.

      

    

  

    

      
        

          
          
            [lang] attributes have a valid value
            
          
          

    
      
      
    
  

        

      
      
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.

      

    

  

    

      
        

          
          
            <video> elements contain a <track> element with [kind="captions"]
            
          
          

    
      
      
    
  

        

      
      
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.

      

    

  

    

      
        

          
          
            <video> elements contain a <track> element with [kind="description"]
            
          
          

    
      
      
    
  

        

      
      
Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes. Learn more.