You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
The biggest improvement this year to web performance has been the introduction of WebAssembly. Now available in Firefox and Chrome, and coming soon in Edge and WebKit, WebAssembly enables the execution of code at a low assembly-like level in the browser. Mozilla has worked closely with the games industry for several years to reach this stage: including milestones like the release of games built wi
Over the last few years, Mozilla has worked closely with other browsers and the industry to advance the state of games on the Web. Together, we have enabled developers to deploy native code on the web, first via asm.js, and then with its successor WebAssembly. Now available in Firefox and Chrome, and also soon in Edge and WebKit, WebAssembly enables near-native performance of code in the browser,
User-centric performance metrics Stay organized with collections Save and categorize content based on your preferences. We've all heard how important performance is. But when we talk about performance, and about making websites "fast", what specifically do we mean? The truth is that performance is relative: A site might be fast for one user (on a fast network with a powerful device) but slow for a
$200K 1 10th birthday 4 abusive ads 1 abusive notifications 2 accessibility 3 ad blockers 1 ad blocking 2 advanced capabilities 1 android 2 anti abuse 1 anti-deception 1 background periodic sync 1 badging 1 benchmarks 1 beta 83 better ads standards 1 billing 1 birthday 4 blink 2 browser 2 browser interoperability 1 bundles 1 capabilities 6 capable web 1 cds 1 cds18 2 cds2018 1 chrome 35 chrome 81
layout: true class: center, middle background-image: url(media/links.jpg) --- # `<link>` .center[Yoav Weiss | @yoavweiss] .right[![](media/Akamai-Logo-RGB.png)] ??? Hi, I'm Yoav Weiss. I work for Akamai on making both browsers and CDNs awesomer, and I'm here today to talk to you about the `<link>` element, browser's resource loading, the connection between the two and how *you* can help browser
Today we’ll dive into insights from Chrome’s networking stack to provide clarity on how web loading primitives (like <link rel=“preload”> & <link rel=“prefetch”>) work behind the scenes so you can be more effective with them. As covered well in other articles, preload is a declarative fetch, allowing you to force the browser to make a request for a resource without blocking the document’s onload e
Apply instant loading with the PRPL pattern Stay organized with collections Save and categorize content based on your preferences. PRPL is an acronym that describes a pattern used to make web pages load and become interactive, faster: Preload the late-discovered resources. Render the initial route as soon as possible. Pre-cache remaining assets. Lazy load other routes and non-critical assets. In t
Update: The Cost Of JavaScript In 2019 is now available to read. As web developers, we know how easy it is to end up with web page bloat. But loading a webpage is much more than shipping bytes down the wire. Once the browser has downloaded our page’s scripts it then has to parse, interpret & run them. In this post, we’ll dive into this phase for JavaScript, why it might be slowing down your app’s
Chrome 62 PaymentDetailsModifier is now available In a payment request, there are cases where you want to provide a discount or an extra charge depending on the payment method a customer chooses. PaymentDetailsModifier is the feature you can use to achieve this. Add modifiers property to the second argument of PaymentRequest constructor along with an array of PaymentDetailsModifier object which is
Please leave your sense of logic at the door, thanks! Improving interoperability January 30th, 2017 by Philip Jägenstedt in WHATWG The goal of the WHATWG’s Living Standards is to achieve interoperable implementations. With an ever-evolving web platform, we want changes to our standards to reach all implementations quickly and reliably, but from time to time there have been mishaps: Two table-relat
When a browser receives the HTML response for a page from the server, there are a lot of steps to be taken before pixels are drawn on the screen. This sequence the browsers needs to run through for the initial paint of the page is called the "Critical Rendering Path". Knowledge of the CRP is incredibly useful for understanding how a site's performance can be improved. There are 6 stages to the CRP
Happy new year! As promised I thought I’d share a few of the Web animation things I’m looking forward to in 2017. I’m terrible at predicting the future (I used to be a believer in BeOS and VRML) so this is mostly based on what is already in motion. Specs: CSS transitions – this should move to CR status soon. Part of that involves splitting off a separate Timing Functions spec. That separate spec w
Steve works at SpeedCurve on the interplay between performance and design. He previously served as Google's Head Performance Engineer, Chief Performance Yahoo!, and Chief Performance Officer at Fastly. Steve has pioneered much of the work in the world of web performance. He is the author of High Performance Web Sites and Even Faster Web Sites. He is the creator of many performance tools and servic
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く