2.9 sec in total
16 ms
2.2 sec
666 ms
Visit fastly.net now to see the best up-to-date Fastly content for United States and also check out these interesting facts you probably never knew about fastly.net
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.netWe analyzed Fastly.net page load time and found that the first response time was 16 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fastly.net performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value8.0 s
2/100
25%
Value8.7 s
16/100
10%
Value4,810 ms
0/100
30%
Value0.097
90/100
15%
Value23.1 s
1/100
10%
16 ms
314 ms
70 ms
29 ms
31 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fastly.net, 43% (37 requests) were made to Fastly.com and 10% (9 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (947 ms) relates to the external source S.swiftypecdn.com.
Page size can be reduced by 1.0 MB (71%)
1.4 MB
419.5 kB
In fact, the total size of Fastly.net main page is 1.4 MB. 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. Javascripts take 917.5 kB which makes up the majority of the site volume.
Potential reduce by 26.8 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 26.8 kB or 73% of the original size.
Potential reduce by 24.4 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 24.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 653.7 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 653.7 kB or 71% of the original size.
Potential reduce by 324.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Fastly.net needs all CSS files to be minified and compressed as it can save up to 324.0 kB or 87% of the original size.
Number of requests can be reduced by 38 (46%)
82
44
The browser has sent 82 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 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
fastly.net
16 ms
www.fastly.com
314 ms
css_RZkHofAO3LAPMF6pEtb7v-x2YFzKgx0gRcRCvPnKd-I.css
70 ms
css_mVbAwHFC4teH8QnlrR4HjS3odTpW_y7a4J_ULaUdWmE.css
29 ms
css_L8nyMvOBvYCVaS_rEbghvWyjzIq7ULYrWWcUYtuizds.css
31 ms
css_8_2e-c_roEo56oVE-HbOIT0i0hgdooZXrOoEAxEF1i0.css
29 ms
css_nfGenlHMoeln4Ok2hlGh8u-vfwxI5aLXjt-hYHC9ND4.css
31 ms
css_MiDD-eCSsZyAZI73ap-hvjtVPk7Ye4Fawojn71mpqbI.css
46 ms
css_T1yTq-8v2fvoN6POI-qGzAPsdrSMlLd51pFU3LgoX7c.css
34 ms
js_MpKfe1sTh5JIVGCZ17DsAuT1rqAC38MLLlkjqjQ1X_k.js
64 ms
js_H7q2xORKmR9AN8Qx5spKEIBp7R_wG2apAswJoCUZY7I.js
35 ms
js_vU-iAAhd3rDtYaF56IWCYcsuNq4I0_G9ynfD_6ofNww.js
42 ms
js_eW1SQe8LvsnBcNbvh4Oz9IJqn1WmLBO3KHeFTnyhT2E.js
87 ms
js_IZFR-RcF8rq7Q1Q8RGUvmbL3y5eC0BFFmOYuRG_bgGY.js
95 ms
js_ZxMBDmSTsUaDAx9qpXo--jJXk5MKzIwsMVXSi9kJXXo.js
102 ms
fastly.js
352 ms
analytics.js
290 ms
embed.js
947 ms
elqCfg.min.js
300 ms
120
362 ms
logo.png
91 ms
search.svg
89 ms
FAS001_WHY_FASTLY_21-PRHQ_1080P_MASTER_7_0.jpg
93 ms
icon_cta-arrow.svg
92 ms
homepage_icons_web_mobile.png
91 ms
homepage_icons_streaming.png
110 ms
homepage_icons_cloud_security.png
109 ms
homepage_icons_technology_platform.png
110 ms
homepage_icons_api.png
110 ms
logo_twitter.png
141 ms
logo_vogue.png
140 ms
logo_kayak.png
141 ms
logo_new-relic.png
141 ms
logo_vimeo.png
140 ms
bg_tachometer.svg
230 ms
bg_footer.gif
170 ms
sprite_social.svg
145 ms
151803793
228 ms
151815221
225 ms
151854858
222 ms
151806260
222 ms
151855883
219 ms
Raleway-SemiBold.ttf
140 ms
Raleway-ExtraBold.ttf
198 ms
Raleway-Bold.ttf
234 ms
Raleway-Regular.ttf
194 ms
Raleway-Light.ttf
192 ms
collect
173 ms
player.js
268 ms
player.css
166 ms
ga.js
163 ms
vuid.min.js
260 ms
collect
228 ms
svrGP.aspx
117 ms
0
266 ms
__utm.gif
138 ms
__utm.gif
196 ms
__utm.gif
220 ms
__utm.gif
224 ms
__utm.gif
224 ms
proxy.html
189 ms
553506957.webp
208 ms
ga-audiences
163 ms
484e6ee90c0ba353187e5768a89c0eb8
217 ms
553507470.webp
88 ms
551653986.webp
94 ms
553510607.webp
101 ms
swiftype_onpage-02d2e72de5fcf9d8823ddf010d36df29.js
85 ms
swiftype-179f8909e063840665bced090aa7b3b1.css
32 ms
nr-768.min.js
172 ms
151815221
46 ms
151854858
51 ms
151806260
44 ms
perfmapconfig.js
33 ms
cc.js
128 ms
551653986.webp
52 ms
__utm.gif
80 ms
553506957.webp
47 ms
__utm.gif
50 ms
popname.js
55 ms
popname.js
134 ms
popname.js
248 ms
553507470.webp
22 ms
__utm.gif
21 ms
cc
253 ms
c308c1706e
125 ms
fastly.net 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
Heading elements are not in a sequentially-descending order
fastly.net 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
fastly.net 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.net 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.net 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.net
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: