3.1 sec in total
320 ms
2.2 sec
643 ms
Welcome to frequency.fm homepage info - get ready to check Frequency best content right away, or after learning these important things about frequency.fm
Listen to episodes and learn more about Frequency Podcast. Join us at www.frequency.fm for insightful artist interviews, objective and honest music and book reviews, and thoughtful commentary on art a...
Visit frequency.fmWe analyzed Frequency.fm page load time and found that the first response time was 320 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
frequency.fm performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.6 s
17/100
25%
Value14.8 s
1/100
10%
Value18,730 ms
0/100
30%
Value0.003
100/100
15%
Value25.4 s
0/100
10%
320 ms
394 ms
430 ms
237 ms
248 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Frequency.fm, 51% (29 requests) were made to Shows.acast.com and 14% (8 requests) were made to Res.cloudinary.com. The less responsive or slowest element that took the longest time to load (585 ms) relates to the external source Embed.acast.com.
Page size can be reduced by 74.8 kB (22%)
338.1 kB
263.3 kB
In fact, the total size of Frequency.fm main page is 338.1 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. Images take 220.0 kB which makes up the majority of the site volume.
Potential reduce by 74.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 74.7 kB or 78% of the original size.
Potential reduce by 0 B
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. Frequency images are well optimized though.
Potential reduce by 50 B
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.
Potential reduce by 26 B
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. Frequency.fm has all CSS files already compressed.
Number of requests can be reduced by 35 (70%)
50
15
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frequency. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
frequency.fm
320 ms
frequencyfm
394 ms
gtm.js
430 ms
rollbar.min.js
237 ms
css
248 ms
js
528 ms
e6324cbc2374aa7fa199dfd738f93c81af867dc7_CSS.88d4f806.chunk.css
72 ms
9f7a6c2cdf67e8360e7ee54bcf19d78f5c7a1cd6_CSS.77314a77.chunk.css
99 ms
styles.78f7496e.chunk.css
149 ms
_app.af6fbe1c.chunk.css
117 ms
0d32a703705df9e72871ede44f803b4aa3053335_CSS.86e1b770.chunk.css
117 ms
a8119d66d6eff93d2729a9f14a44cc0049fbbbf3_CSS.e6ded488.chunk.css
164 ms
polyfills-7c72805108ebcf695117.js
118 ms
main-0f9551c35eb04e7acec3.js
116 ms
webpack-d7b2fb72fb7257504a38.js
117 ms
framework.4cb66147a9c8c0fd8872.js
122 ms
0fa1c81b3ff4ddba4590f515a2352830f3dfe464.534790427c5cdb14e8ac.js
122 ms
e6324cbc2374aa7fa199dfd738f93c81af867dc7.33ba7666936f98415046.js
194 ms
cde400cf1c1cfcb88730acb568de0bcbed241b8a.10f7124b154e7b943255.js
163 ms
e6324cbc2374aa7fa199dfd738f93c81af867dc7_CSS.ff5578978733a40a67a3.js
163 ms
9f7a6c2cdf67e8360e7ee54bcf19d78f5c7a1cd6.26f44d063c02f28162a8.js
163 ms
9f7a6c2cdf67e8360e7ee54bcf19d78f5c7a1cd6_CSS.19830e50427f38e47434.js
372 ms
6a05df13548c4fe5e0dcb448db988412f2a07bbe.ffc777c63ce53961d57f.js
372 ms
f8cc6a1e000369201bd6678c60b37fa1a7d5ba50.d7e869f71d3a1b55251c.js
372 ms
d46bf48ec35dfa6718793a7bcc63816ca861c799.b46997177d0bd6841af1.js
372 ms
styles.bf24e8d3f8067bb25229.js
355 ms
_app-8cedb039a28cf5159624.js
456 ms
0d32a703705df9e72871ede44f803b4aa3053335.b198b983eb1865729709.js
454 ms
0d32a703705df9e72871ede44f803b4aa3053335_CSS.d6f2610c02ca1f2f8023.js
453 ms
a8119d66d6eff93d2729a9f14a44cc0049fbbbf3.6c154af84924721000e8.js
453 ms
a8119d66d6eff93d2729a9f14a44cc0049fbbbf3_CSS.955cd01b185e91c5e5fc.js
453 ms
%5BshowId%5D-37c6fc83b9a6f61acd6a.js
453 ms
_buildManifest.js
455 ms
_ssgManifest.js
455 ms
1609356473257-326b16c9a2348087e96b4f9aa47cd529.jpeg
355 ms
1565373611706-afcfc2a6f9bf43523d9b9925980db1d7.jpeg
311 ms
1557876451332-4cc8c964cabcbad374de84808cf187ab.jpeg
378 ms
1554759184254-1b2756298e95ae99f0d3d15d53343688.jpeg
349 ms
1547835357019-3144ffb7ae001d8a53a71f8cd1844047.jpeg
427 ms
1546315923291-350ac0ae906e92583efdf5c216ca8905.jpeg
349 ms
1545943267614-df5aa1fa1d20bf1648ab50834ebc8c12.jpeg
358 ms
1543442223236-62a63b1cfc093cc5984bde755c464715.jpeg
463 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
260 ms
KFOmCnqEu92Fr1Mu4mxM.woff
268 ms
analytics.js
217 ms
collect
32 ms
collect
39 ms
collect
35 ms
585 ms
39 ms
54 ms
48 ms
collect
36 ms
fonts.css
26 ms
278.ecd2fb66.js
23 ms
main.b4161305.js
23 ms
gtm.js
19 ms
frequency.fm 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
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
frequency.fm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
frequency.fm SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frequency.fm can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Frequency.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.
frequency.fm
Open Graph data is detected on the main page of Frequency. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: