Tools & Wizards About Us
flux.fm screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

flux.fm

The Internet home of Andy Rechenberg - flux.fm

Page Load Speed

733 ms in total

First Response

31 ms

Resources Loaded

448 ms

Page Rendered

254 ms

flux.fm screenshot

About Website

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.fm

Key Findings

We analyzed Flux.fm page load time and found that the first response time was 31 ms and then it took 702 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

flux.fm performance score

0

Network Requests Diagram

flux.fm

31 ms

flux.fm

81 ms

style.min.css

30 ms

clients-bar.css

46 ms

woocommerce-layout.css

47 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 96% of them (67 requests) were addressed to the original Flux.fm, 1% (1 request) were made to Stats.wp.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (174 ms) belongs to the original domain Flux.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.5 kB (76%)

Content Size

101.0 kB

After Optimization

24.5 kB

  • HTML
  • JavaScript

In fact, the total size of Flux.fm main page is 101.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 96.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 76.5 kB

  • Original 96.2 kB
  • After minification 94.8 kB
  • After compression 19.7 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 76.5 kB or 80% of the original size.

JavaScript Optimization

-1%

Potential reduce by 27 B

  • Original 4.9 kB
  • After minification 4.9 kB
  • After compression 4.8 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 59 (88%)

Requests Now

67

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 67 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 49 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

flux.fm

flux.fm

31 ms

flux.fm

flux.fm

81 ms

style.min.css

style.min.css

30 ms

clients-bar.css

clients-bar.css

46 ms

woocommerce-layout.css

woocommerce-layout.css

47 ms

woocommerce.css

woocommerce.css

49 ms

bootstrap.min.css

bootstrap.min.css

52 ms

font-sizes.min.css

font-sizes.min.css

51 ms

style.min.css

style.min.css

65 ms

woocommerce.min.css

woocommerce.min.css

63 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

49 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

50 ms

wp-polyfill.min.js

wp-polyfill.min.js

73 ms

hooks.min.js

hooks.min.js

52 ms

w.js

w.js

29 ms

jquery.min.js

jquery.min.js

88 ms

jquery-migrate.min.js

jquery-migrate.min.js

71 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

72 ms

add-to-cart.min.js

add-to-cart.min.js

87 ms

js.cookie.min.js

js.cookie.min.js

88 ms

woocommerce.min.js

woocommerce.min.js

87 ms

js

js

130 ms

wc-blocks.css

wc-blocks.css

117 ms

all.min.css

all.min.css

121 ms

v4-shims.min.css

v4-shims.min.css

118 ms

sourcebuster.min.js

sourcebuster.min.js

151 ms

order-attribution.min.js

order-attribution.min.js

151 ms

react.min.js

react.min.js

154 ms

deprecated.min.js

deprecated.min.js

153 ms

dom.min.js

dom.min.js

155 ms

react-dom.min.js

react-dom.min.js

159 ms

escape-html.min.js

escape-html.min.js

165 ms

element.min.js

element.min.js

165 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

165 ms

i18n.min.js

i18n.min.js

165 ms

keycodes.min.js

keycodes.min.js

158 ms

priority-queue.min.js

priority-queue.min.js

171 ms

compose.min.js

compose.min.js

174 ms

private-apis.min.js

private-apis.min.js

171 ms

redux-routine.min.js

redux-routine.min.js

171 ms

data.min.js

data.min.js

156 ms

lodash.min.js

lodash.min.js

145 ms

wc-blocks-registry.js

wc-blocks-registry.js

154 ms

url.min.js

url.min.js

151 ms

api-fetch.min.js

api-fetch.min.js

148 ms

wc-settings.js

wc-settings.js

146 ms

data-controls.min.js

data-controls.min.js

145 ms

html-entities.min.js

html-entities.min.js

145 ms

notices.min.js

notices.min.js

149 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

141 ms

wc-blocks-data.js

wc-blocks-data.js

134 ms

dom-ready.min.js

dom-ready.min.js

131 ms

g.gif

g.gif

83 ms

a11y.min.js

a11y.min.js

117 ms

primitives.min.js

primitives.min.js

119 ms

warning.min.js

warning.min.js

127 ms

blocks-components.js

blocks-components.js

142 ms

blocks-checkout.js

blocks-checkout.js

114 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

97 ms

comment-reply.min.js

comment-reply.min.js

97 ms

bootstrap.min.js

bootstrap.min.js

91 ms

core.min.js

core.min.js

97 ms

script.min.js

script.min.js

74 ms

921F06DF-A6DA-406B-A00A-0D466DC05B5D_1_105_c.jpeg

921F06DF-A6DA-406B-A00A-0D466DC05B5D_1_105_c.jpeg

129 ms

vab_and_moon-1980-360x240.jpeg

vab_and_moon-1980-360x240.jpeg

126 ms

201011-sts133-flux_vab--e1524439092715.jpg

201011-sts133-flux_vab--e1524439092715.jpg

126 ms

rocketpark-360x240.jpg

rocketpark-360x240.jpg

125 ms

Screen-Shot-2019-03-10-at-8.35.04-PM-360x240.png

Screen-Shot-2019-03-10-at-8.35.04-PM-360x240.png

118 ms

fa-brands-400.woff

fa-brands-400.woff

28 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

14 ms

SEO Factors

flux.fm SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

flux.fm

Open Graph data is detected on the main page of Flux. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: