Abstract: Generally described, one or more aspects of the present application correspond to a content rendering system. A content management service hosts content on behalf of the content provider. The content management service includes one or more rendering engines that receive content from the one or more content providers that are registered with the content management service. Each content rendering engine can be configured to receive a content resource and generate at least one piece of processed content that can be rendered on a user device.

Abstract: This disclosure describes techniques for utilizing sensor data to automatically determine the results of events within a system. Upon receiving sensor data indicative of an event, the techniques may analyze the sensor data to determine a result of the event, such as that a particular user associated with a user identifier selected a particular item associated with an item identifier. The techniques described herein may determine when sensor data is to be stored for a default amount of time, and when sensor data is to be stored for a greater amount of time. By retaining data in an intelligent manner, the system is able to function accurately without unduly taxing storage constraints.

Abstract: Generally described, one or more aspects of the present application correspond to a content rendering system. A content management service hosts content on behalf of the content provider. The content management service includes one or more rendering engines that receive content from the one or more content providers that are registered with the content management service. Each content rendering engine can be configured to receive a content resource and generate at least one piece of processed content that can be rendered on a user device.

Abstract: Features are disclosed for selecting preferred content request modes on a client computing device when initiating content requests. The request modes may correspond to direct requests (e.g., requests made from a client device directly to a content sever hosting requested content) or to indirect requests (e.g., requests made from the client device to the content server via an intermediary system). The preferred request modes made be based on a statistical analysis of performance data (e.g., prior content load times) observed or recorded by the client computing device in connection with prior content requests. Randomly selected request modes may be used to provide additional data for performance analysis.

Abstract: Techniques and solutions are described for content synchronization across devices. A web page currently being viewed at a first device associated with a user profile of a user can be identified. Browsing information for the page (such as URL, scrolling location, and a DOM element) may be stored in the profile. The DOM element may be associated with page content displayed during a browsing session in a viewport while the web page is at the current scrolling location. The browsing information may be updated dynamically, upon detecting a change in the current scrolling location of the page at the first device. A request for displaying the web page at a second device associated with the user profile may be received. The browsing information for the web page may be provided to the second device, so that the web page with the current scrolling location is displayed at the second device.

Abstract: Network accessible content, including but not limited to web pages, can be analyzed to identify characteristics of the content. Historical content requests associated with users and/or other user-specific information can be analyzed to identify user interests. Content can then be provided or recommended to users based on content characteristics and user interests. The content that is provided or recommended may be trending content that has at least a threshold level of popularity, became popular recently, and/or is associated with a threshold level of social network activity.

Abstract: A system is disclosed that enables a user to access a first piece of content on a first computing device while accessing a related, but different piece of content on a second computing device. In some cases, the different piece of content is a portion of the first piece of content. In some embodiments, the system can automatically identify complementary content and can automatically cause the second computing device to access the complementary content without the user interacting with the second computing device. In some cases, the system may reformat the complementary content for presentation to the user based on characteristics of the second computing device.

Abstract: Features are disclosed for generating request decision models for use by client computing devices to determine request paths or modes for content requests. The request modes may correspond to direct requests (e.g., requests made from a client device directly to a content server hosting requested content) or to indirect requests (e.g., requests made from the client device to the content server via an intermediary system). The request decision models may be trained by a machine learning algorithm using performance data (e.g., prior content load times), contextual information (e.g., state information associated with devices at times content requests are executed), and the like.

Abstract: Features are disclosed for determining preferred content request modes for client computing devices when initiating content requests. The request modes may correspond to direct requests (e.g., requests made from a client device directly to a content sever hosting requested content) or to indirect requests (e.g., requests made from the client device to the content server via an intermediary system). The preferred request modes made be based on a statistical analysis of performance data (e.g., prior content load times) obtained from one or more client computing devices for a given content item, group of content items (e.g., domain), and the like.

Abstract: Features are disclosed for generating bundles of content items and proactively providing the bundles to client devices. The bundles may be provided to client devices in response to requests for the content page that references the content items in the bundle, or in response to a request for a content page hosted by the same domain as the content items in the bundle. A browser module executing on the client device can extract the referenced content items in the bundle and cache them in a local content cache at the client device prior to the client device receiving and processing a requested content page. As a result, the browser module may have access to cached versions of referenced content items when processing the requested content page even if the referenced content items were not present when the requested content page was requested.

Abstract: A system and process are disclosed for providing users with page previews during page loading events, such that the delay experienced before the display of page content is reduced. The previews may include screenshots of the pages or of portions thereof, and may be generated periodically and cached by the system for delivery to user devices. The process of generating and delivering the previews via the Internet or some other network may be implemented partly or wholly within an intermediary system that sits logically between the user devices and content servers. The process may be used with existing browsers without the need for any browser modifications, or may be used with a “preview-aware” browser that includes special program code for providing page previews.

Abstract: A user device that presents a static non-interactive graphical representation of a content page received from an intermediary system may emulate controls or interactive elements included in the content page based on control metadata received from the intermediary system. The emulated controls enable the user device to restore the interactivity that is lost by generating the graphical representation of the content page. Further, the emulated controls may be included as part of an overlay layer positioned above the graphical representation of the content page. Information or control metadata for each control included in the content page may be provided to the user device with the graphical representation of the content page. The user device may use the control metadata to identify types of controls to emulate and where to position the emulated control with respect to the graphical representation of the content page.

Abstract: A system and process are disclosed for providing users with page previews during page loading events, such that the delay experienced before the display of page content is reduced. The previews may include screenshots of the pages or of portions thereof, and may be generated periodically and cached by the system for delivery to user devices. The process of generating and delivering the previews via the Internet or some other network may be implemented partly or wholly within an intermediary system that sits logically between the user devices and content servers. The process may be used with existing browsers without the need for any browser modifications, or may be used with a “preview-aware” browser that includes special program code for providing page previews.

Abstract: Features are disclosed for generating bundles of content items and proactively providing the bundles to client devices. The bundles may be provided to client devices in response to requests for the content page that references the content items in the bundle, or in response to a request for a content page hosted by the same domain as the content items in the bundle. A browser module executing on the client device can extract the referenced content items in the bundle and cache them in a local content cache at the client device prior to the client device receiving and processing a requested content page. As a result, the browser module may have access to cached versions of referenced content items when processing the requested content page even if the referenced content items were not present when the requested content page was requested.

Abstract: Techniques and solutions are described for content synchronization across devices. A web page currently being viewed at a first device associated with a user profile of a user can be identified. Browsing information for the page (such as URL, scrolling location, and a DOM element) may be stored in the profile. The DOM element may be associated with page content displayed during a browsing session in a viewport while the web page is at the current scrolling location. The browsing information may be updated dynamically, upon detecting a change in the current scrolling location of the page at the first device. A request for displaying the web page at a second device associated with the user profile may be received. The browsing information for the web page may be provided to the second device, so that the web page with the current scrolling location is displayed at the second device.

Abstract: Features are disclosed for determining which content item or items are likely to be requested by a particular user or device, or by a group of users or devices. The determined content items may be obtained independently of a request from the users or devices, and substantially current versions of the content items may be maintained at a server system, such as an intermediary system. Visual representations of the content items may be generated to reduce processing requirements at a user device. When the content items are determined to be likely to be requested by a particular user, a predicted time may also be determined, and the visual representations may be generated such that they are available at the predicted time.

Abstract: Features are disclosed for automatically generating content requests and recording metrics and other information about execution of the requests. The requests can be background requests, executed by user computing devices during idle periods and without any user initiation. The background requests may be browser requests for content pages. Metrics and other information about execution of the requests may be recorded during execution of the background requests and reported to a performance analysis system. Instructions to execute background requests can be generated so as to develop a data set, such as a data set for analyzing request execution performance.

Abstract: Features are disclosed for enabling users to efficiently store and share browsing sessions or portions thereof with other users or the general public. Browsing session requests and other activities may be sent to an intermediary system, which can retrieve requested content and store a representation of the requested content or data regarding the requested content. The stored data may be organized as a saved browsing session such that users may access the shared browsing session at a subsequent time and view the browsing session substantially in its entirety. Users may search for shared browsing sessions and access data regarding the requests made during a browsing session. In addition, data regarding client devices used during shared browsing sessions may be tracked and associated with the shared browsing sessions such that subsequent users can search for shared browsing sessions based partly on such device characteristics.

Abstract: Features are disclosed for determining which content item or items are likely to be requested by a particular user or device, or by a group of users or devices. The determined content items may be obtained independently of a request from the users or devices, and substantially current versions of the content items may be maintained at a server system, such as an intermediary system. Visual representations of the content items may be generated to reduce processing requirements at a user device. When the content items are determined to be likely to be requested by a particular user, a predicted time may also be determined, and the visual representations may be generated such that they are available at the predicted time.

Abstract: Features are disclosed for enabling users to select portions of content pages, including predefined portions and arbitrarily defined portions, for which to receive update notifications or which to share with other users. Notifications regarding updates to the selected portions may be displayed to the user in a notification overlay. The notification overlay may be at least partially transparent so as to allow users to see content on a content page displayed beneath the overlay. The notification overlay may be displayed persistently as the user navigates or otherwise transitions from page to page. Users may also access shared, predefined, and context-sensitive notification overlays created by other users, entities, or automated processes.