A method, device and medium for detecting loading of web page opening speed

Abstract

This invention discloses a method, device, and medium for detecting webpage loading speed, belonging to the field of webpage detection technology. It addresses the technical problem that existing methods for webpage loading speed detection are difficult to perform intuitively, making it inconvenient for users to promptly grasp the specific loading status of webpages and reducing the user's webpage browsing experience. The method includes: monitoring the performance navigation time during webpage loading based on the user's webpage request information to obtain stage indicator data; performing parameter analysis on the stage indicator data related to time values ​​to determine the stage indicator time; wherein, the stage indicator time includes: page load time, first byte time, DNS time, and TCP time; applying a time threshold to the stage indicator time to obtain webpage opening result information; and feeding back the webpage opening result information to the user's operation page.

Description

Technical Field

[0001] The present application relates to the technical field of web page detection, and in particular to a method, device and medium for detecting the loading speed of a web page. Background Art

[0002] With the continuous development of the Internet and the popularity of mobile devices, more and more users access the web through mobile phones or tablets. Mobile networks may be relatively slow, and mobile devices have smaller screens, so users are more sensitive to fast-loading web pages. The speed at which web pages open also affects the experience of mobile users. The speed of web page opening is directly related to the user experience. Modern users have high expectations for web page loading speed because fast loading time can provide a better user experience. Users are usually more willing to spend time browsing content rather than waiting for pages to load.

[0003] Based on this, there is an urgent need for a web page opening detection method to allow users to know the speed of currently opening web pages more conveniently and intuitively, thereby improving the user experience. Summary of the invention

[0004] The embodiments of the present application provide a loading detection method, device and medium for the opening speed of a web page, which are used to solve the following technical problems: the opening speed of existing web pages is difficult to detect intuitively, which makes it inconvenient for users to grasp the specific loading status of the web page in a timely manner, thereby reducing the user's web browsing experience.

[0005] The present application embodiment adopts the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides a loading detection method for web page opening speed, including: based on the user's web page request information, data monitoring of the performance navigation time in the web page loading to obtain stage indicator data; performing parameter analysis on the stage indicator data related to the time value to determine the stage indicator time in the stage indicator data; wherein the stage indicator time includes: page loading time, first byte time, DNS time and TCP time; performing time threshold judgment on the stage indicator time to obtain web page opening result information; and feeding back the web page opening result information to the user's operation page.

[0007] The embodiment of the present application analyzes the indicator data of the performance indicators in the web page Web: page loading time, first byte time, DNS time and TCP time, so as to better feedback the opening speed of the web page that the user wants to access, and combined with the subsequent indicator threshold judgment, it is conducive to accurately detecting the opening and loading speed of the actual web page according to the specific situation of the web page opening, and is conducive to intuitive speed detection of the opening speed of the web page, so that the user can grasp the specific loading situation of the web page in time, which greatly improves the user's web browsing experience.

[0008] In a feasible implementation, based on the user's web page request information, data monitoring is performed on the performance navigation time in web page loading to obtain stage indicator data, specifically including: obtaining the timestamp data of the web page corresponding to the web page request information through the performance timing API; wherein the performance timing API is an interface in Web development, and is used to provide time-related data on various events in the web page loading and navigation process; according to the time stage when the web page request information is executed, the timestamp data is divided into full time periods to obtain the stage indicator data; wherein the stage indicator data includes: page loading stage, first byte stage, DNS stage and TCP stage.

[0009] In a feasible implementation manner, the stage indicator data is subjected to parameter analysis related to time values ​​to determine the stage indicator time in the stage indicator data, including: determining the triggering of a loading event in the page loading stage in the stage indicator data; if the loading event is in a triggered state, calculating the difference time between the loading end time node and the loading start time node in the loading event through a performance timing API to obtain the page loading time in the triggered state; wherein the triggered state is that the CSS, JS9 and image resources referenced by HTML are all in a loaded state; if the loading event is in an untriggered state, performing a waiting timing process related to the triggering state on the loading event through the performance timing API to obtain the waiting trigger time; until the loading event is in a triggered state, the waiting trigger time and the difference time are added to obtain the page loading time in the untriggered state.

[0010] In a feasible implementation manner, the stage indicator data is subjected to parameter analysis related to time values ​​to determine the stage indicator time in the stage indicator data, including: dividing the first byte stage in the stage indicator data by time; obtaining the TCP connection time between the web page request information and the web page server based on the receiving process of the web page request information; obtaining the HTTP request time sent by the web page request information based on the TCP connection time; obtaining the byte response time of the web page server responding to the first byte in the web page request information based on the HTTP request time; and adding the TCP connection time, the HTTP request time and the byte response time through a performance timing API to obtain the first byte time in the stage indicator time.

[0011] In a feasible implementation, a parameter analysis of relevant time values ​​is performed on the stage indicator data to determine the stage indicator time in the stage indicator data, including: obtaining the domain name resolution data of the DNS stage in the stage indicator data; and calculating the difference time between the domain lookup end time node and the domain lookup start time node of the domain name resolution data through a performance timing API to obtain the DNS time in the stage indicator time.

[0012] In a feasible implementation manner, the stage indicator data is subjected to parameter analysis related to time values ​​to determine the stage indicator time in the stage indicator data, including: obtaining interface connection data of the TCP stage in the stage indicator data according to the web page request information; wherein the interface connection data is connection data between a web page client and a web page server; and calculating the difference time between a connection establishment end time node and a connection establishment start time node for the interface connection data through a performance timing API to obtain the TCP time in the stage indicator time.

[0013] In a feasible implementation manner, the stage indicator time is subjected to a time threshold judgment to obtain web page opening result information, specifically including: integrating the page loading time, the first byte time, the DNS time and the TCP time in the stage indicator time to obtain a total stage indicator time; conducting a time threshold judgment on the total stage indicator time; if the total stage indicator time is less than or equal to a first preset time threshold, the web page opening speed is determined as fast opening information; if the total stage indicator time is greater than the first preset time threshold and less than or equal to a second preset time threshold, the web page opening speed is determined as normal opening information; if the total stage indicator time is greater than the second preset time threshold and less than or equal to a third preset time threshold, the web page opening speed is determined as relatively slow opening information; if the total stage indicator time is greater than the third preset time threshold, the web page opening speed is determined as very slow opening information; wherein the web page opening result information includes: the fast opening information, the normal opening information, the relatively slow opening information and the very slow opening information.

[0014] In a feasible implementation, the web page opening result information is fed back to the user's operation page, specifically including: sending the web page opening result information to the user's web client; and visually displaying it on the operation page; when the data tag of the web page opening result information is re-detection information, re-acquiring the timestamp data of the web page corresponding to the re-detection information through a performance timing API; and performing a loading test on the timestamp data regarding the web page opening speed.

[0015] In a second aspect, an embodiment of the present application also provides a loading detection device for the opening speed of a web page, the device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, so that the at least one processor can execute a loading detection method for the opening speed of a web page as described in any of the above-mentioned embodiments.

[0016] In a third aspect, an embodiment of the present application further provides a non-volatile computer storage medium, characterized in that the storage medium is a non-volatile computer-readable storage medium, and the non-volatile computer-readable storage medium stores at least one program, each of which includes instructions, and when the instructions are executed by a terminal, the terminal executes a loading detection method for the opening speed of a web page as described in any of the above-mentioned embodiments.

[0017] The present application provides a loading detection method, device and medium for the opening speed of a web page. By analyzing the performance indicators of a web page Web: page loading time, first byte time, DNS time and TCP time, the indicator data can better feedback the opening speed of the web page that the user wants to access. In combination with the subsequent indicator threshold judgment, it is conducive to accurately detecting the opening and loading speed of the actual web page according to the specific situation of the web page opening, which is conducive to intuitive speed detection of the opening speed of the web page, making it convenient for users to timely grasp the specific loading situation of the web page, and greatly improving the user's web browsing experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0019] Figure 1 A flow chart of a method for detecting the speed of opening a web page provided in an embodiment of the present application;

[0020] Figure 2 An overall flow chart of a web page opening speed detection method provided in an embodiment of the present application;

[0021] Figure 3 A schematic diagram of the structure of a loading detection device for web page opening speed provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0023] The present application embodiment provides a method for detecting the loading speed of a web page opening. Figure 1 As shown, the loading detection method for web page opening speed specifically includes steps S101-S104:

[0024] It should be noted that the web page opening speed usually refers to the time from when the user initiates a request to access a web page to when the web page is fully loaded and displayed. Performance Timing API: This is an interface in web development that is used to provide time-related information about various events during web page loading and navigation.

[0025] S101. Based on the user's web page request information, data of the performance navigation time during web page loading is monitored to obtain stage indicator data.

[0026] Specifically, the timestamp data of the web page corresponding to the web page request information is obtained through the performance timing API, wherein the performance timing API is an interface in Web development and is used to provide time-related data of various events in the process of web page loading and navigation.

[0027] Furthermore, according to the time stage when the webpage request information is executed, the timestamp data is divided into full time periods to obtain stage indicator data, wherein the stage indicator data includes: page loading stage, first byte stage, DNS stage and TCP stage.

[0028] In one embodiment, Figure 2 The overall flow chart of a web page opening speed detection provided by the embodiment of the present application is as follows: Figure 2 As shown, first, according to the web page request information after the user's operation, that is, based on the user's first operation, a web page is opened, and the web page loading and opening speed is detected throughout the whole process until the web page is loaded. Then, the timestamps of each time period of the entire life cycle of the current web page opening are obtained through the Performance Timing API of the web page, and the stage indicator data of the entire process of the entire web page opening is collected.

[0029] As a feasible implementation method, the entire webpage monitoring opening process is to execute Performance Navigation Timing in the API callback after the webpage opening is completed to complete the statistics of the time of each time period of the webpage opening.

[0030] S102, performing parameter analysis on the phase indicator data in terms of time values, and determining the phase indicator time in the phase indicator data, wherein the phase indicator time includes: page loading time, first byte time, DNS time, and TCP time.

[0031] Specifically, the triggering determination of the loading event is performed on the page loading stage in the stage indicator data:

[0032] If the loading event is in the triggered state, the performance timing API is used to calculate the difference between the loading end time node and the loading start time node in the loading event to obtain the page loading time in the triggered state. The triggered state is when the CSS, JS9 and image resources referenced by the HTML are all in the loaded state.

[0033] If the loading event is in the untriggered state, the performance timing API is used to perform the waiting timing processing on the loading event for the trigger state, and the waiting trigger time is obtained. When the loading event is in the triggered state, the waiting trigger time is added to the difference time to obtain the page loading time in the untriggered state.

[0034] In one embodiment, Figure 2 As shown in the figure, it is the time from the page starts loading to the page onload event is triggered. Generally speaking, onload triggering means that CSS (Cascading Style Sheets), JS9 (scripts), image resources directly referenced by HTML have been completely loaded. Through Performance Navigation Timing, i.e., the performance timing API, the difference between load event end (load end time node) and start time (load start time node) is taken to calculate the page loading time.

[0035] Furthermore, the first byte stage in the stage indicator data is divided into time periods:

[0036] Based on the receiving process of the webpage request information, the TCP connection time between the webpage request information and the webpage server is obtained. Based on the TCP connection time, the HTTP request time sent by the webpage request information is obtained. Based on the HTTP request time, the byte response time of the first byte in the webpage request information in response to the webpage server is obtained.

[0037] Furthermore, the TCP connection time, HTTP request time and byte response time are added together through the performance timing API to obtain the first byte time in the stage indicator time.

[0038] In one embodiment, Figure 2As shown in the figure, the first byte time is the time from when the initial network request information is initiated to when the first byte is received from the server. It includes the TCP connection time, the time to send the HTTP request, and the time to get the first byte of the response message. Since the more web page redirects, the higher the TTFB, so we need to reduce redirects. The response Start-start Time is obtained through PerformanceNavigation Timing, which is the first byte time of the response first byte stage.

[0039] Furthermore, the domain name resolution data of the DNS stage in the stage indicator data is obtained. Through the performance timing API, the difference time between the domain lookup end time node and the domain lookup start time node is calculated for the domain name resolution data to obtain the DNS time in the stage indicator time.

[0040] Further, according to the webpage request information, the interface connection data of the TCP stage in the stage indicator data is obtained. The interface connection data is the connection data between the webpage client and the webpage server. Through the performance timing API, the difference time between the connection establishment end time node and the connection establishment start time node is calculated for the interface connection data to obtain the TCP time in the stage indicator time.

[0041] S103: Perform time threshold judgment on the stage indicator time to obtain web page opening result information.

[0042] Specifically, the page loading time, first byte time, DNS time and TCP time in the stage indicator time are integrated to obtain the total stage indicator time, and then the time threshold is determined for the total stage indicator time.

[0043] If the total stage indicator time is less than or equal to the first preset time threshold, the web page opening speed is determined as fast opening information.

[0044] If the total stage indicator time is greater than the first preset time threshold and less than or equal to the second preset time threshold, the web page opening speed is determined as normal opening information.

[0045] If the total stage indicator time is greater than the second preset time threshold and less than or equal to the third preset time threshold, the webpage opening speed is determined as slow opening information.

[0046] If the total stage indicator time is greater than the third preset time threshold, the webpage opening speed is determined as very slow opening information.

[0047] The web page opening result information includes: fast opening information, normal opening information, slow opening information and very slow opening information.

[0048] In one embodiment, Figure 2 As shown, according to the calculated duration (loading) time, that is, the stage indicator time, the stage indicator time and the set specific distribution time period are judged to obtain the opening status of the current detection page. There are five specific distribution time periods: fast opening information, normal opening information, slow opening information, very slow opening information, and timeout opening information; the corresponding time is within 1 second, 1 to 2 seconds, 2 to 6 seconds, 6 to 8 seconds, and more than 8 seconds.

[0049] S104: Feedback the web page opening result information to the user's operation page.

[0050] Specifically, the web page opening result information is sent to the user's web client and is visually displayed on the operation page.

[0051] Furthermore, when the data tag of the web page opening result information is re-detection information, the timestamp data of the web page corresponding to the re-detection information is re-acquired through the performance timing API, and a loading detection of the web page opening speed is performed on the timestamp data.

[0052] As a feasible implementation method, when the data tag of the web page opening result information is re-detection information, that is, when the user re-selects to detect the web page speed, the entire detection process is repeated to prevent the user from having network deviation during detection, so that the network is normal during re-detection.

[0053] In addition, the embodiment of the present application also provides a loading detection device for the opening speed of a web page, such as Figure 3 As shown, the loading detection device 300 for the web page opening speed specifically includes:

[0054] At least one processor 301. And a memory 302 in communication with the at least one processor 301. The memory 302 stores instructions that can be executed by the at least one processor 301, so that the at least one processor 301 can execute:

[0055] Based on the user's web page request information, the performance navigation time during web page loading is monitored to obtain stage indicator data;

[0056] Perform parameter analysis on the time value of the stage indicator data to determine the stage indicator time in the stage indicator data; wherein the stage indicator time includes: page loading time, first byte time, DNS time and TCP time;

[0057] The stage indicator time is judged by the time threshold to obtain the web page opening result information;

[0058] Feedback the web page opening result information to the user's operation page.

[0059] The present application provides a loading detection method, device and medium for the opening speed of a web page. By analyzing the performance indicators of a web page Web: page loading time, first byte time, DNS time and TCP time, the indicator data can better feedback the opening speed of the web page that the user wants to access. In combination with the subsequent indicator threshold judgment, it is conducive to accurately detecting the opening and loading speed of the actual web page according to the specific situation of the web page opening, which is conducive to intuitive speed detection of the opening speed of the web page, making it convenient for users to timely grasp the specific loading situation of the web page, and greatly improving the user's web browsing experience.

[0060] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0061] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0062] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0063] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0064] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0065] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0066] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0067] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the embodiments of the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for detecting the loading speed of a web page, characterized in that: The method comprises: Based on the user's web page request information, the performance navigation time during web page loading is monitored to obtain stage indicator data; Performing parameter analysis on the stage indicator data regarding time values ​​to determine the stage indicator time in the stage indicator data, wherein the stage indicator time includes: page loading time, first byte time, DNS time, and TCP time; The page loading time includes: Performing triggering determination of a loading event on the page loading stage in the stage indicator data; If the loading event is in a triggered state, the difference time between the loading end time node and the loading start time node in the loading event is calculated through the performance timing API to obtain the page loading time in the triggered state; wherein the triggered state is that the CSS, JS9 and image resources referenced by HTML are all in a loaded state; If the loading event is in an untriggered state, the loading event is subjected to a waiting timing process related to the trigger state through the performance timing API, and the waiting trigger time is obtained; until the loading event is in a triggered state, the waiting trigger time is added to the difference time to obtain the page loading time in the untriggered state; The first byte time includes: Dividing the time of the first byte stage in the stage indicator data; Based on the receiving process of the webpage request information, obtaining the TCP connection time between the webpage request information and the webpage server; Based on the TCP connection time, obtaining the HTTP request time sent by the webpage request information; Based on the HTTP request time, obtaining the byte response time of the web page server responding to the first byte in the web page request information; Through the performance timing API, the TCP connection time, the HTTP request time and the byte response time are added together to obtain the first byte time in the stage indicator time; The DNS time includes: Obtaining the domain name resolution data of the DNS stage in the stage indicator data; By using the performance timing API, the difference time between the domain lookup end time node and the domain lookup start time node is calculated for the domain name resolution data to obtain the DNS time in the stage indicator time; The TCP time includes: According to the webpage request information, obtain the interface connection data of the TCP stage in the stage indicator data; wherein the interface connection data is the connection data between the webpage client and the webpage server; By using the performance timing API, the difference time between the connection establishment end time node and the connection establishment start time node is calculated for the interface connection data to obtain the TCP time in the stage indicator time; The time threshold of the stage indicator time is judged to obtain the web page opening result information; Feedback the web page opening result information to the user's operation page.

2. A method for detecting the loading speed of a web page according to claim 1, characterized in that: Based on the user's web page request information, the performance navigation time during web page loading is monitored to obtain stage indicator data, including: Obtaining timestamp data of a web page corresponding to the web page request information through a performance timing API, wherein the performance timing API is an interface in Web development and is used to provide time-related data of various events during web page loading and navigation; According to the time stage when the web page request information is executed, the timestamp data is divided into full time periods to obtain the stage indicator data; wherein the stage indicator data includes: page loading stage, first byte stage, DNS stage and TCP stage.

3. A method for detecting the loading speed of a web page according to claim 1, characterized in that: The stage indicator time is subjected to a time threshold judgment to obtain web page opening result information, specifically including: Integrate the page loading time, the first byte time, the DNS time and the TCP time in the stage indicator time to obtain a total stage indicator time; Performing time threshold judgment on the total stage indicator time; If the total stage indicator time is less than or equal to the first preset time threshold, the webpage opening speed is determined as fast opening information; If the total stage indicator time is greater than the first preset time threshold and less than or equal to the second preset time threshold, the webpage opening speed is determined as normal opening information; If the total stage indicator time is greater than the second preset time threshold and less than or equal to the third preset time threshold, the webpage opening speed is determined as slow opening information; If the total stage indicator time is greater than the third preset time threshold, the webpage opening speed is determined as very slow opening information; The webpage opening result information includes: the fast opening information, the normal opening information, the slow opening information and the very slow opening information.

4. A method for detecting the loading speed of a web page according to claim 1, characterized in that: Feeding back the webpage opening result information to the user's operation page specifically includes: Sending the web page opening result information to the web client of the user; and visually displaying it on the operation page; When the data tag of the web page opening result information is re-detection information, the timestamp data of the web page corresponding to the re-detection information is re-acquired through the performance timing API; and a loading detection of the web page opening speed is performed on the timestamp data.

5. A loading detection device for web page opening speed, characterized in that: The device comprises: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, so that the at least one processor can execute the loading detection method for web page opening speed according to any one of claims 1-4.

6. A non-volatile computer storage medium, characterized in that: The storage medium is a non-volatile computer-readable storage medium, and the non-volatile computer-readable storage medium stores at least one program, each of which includes instructions, and when the instructions are executed by the terminal, the terminal executes a loading detection method for web page opening speed according to any one of claims 1-4.

Images