2.2 sec in total
46 ms
1.9 sec
268 ms
Click here to check amazing Xxi content. Otherwise, check out these important facts you probably never knew about xxi.net
Jean Shepherd, OTR, old time radio, vintage radio, old time radio shows, old time radio programs, old time radio broadcasts dvd, dvds, mp3, mp3s, cd, cds, cd-rom, cd-roms, history, historical, media, ...
Visit xxi.netWe analyzed Xxi.net page load time and found that the first response time was 46 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
xxi.net performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value5.1 s
24/100
25%
Value5.3 s
58/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value5.1 s
76/100
10%
46 ms
158 ms
641 ms
20 ms
328 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Xxi.net, 91% (50 requests) were made to Onesmedia.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (641 ms) relates to the external source Onesmedia.com.
Page size can be reduced by 95.7 kB (6%)
1.5 MB
1.4 MB
In fact, the total size of Xxi.net main page is 1.5 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 29.4 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 4.5 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 29.4 kB or 79% of the original size.
Potential reduce by 37.3 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. Xxi images are well optimized though.
Potential reduce by 23.6 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 23.6 kB or 22% of the original size.
Potential reduce by 5.4 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. Xxi.net needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 36% of the original size.
Number of requests can be reduced by 18 (35%)
51
33
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xxi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
xxi.net
46 ms
onesmedia.com
158 ms
onesmedia.com
641 ms
css
20 ms
styles.css
328 ms
cart_dropdown.css
335 ms
responsive-menu.css
336 ms
stylesheet.css
339 ms
stylesheet_css_buttons.css
337 ms
stylesheet_flex.css
337 ms
stylesheet_reward.css
389 ms
jscript_browserselector.js
401 ms
jscript_utils.js
400 ms
jquery-latest.min.js
4 ms
script.js
401 ms
modernizr.custom.js
403 ms
jquery-1.8.3.min.js
466 ms
jquery.elevatezoom.js
511 ms
classie.js
464 ms
jquery.flexslider.js
536 ms
css
18 ms
jquery.min.js
18 ms
logo.png
62 ms
cart-icon.png
65 ms
menu-line.gif
63 ms
search-icon.png
64 ms
mob-menu.png
64 ms
slide1.jpg
138 ms
slide2.jpg
184 ms
slide3.jpg
240 ms
home-top.png
352 ms
home1.jpg
127 ms
home2.jpg
185 ms
home3.jpg
192 ms
8003678_125475188288.jpg
202 ms
Christmas-400x400.jpg
301 ms
BostonBlackieCaseFL.jpg
368 ms
stars_5.gif
254 ms
_radio500.jpg
120 ms
Radio.png
269 ms
Radio1.png
362 ms
Radio.png
375 ms
Audiobooks.png
333 ms
Films.png
369 ms
Shep.png
398 ms
pixel_trans.gif
414 ms
LOGO-YT-1.png
427 ms
USPS.png
432 ms
header_stripes_dark.png
411 ms
facebook.png
402 ms
googleplus.png
419 ms
pinterest.png
435 ms
youtube.png
449 ms
_radio500.jpg
376 ms
print_stylesheet.css
66 ms
xxi.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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
xxi.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
xxi.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Xxi.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 Xxi.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.
xxi.net
Open Graph description is not detected on the main page of Xxi. 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: