resourcetiming-compression.js | ResourceTiming compression and decompression
kandi X-RAY | resourcetiming-compression.js Summary
kandi X-RAY | resourcetiming-compression.js Summary
resourcetiming-compression.js is a JavaScript library. resourcetiming-compression.js has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i resourcetiming-compression' or download it from GitHub, npm.
resourcetiming-compression.js compresses data from ResourceTiming. A companion script, resourcetiming-decompression.js, converts the compressed data back to the original form. ResourceTiming is a W3C web-perf API that exposes all of the page's resources' network timing information to the developer and is available in most modern browsers. The interface performance.getEntriesByType('resource') returns a list of resources with information about each resource's URL, why it was downloaded, and a dozen timestamps. Collecting this information is easy, but beaconing all of this data back to a data warehouse can be a challenge because of the amount of data available for each resource. On a typical page, which might have over 100 resources, you could easily see 50 KB of ResourceTiming data per page-load. resourcetiming-compression.js applies several data-compression techniques to reduce the size of your serialized ResourceTiming data to about 15% of it's original size in many cases. See this nicj.net blog post for a description of these techniques. resourcetiming-decompression.js is a companion script that will take the compressed ResourceTiming data and builds it back to its original ResourceTiming form (eg. performance.getEntriesByType('resource')) for analysis. NOTE: resourcetiming-compression.js is the same code that drives the restiming.js plugin for Boomerang, but also includes the resourcetiming-decompression.js component.
resourcetiming-compression.js compresses data from ResourceTiming. A companion script, resourcetiming-decompression.js, converts the compressed data back to the original form. ResourceTiming is a W3C web-perf API that exposes all of the page's resources' network timing information to the developer and is available in most modern browsers. The interface performance.getEntriesByType('resource') returns a list of resources with information about each resource's URL, why it was downloaded, and a dozen timestamps. Collecting this information is easy, but beaconing all of this data back to a data warehouse can be a challenge because of the amount of data available for each resource. On a typical page, which might have over 100 resources, you could easily see 50 KB of ResourceTiming data per page-load. resourcetiming-compression.js applies several data-compression techniques to reduce the size of your serialized ResourceTiming data to about 15% of it's original size in many cases. See this nicj.net blog post for a description of these techniques. resourcetiming-decompression.js is a companion script that will take the compressed ResourceTiming data and builds it back to its original ResourceTiming form (eg. performance.getEntriesByType('resource')) for analysis. NOTE: resourcetiming-compression.js is the same code that drives the restiming.js plugin for Boomerang, but also includes the resourcetiming-decompression.js component.
Support
Quality
Security
License
Reuse
Support
resourcetiming-compression.js has a low active ecosystem.
It has 51 star(s) with 14 fork(s). There are 6 watchers for this library.
It had no major release in the last 12 months.
There are 1 open issues and 7 have been closed. On average issues are closed in 149 days. There are 8 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of resourcetiming-compression.js is v1.3.1
Quality
resourcetiming-compression.js has 0 bugs and 0 code smells.
Security
resourcetiming-compression.js has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
resourcetiming-compression.js code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
resourcetiming-compression.js is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
resourcetiming-compression.js releases are available to install and integrate.
Deployable package is available in npm.
Installation instructions, examples and code snippets are available.
resourcetiming-compression.js saves you 10 person hours of effort in developing the same functionality from scratch.
It has 30 lines of code, 0 functions and 13 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of resourcetiming-compression.js
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of resourcetiming-compression.js
resourcetiming-compression.js Key Features
No Key Features are available at this moment for resourcetiming-compression.js.
resourcetiming-compression.js Examples and Code Snippets
No Code Snippets are available at this moment for resourcetiming-compression.js.
Community Discussions
No Community Discussions are available at this moment for resourcetiming-compression.js.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install resourcetiming-compression.js
Releases are available for download from GitHub. Development: resourcetiming-compression.js - 30kb. Production: resourcetiming-compression.min.js - 2.4kb (minified / gzipped). Development: resourcetiming-decompression.js - 8.8kb. Production: resourcetiming-decompression.min.js - 1kb (minified / gzipped).
Support
We call contribution of a resource to a page the proportion of the total load time that can be blamed on that resource. We want contribution scores to encourage parallelization and not only short resources. It enables us to study resource impact in a more meaningful way over simply looking at raw load times.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page