Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Google PageSpeed Tools

From Wikipedia, the free encyclopedia
Online service by Google
This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages)
Some of this article'slisted sourcesmay not bereliable. Please help improve this article by looking for better, more reliable sources. Unreliable citations may be challenged and removed.(March 2017) (Learn how and when to remove this message)
This articlecontainspromotional content. Please helpimprove it by removingpromotional language and inappropriateexternal links, and by adding encyclopedic text written from aneutral point of view.(March 2022) (Learn how and when to remove this message)
(Learn how and when to remove this message)

Google PageSpeed is a family of tools byGoogle, Inc.[1] designed to helpoptimize website performance.[2] It was introduced at aDeveloper Conference in 2010.[3][4]There are four main components of PageSpeed family tools:

PageSpeed Modules

[edit]

ThePageSpeed Modules are theopen-sourceApache HTTP Server orNginx web server modules, which automatically apply chosen filters to pages, associated assets (likestylesheets,JavaScript, andHTML files), as well as to images andwebsite cache requirements. These modules do not require modifications to existing content or workflow,[8] meaning that all internal optimizations and changes to files are made on the server side, and present modified files directly to the user. Each of the 40+ filters corresponds to one of Google's web performance best practices rules.

Since the PageSpeed module is anopen-source library, it is frequently updated by numerous developers worldwide. It can be deployed by any individual site,hosting providers, orCDNs.[9]

The installation can be done in two ways: from packages or built from source on the following supported platforms:

Ports

[edit]

Other servers that offer a PageSpeed optimization module based on Google's Page Speed SDK:

Filters

[edit]

PageSpeed module filters are settings, based on which a web page optimization rule is applied. They can be divided into five main categories:

Speed impact

[edit]

The PageSpeed Module showed the most significant impact on decreasing web page loading times, payload size, and number of requests compared to other industry options. According to several researchers, 'mod_pagespeed' can reduce loading times by up to 80%, the number of bytes on a wire can be decreased by 30%, and the number of total requests can drop by over 20%. Since many search engines, including Google, employ a ranking algorithm that is affected by a page's loading speed, these optimizations can impact a website's placement in search results.[12][13] As of February 2015, Google has begun testing “Slow” labels on mobile devices[14] for websites that exceed a certain amount of loading time, prompting developers to examine ways to increase a page's load speed.

Google estimates that for every delay in mobile page load time, the conversion rate drops by 20%.[15]

PageSpeed Insights (PSI)

[edit]

PageSpeed Insights (PSI) is a free tool from Google that analyzes the performance of a web page on both mobile and desktop devices. It provides suggestions on how to improve the page's speed and overall user experience.

Data and Metrics

PSI utilizestwo main types of data:

  • Lab Data: Collected in a controlled environment using Lighthouse to simulate user experience. Useful for debugging performance issues.
  • Field Data: Real-world user experience data gathered from theChrome User Experience Report (CrUX) dataset. This data includes metrics like First Contentful Paint (FCP), Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).

Real-User Experience Data

PSI leverages CrUX data to provide insights into real user experiences. It reports on various metrics over a 28-day period, including:

  • First Contentful Paint (FCP): Time taken for the first content to render on the page.
  • Largest Contentful Paint (LCP): Time taken for the main content of the page to render.
  • Interaction to Next Paint (INP): Time taken for the page to become interactive after the user interacts with it.
  • Cumulative Layout Shift (CLS): Measures the amount of unexpected layout shift a user experiences during page load.
  • Time to First Byte (TTFB) (Experimental): Time taken for the browser to receive the first byte of response from the server.
  • First Input Delay (FID) (Deprecated): Measures the time it takes for a user interaction to be reflected on the page (no longer recommended by Google).

PSI classifies these metrics into three categories based on Web Vitals thresholds: Good, Needs Improvement, and Poor.

Core Web Vitals

A subset of the field data metrics,Core Web Vitals, are critical for a good user experience. These include LCP, INP, and CLS. PSI analyzes these metrics to determine if a page meets the Core Web Vitals assessment criteria. These are also used as aSEO ranking signal.

Lab Diagnostics

PSI usesLighthouse to analyze a web page in a simulated environment. It provides scores and recommendations for various categories like Performance, Accessibility, Best Practices, and SEO. The Performance category includes metrics like FCP, LCP, CLS, and Time to Interactive, each with scores and improvement suggestions.

Overall, PSI is a valuable tool for website owners and developers to identify performance bottlenecks and improve the user experience of their web pages.

PageSpeed Chrome Extension

[edit]

Pagespeed extension is anextension of Chrome Browser and is a part ofGoogle Chrome Developer Tools. Visitors who use PageSpeed regularly can view all given metrics by PageSpeed Insights directly in a browser and download webpage resources, optimized according to web performance best practices. It has now been deprecated[16] and Google recommends the online version be used instead.

PageSpeed Service

[edit]

PageSpeed service was a commercial product, provided by Google Inc. The service was offered free of charge since it was still officially in beta version. Service included all Pagespeed Module optimizations and use of Google servers’ infrastructure.[17] Google announced the deprecation of PageSpeed service on 5 May 2015[18] and turned it off on 3 August 2015.[19]

PageSpeed is now a critical tool for businesses looking to rank their website on search engines organically, given that 47% of users abandon websites that take longer than 2 seconds to load.[20]

See also

[edit]

References

[edit]
  1. ^"About PageSpeed Insights".Google Developers. Retrieved2022-08-13.
  2. ^Ivanovs, Alex (16 April 2014)."PageSpeed Module: Improving Your Websites' Performance".huffingtonpost.com/. The Huffington Post. Retrieved23 March 2015.
  3. ^Kerner, Sean Michael (4 November 2010)."Google Speeds Up the Web with Apache Web Server Module".serverwatch.com/news/. Retrieved23 March 2015.
  4. ^Ram, Ramani (2011-07-29)."Page Speed Service: Web performance, delivered".googlecode.blogspot.com/. Retrieved17 March 2015.
  5. ^"Github".github.com. Google Inc. Retrieved6 August 2020.
  6. ^"Github".github.com. Google Inc. Retrieved6 August 2020.
  7. ^"Apache Incubator".modpagespeed.com/. Google Inc. Retrieved6 August 2020.
  8. ^Edwards, Ben (2014-07-28)."Authoring critical above-the-fold CSS".benedfit.com. Retrieved23 March 2015.
  9. ^"PageSpeed Insights SDK".code.google.com. Google Inc. Retrieved23 March 2015.
  10. ^"ats_pagespeed".iispeed.com/. IISpeed B.V. Archived fromthe original on 2015-05-25. Retrieved2015-05-25.
  11. ^"IIS WebSpeed".iiswebspeed.com/. IISpeed B.V.
  12. ^Enge, Eric (2011-03-06)."Case Study: Impact of Code Cleanup on Site Traffic".searchenginewatch.com/. Search Engine Watch. Retrieved23 March 2015.
  13. ^Kuchler, Margaret (19 May 2011)."The Growing Need For Speed: How Site Performance Increasingly Influences Search Rankings".retailtouchpoints.com/. Retail Touch Points. Retrieved23 March 2015.
  14. ^Barry, Shwartz (2015-02-25)."Google Testing A Red "Slow" Label In The Search Results For Slower Sites".searchengineland.com/. Retrieved17 March 2015.
  15. ^"Mobile Page Load Delay Causes Conversion Loss".Think with Google. Retrieved2024-05-23.
  16. ^"PageSpeed Insights | PageSpeed Insights | Google Developers".Google Developers. Retrieved2016-09-08.
  17. ^Lardinois, Frederic (3 August 2012)."Google Updates PageSpeed Service, Promises To "Turbocharge Your Website"".techcrunch.com. The Tech Crunch. Retrieved23 March 2015.
  18. ^"Google Groups".groups.google.com. Retrieved7 February 2019.
  19. ^"Turndown information for PageSpeed Service - PageSpeed Service".Google Developers. Retrieved7 February 2019.
  20. ^Dentten, Will (Dec 6, 2024)."Google Pagespeed Insights: Why Is It Important".Test Valley Digital.

External links

[edit]
a subsidiary ofAlphabet
Company
Divisions
Subsidiaries
Active
Defunct
Programs
Events
Infrastructure
People
Current
Former
Criticism
General
Incidents
Other
Software
A–C
D–N
O–Z
Operating systems
Language models
Neural networks
Computer programs
Formats and codecs
Programming languages
Search algorithms
Domain names
Typefaces
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
Y
Hardware
Pixel
Smartphones
Smartwatches
Tablets
Laptops
Other
Nexus
Smartphones
Tablets
Other
Other
Advertising
Antitrust
Intellectual
property
Privacy
Other
Related
Concepts
Products
Android
Street View coverage
YouTube
Other
Documentaries
Books
Popular culture
Other
Retrieved from "https://en.wikipedia.org/w/index.php?title=Google_PageSpeed_Tools&oldid=1279256160"
Category:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp