3.7 sec in total
147 ms
3 sec
614 ms
Welcome to 22media.com homepage info - get ready to check 22 Media best content right away, or after learning these important things about 22media.com
Marketing Analyst & Webhead
Visit 22media.comWe analyzed 22media.com page load time and found that the first response time was 147 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
22media.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.6 s
60/100
25%
Value2.9 s
95/100
10%
Value160 ms
94/100
30%
Value0.099
90/100
15%
Value3.8 s
89/100
10%
147 ms
1032 ms
168 ms
246 ms
199 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 22media.com, 92% (66 requests) were made to Joehall.me and 1% (1 request) were made to Statcounter.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Joehall.me.
Page size can be reduced by 422.3 kB (32%)
1.3 MB
891.6 kB
In fact, the total size of 22media.com main page is 1.3 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. 50% of websites need less resources to load. Images take 942.7 kB which makes up the majority of the site volume.
Potential reduce by 41.5 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 41.5 kB or 77% of the original size.
Potential reduce by 176.1 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. Obviously, 22 Media needs image optimization as it can save up to 176.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 139.0 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 139.0 kB or 65% of the original size.
Potential reduce by 65.7 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. 22media.com needs all CSS files to be minified and compressed as it can save up to 65.7 kB or 64% of the original size.
Number of requests can be reduced by 27 (40%)
68
41
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 22 Media. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
22media.com
147 ms
joehall.me
1032 ms
wp-emoji-release.min.js
168 ms
dashicons.min.css
246 ms
thickbox.css
199 ms
style.css
124 ms
style.css
158 ms
social_widget.css
200 ms
jquery.js
260 ms
jquery-migrate.min.js
230 ms
thickbox.js
265 ms
jquery.cycle2.min.js
270 ms
jquery.cycle2.carousel.min.js
290 ms
jquery.cycle2.flip.min.js
292 ms
jquery.cycle2.scrollVert.min.js
315 ms
jquery.cycle2.shuffle.min.js
313 ms
jquery.cycle2.tile.min.js
333 ms
jquery.cycle2.caption2.min.js
333 ms
jquery.cycle2.swipe.min.js
336 ms
jquery.easing.1.3.js
356 ms
counter.js
7 ms
hoverIntent.min.js
62 ms
superfish.min.js
89 ms
superfish.args.min.js
89 ms
superfish.compat.min.js
96 ms
wp-embed.min.js
112 ms
css
529 ms
smashing.jpg
248 ms
logo.png
247 ms
gray-texture.jpg
246 ms
dashes.png
245 ms
3870006964_4d20288227_m.jpg
314 ms
quote-icon.png
245 ms
comment-icon.jpg
290 ms
Selection_004.png
339 ms
4667174817_d8c653175c_m-181x100.jpg
377 ms
equal.jpg
374 ms
studiopress-logo-169x100.png
363 ms
922445_10100193153251586_1346257289_o.jpg
488 ms
ayers.jpg
492 ms
rss.png
485 ms
marissa_new4.jpg
559 ms
trading.jpg
608 ms
bullet.png
439 ms
ct.jpg
557 ms
fastcompany.jpg
570 ms
hls.jpg
613 ms
marketingpilgrim1.jpg
575 ms
mash.jpg
651 ms
graywolf.jpg
660 ms
mit.jpg
652 ms
npr.jpg
619 ms
OM.jpg
668 ms
rww.jpg
657 ms
sej.jpg
712 ms
sel.jpg
694 ms
si.jpg
696 ms
tnw.jpg
700 ms
tp.jpg
747 ms
wwd.jpg
711 ms
yahoo.jpg
737 ms
rss.png
778 ms
googleplus.png
801 ms
twitter.png
771 ms
t.php
363 ms
270c.png
258 ms
smashing.jpg
556 ms
linkedin.png
567 ms
return-top-arrow.png
553 ms
loadingAnimation.gif
591 ms
88x31.png
30 ms
arrow-down.png
552 ms
22media.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
22media.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
22media.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 22media.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that 22media.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.
22media.com
Open Graph data is detected on the main page of 22 Media. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: