4.8 sec in total
167 ms
3.9 sec
732 ms
Visit recordiplayer.com now to see the best up-to-date Record IPlayer content and also check out these interesting facts you probably never knew about recordiplayer.com
How to Record iPlayer, Channel 4 or Hulu programmes for personal use
Visit recordiplayer.comWe analyzed Recordiplayer.com page load time and found that the first response time was 167 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
recordiplayer.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value6.6 s
8/100
25%
Value8.3 s
19/100
10%
Value300 ms
78/100
30%
Value0.086
93/100
15%
Value8.3 s
40/100
10%
167 ms
552 ms
94 ms
161 ms
186 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 51% of them (26 requests) were addressed to the original Recordiplayer.com, 12% (6 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (552 ms) belongs to the original domain Recordiplayer.com.
Page size can be reduced by 87.3 kB (33%)
262.5 kB
175.2 kB
In fact, the total size of Recordiplayer.com main page is 262.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. 55% of websites need less resources to load. Javascripts take 152.7 kB which makes up the majority of the site volume.
Potential reduce by 40.3 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 40.3 kB or 73% 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. Record IPlayer images are well optimized though.
Potential reduce by 26.9 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 26.9 kB or 18% of the original size.
Potential reduce by 20.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. Recordiplayer.com needs all CSS files to be minified and compressed as it can save up to 20.1 kB or 37% of the original size.
Number of requests can be reduced by 27 (69%)
39
12
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Record IPlayer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
recordiplayer.com
167 ms
www.recordiplayer.com
552 ms
wp-emoji-release.min.js
94 ms
style.min.css
161 ms
theme.min.css
186 ms
polls-css.css
185 ms
css
84 ms
genericons.css
252 ms
style.css
260 ms
blocks.css
197 ms
jwplayer.js
287 ms
jquery.js
364 ms
jquery-migrate.min.js
249 ms
swfobject.js
267 ms
index.php
132 ms
external-tracking.min.js
311 ms
yahoo-dom-event.js
20 ms
swfobject.js
132 ms
widgets.js
14 ms
polls-js.js
289 ms
skip-link-focus-fix.js
297 ms
functions.js
305 ms
wp-embed.min.js
332 ms
swfobject.js
249 ms
index.php
418 ms
ga.js
81 ms
loading.gif
115 ms
Self-Portrait-150x150.gif
115 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCTyccP.ttf
84 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZT1eTyccP.ttf
116 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9U6Vc.ttf
128 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6Vc.ttf
127 ms
Genericons.svg
142 ms
8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=
38 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBNLg_cGrq4.ttf
155 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBOshPcGrq4.ttf
155 ms
like.php
256 ms
like.php
353 ms
like.php
345 ms
like.php
362 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
37 ms
__utm.gif
35 ms
Self-Portrait-150x150.gif
76 ms
settings
103 ms
button.856debeac157d9669cf51e73a08fbc93.js
2 ms
embeds
40 ms
embeds
55 ms
embeds
69 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.en.html
33 ms
9RkfBY4NJsx.js
29 ms
FEppCFCt76d.png
25 ms
recordiplayer.com accessibility score
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
recordiplayer.com 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
Issues were logged in the Issues panel in Chrome Devtools
recordiplayer.com 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
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recordiplayer.com 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 Recordiplayer.com 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.
recordiplayer.com
Open Graph description is not detected on the main page of Record IPlayer. 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: