Saying "Basically it’s graphical representation of pace of the script and the granularity is at the scene level." and linking to "a graphical representation of the pace of the script" doesn't answer "how do you read it?".  It's called a Pace Graph, which pretty much means "a graphical representation of the pace of the script" just in the name.  But how do you read it. I think the confusion, if any, come from that fact that there's no such thing as a unit of pace.  One assumes that a higher pace number is better but ...  is it?   Could it be that higher numbers show where your script is bogged down? Probably not but nowhere is there an explanation. Why does the example of the pace for Babel that you link to max out at 70 "units of pace".  With an arbitrary unit such as this why not make the scale 0 to 100?  The pace scale on the script I justr started maxes out at 50.  Do the graphs just go to whatever the max pace in your script is and just not show the rest of the chart above your max pace?  What is the max pace then? 70? 100? 1200

So I assume higher pace numbers are better - yes?

I assume of you look at the graph riding along the top of your page numbers you can detect fast paced stretches (where the graph line flows consistiently high), low pace stretches (where the graph line travels along lower numbers), and varied pace sections which would look like spikes and valleys - yes?

Why doesn't your scale go to 100 since the units are arbitrary in the first place? (Actually I assume it does go to 100 - you just don't show the rest of the scale unless the script's pace rates high enough, right?)

There should probably be a definition and some tips like the above beyond just a definition which is basically the definition of any graph - "A visual representation of X, based on analysis of X"  Especially since "Pace" is not a real unit like miles or MPH, etc.