2.4 sec in total
368 ms
1.1 sec
903 ms
Visit fastly.us now to see the best up-to-date Fastly content and also check out these interesting facts you probably never knew about fastly.us
Fastly's edge cloud platform delivers faster, safer, and more scalable sites and apps to customers. Elevate your edge CDN, video delivery, security, and more.
Visit fastly.usWe analyzed Fastly.us page load time and found that the first response time was 368 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
fastly.us performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value2.5 s
90/100
25%
Value31.8 s
0/100
10%
Value80,270 ms
0/100
30%
Value0.167
71/100
15%
Value106.4 s
0/100
10%
368 ms
500 ms
648 ms
547 ms
285 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fastly.us, 4% (2 requests) were made to Munchkin.marketo.net and 2% (1 request) were made to Js.driftt.com. The less responsive or slowest element that took the longest time to load (648 ms) relates to the external source Js.driftt.com.
Page size can be reduced by 483.0 kB (71%)
677.0 kB
194.0 kB
In fact, the total size of Fastly.us main page is 677.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 539.6 kB which makes up the majority of the site volume.
Potential reduce by 461.9 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 461.9 kB or 86% of the original size.
Potential reduce by 14.0 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Fastly needs image optimization as it can save up to 14.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 7.1 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 7.1 kB or 58% of the original size.
Number of requests can be reduced by 9 (20%)
44
35
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fastly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
www.fastly.com
368 ms
munchkin.js
500 ms
x2ugb2nh7dxy.js
648 ms
gtm.js
547 ms
polyfill-d6ee7a207df90779369c.js
285 ms
app-b1e3e56480c8b71c270e.js
332 ms
dc6a8720040df98778fe970bf6c000a41750d3ae-1b7c22439fb7ad9f9dbf.js
308 ms
2c56e427-dfbd61e9fd14a69ac708.js
363 ms
framework-f259db23892fd05e6c38.js
309 ms
webpack-runtime-c793247311c46ec46382.js
310 ms
nav-carat-icon.svg
448 ms
MF1_Hamilton44.1.png
333 ms
Button-Arrow.svg
441 ms
hero-laptop_1.png
334 ms
yelp_logo__1___1_.svg
445 ms
anheuser-busch-logo__1___1_.svg
458 ms
Epic_Games_logo_1__1_.svg
455 ms
NewYorkTimes_1__1_.svg
461 ms
Boots_UK__logo__1__1_.svg
464 ms
Stripe_Logo__revised_2016_1__1___1_.svg
522 ms
A_E_Network_logo_2__1_.svg
518 ms
reddit-logo-lg__1_.svg
520 ms
Gartner-Peer-Insights-Customers-Choice-badge-color-2022__2___1_.svg
523 ms
Forrester_New_Wave_Graphic_Q4_2021.png
461 ms
Gartner-Peer-Insights-Customers-Choice2020__1_.svg
531 ms
Gartner-Peer-Insights-Customers-Choice2021__1_.svg
525 ms
terminal-line-lg-desktop.svg
536 ms
analyst-logo-IDC__1___1_.svg
538 ms
forrester_logo-black-small.svg
493 ms
gartner__1___1_.svg
538 ms
Image__1_.svg
529 ms
Edgemesh-svg-logo.svg
526 ms
LaunchDarkly_RGB_Primary_Lock-up_Black__1_.svg
536 ms
slider-arrow.svg
552 ms
graphic-deliver__1_.svg
574 ms
The_Guardian_2x.png
532 ms
gannett.png
533 ms
graphic-secure__1_.svg
594 ms
Axon__1___1_.svg
605 ms
remitly-inc-vector-logo__1_.svg
396 ms
betterment__1___1_.svg
370 ms
munchkin.js
33 ms
Visual__1_.svg
363 ms
1stdibs_2x.png
335 ms
network-worldMap.svg
369 ms
visitWebPage
336 ms
fastly.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
fastly.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fastly.us SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fastly.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fastly.us main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
fastly.us
Open Graph data is detected on the main page of Fastly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: