Navigation Timing

navigation-timing

https://www.w3.org/TR/navigation-timing/

Introduction

This section is non-normative.
User latency is an important quality benchmark for Web Applications. While script-based mechanisms, such as the one described in [JSMEASURE], can provide comprehensive instrumentation for user latency measurements within an application, in many cases, they are unable to provide a complete end-to-end latency picture.

For example, the following script shows a naive attempt to measure the time it takes to fully load a page:

<!- Main page body goes from here. -->

http://.......cat/prova-navigation-timing.html 

resultat 

page loading time: 6

The script calculates the time it takes to load the page after the first bit of JavaScript in the head is executed, but it does not give any information about the time it takes to get the page from the server.
To address the need for complete information on user experience, this document introduces the PerformanceTiming interfaces. This interface allows JavaScript mechanisms to provide complete client-side latency measurements within applications. With the proposed interface, the previous example can be modified to measure a user's perceived page load time.

The following script calculates how much time to load a page since the most recent navigation.

<!- Main page body goes from here. -->

http://.......cat/prova-navigation-timing2.html  

resultat 

User-perceived page loading time: 54

The interface provided by this work does not intend to be used as any sort of performance benchmark for user agents.

continuant del document

https://www.w3.org/TR/navigation-timing/timing-overview.png

https://developers.google.com/web/fundamentals/performance/navigation-and-resource-timing/


m'he de mirar el contingut

https://github.com/micmro/performance-bookmarklet
https://github.com/andydavies/waterfall


pero finalment he anat a web de proves de temps de carrega

https://www.webpagetest.org/

Web Page Performance Test for
ies-sabadell.cat

From: Dulles, VA - Chrome - Cable
10/9/2018, 10:01:42

• Summary
• Details
• Performance Review
• Content Breakdown
• Domains
• Processing Breakdown
• Screen Shot
• Image Analysis
• Request Map

Tester: VM2-01-192.168.11.98
First View only
Test runs: 3

Raw page data - Raw object data
Export HTTP Archive (.har)
View Test Log

Performance Results (Median Run)

						Document Complete			Fully Loaded
	Load Time	First Byte	Start Render	Speed Index	First Interactive (beta)	Time	Requests	Bytes In	Time	Requests	Bytes In	Cost
First View (Run 2)	21.449s	1.432s	3.600s	4039	10.070s	21.449s	137	10,747 KB	21.652s	138	10,748 KB	$$$$$

https://testmysite.withgoogle.com/intl/en-gb

https://frontal.ies-sabadell.cat/cicles-moodle

Loading time:

This is Speed Index, how long the visible content of your page takes to appear using Chrome on a Moto G4 device within a 3G network. Loading time can vary based on server location, device, browser, and third-party apps. If your site contains carousels, overlays or interstitials, this may impact your loading time results. To perform a website speed test using different settings, visit webpagetest.org.

Estimated visitor loss:

This is the probability of a user leaving this web page as a result of waiting for more than three seconds for it to load. [Source]

5s

Loading time on 3G: Good

19%

Est. Visitor loss

(Due to loading time)

altres
https://developers.google.com/speed/pagespeed/insights/?url=ies-sabadell.cat&tab=mobile

https://developers.google.com/speed/pagespeed/insights/?url=ies-sabadell.cat&tab=desktop