4 sec in total
120 ms
1.7 sec
2.2 sec
Visit flux.fm now to see the best up-to-date Flux content and also check out these interesting facts you probably never knew about flux.fm
Welcome to the Internet home of father, DJ, runner, photographer, fitness instructor, and NASA Flight Controller Andrew Rechenberg.
Visit flux.fmWe analyzed Flux.fm page load time and found that the first response time was 120 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
flux.fm performance score
120 ms
69 ms
28 ms
29 ms
86 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 71% of them (56 requests) were addressed to the original Flux.fm, 5% (4 requests) were made to Pagead2.googlesyndication.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Flux.fm.
Page size can be reduced by 506.7 kB (74%)
687.5 kB
180.7 kB
In fact, the total size of Flux.fm main page is 687.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 387.5 kB which makes up the majority of the site volume.
Potential reduce by 48.6 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. This page needs HTML code to be minified as it can gain 7.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 48.6 kB or 78% of the original size.
Potential reduce by 135.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 135.1 kB or 57% of the original size.
Potential reduce by 323.1 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. Flux.fm needs all CSS files to be minified and compressed as it can save up to 323.1 kB or 83% of the original size.
Number of requests can be reduced by 30 (40%)
75
45
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flux. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
flux.fm
120 ms
css_ca63c3861bb0b08cde883f1bfafa5903.css
69 ms
grid16-960.css
28 ms
local.css
29 ms
js_4f487bcc2458d3d57a1ae81833b9eeef.js
86 ms
show_ads.js
4 ms
css
29 ms
badge1.png
576 ms
widgets.js
572 ms
ca-pub-2089164512377804.js
701 ms
zrt_lookup.html
550 ms
show_ads_impl.js
223 ms
secondary-menu-bg.png
209 ms
search-bg.png
355 ms
search-icon.png
355 ms
logo.png
356 ms
linkedin.png
526 ms
youtube.png
527 ms
facebook.png
530 ms
foursquare.png
596 ms
g-plus-icon-32x32.png
597 ms
soundcloud.png
596 ms
flickr.png
604 ms
instagram32.png
605 ms
twitter.png
604 ms
primary-menu-bg.png
654 ms
flux_nopics_please.jpg
654 ms
dream_team_pad01.jpg
672 ms
4877485053_876e18d6d9_b.jpg
673 ms
nye_flux_gear.jpg
677 ms
cincinnati01.jpg
672 ms
flux_vab_crop_01.jpg
684 ms
sts130_sequence.jpg
682 ms
IMG_8113-1600.jpg
695 ms
20130604-third_flight.jpg
742 ms
image_9.jpg
683 ms
image_10.jpg
734 ms
list-level-1.png
737 ms
flux_nasaintern_stpatricks_dj.jpg
737 ms
b20-sunset01-insta.jpg
737 ms
nasa_interns_volunteer_family_space_day.jpg
791 ms
rover_mars_yard_nasaintern.jpg
1026 ms
image_6.jpg
1026 ms
image_7.jpg
1028 ms
image_8.jpg
1027 ms
image_5.jpg
978 ms
image_3.jpg
979 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
463 ms
image_2.jpg
974 ms
KyZqSWWKmHQ
480 ms
ads
260 ms
image_0.jpg
689 ms
image_1.jpg
687 ms
image.jpg
688 ms
Orionflightestprofile.jpg
671 ms
osd.js
234 ms
ga.js
217 ms
Orionsketch1.jpg
528 ms
cropped-Orion_Exploration_Flight_Test_1.jpg
528 ms
sts133-20101101-1.jpg
526 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
181 ms
sts133-20101102-1-rss-bighouse.jpg
461 ms
sts133-20110223-1.jpg
462 ms
sts133-20110224-1.jpg
456 ms
pager-next.png
455 ms
pager-last.png
454 ms
feed.png
472 ms
__utm.gif
28 ms
menu-leaf.png
425 ms
www-embed-player-vfl-z2BtK.css
44 ms
www-embed-player.js
88 ms
base.js
126 ms
menu-expanded.png
408 ms
syndication
333 ms
284054138873057280
502 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
188 ms
ad_status.js
192 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
153 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
154 ms
flux.fm SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flux.fm 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 Flux.fm 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.
flux.fm
Open Graph description is not detected on the main page of Flux. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: