5 sec in total
528 ms
4.2 sec
331 ms
Welcome to p22.me homepage info - get ready to check P 22 best content right away, or after learning these important things about p22.me
Visit p22.meWe analyzed P22.me page load time and found that the first response time was 528 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
p22.me performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.9 s
29/100
25%
Value4.8 s
67/100
10%
Value1,480 ms
14/100
30%
Value0.104
89/100
15%
Value6.6 s
58/100
10%
528 ms
190 ms
229 ms
218 ms
259 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 82% of them (49 requests) were addressed to the original P22.me, 10% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain P22.me.
Page size can be reduced by 499.2 kB (68%)
736.6 kB
237.4 kB
In fact, the total size of P22.me main page is 736.6 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. 40% of websites need less resources to load. Javascripts take 391.8 kB which makes up the majority of the site volume.
Potential reduce by 26.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 26.5 kB or 79% of the original size.
Potential reduce by 16.6 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, P 22 needs image optimization as it can save up to 16.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 295.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 295.0 kB or 75% of the original size.
Potential reduce by 161.0 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. P22.me needs all CSS files to be minified and compressed as it can save up to 161.0 kB or 85% of the original size.
Number of requests can be reduced by 39 (74%)
53
14
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of P 22. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.p22.me
528 ms
style.css
190 ms
white.css
229 ms
styles.css
218 ms
prettyPhoto.css
259 ms
tipsy.css
245 ms
responsive.css
240 ms
css
109 ms
css
149 ms
jquery-1.8.3.min.js
125 ms
bootstrap.min.js
356 ms
scripts.js
343 ms
jquery-ui.min.js
165 ms
modenizr.min.js
345 ms
jquery.livequery.min.js
341 ms
jquery.superbgimage.min.js
362 ms
custom-superbgimage.js
398 ms
swfobject.js
435 ms
jwplayer.js
578 ms
jquery.isotope.min.js
468 ms
jquery.imagesLoaded.min.js
447 ms
supersubs.js
466 ms
superfish.js
510 ms
jquery.fitvids.min.js
561 ms
jquery.easing.1.3.js
573 ms
jquery.prettyPhoto.js
616 ms
iScroll.js
615 ms
jquery.tipsy.min.js
712 ms
custom.js
1186 ms
jquery.mousewheel.min.js
774 ms
froogaloop2.min.js
97 ms
style.css
588 ms
style_480px.css
600 ms
bg-scanlines-thumbs.png
141 ms
bg-expander-arrow.png
122 ms
grid.png
124 ms
responsive-menu.gif
125 ms
bg-scanlines.png
133 ms
logo2.png
248 ms
bg-fsg-play.png
153 ms
bg-fullsize-arrow.png
171 ms
bg-expander-arrow.png
168 ms
bg-thumb-controls.png
182 ms
timthumb.php
339 ms
bg-thmb-photo.png
288 ms
timthumb.php
371 ms
timthumb.php
386 ms
timthumb.php
384 ms
timthumb.php
522 ms
timthumb.php
396 ms
timthumb.php
451 ms
timthumb.php
534 ms
8d6bGRHQjSQfnRvIX_v_pwLUuEpTyoUstqEm5AMlJo4.ttf
103 ms
hpORcvLZtemlH8gI-1S-7sDdSZkkecOE1hvV7ZHvhyU.ttf
120 ms
We_iSDqttE3etzfdfhuPRcLUaXXPEM4GWmkZydH3hOH3rGVtsTkPsbDajuO5ueQw.ttf
134 ms
We_iSDqttE3etzfdfhuPRRHlw86iTBCnepaAC4pvZz_3rGVtsTkPsbDajuO5ueQw.ttf
134 ms
YDAoLskQQ5MOAgvHUQCcLdiVVvVwwdPZOs3JFCTDF40.ttf
134 ms
We_iSDqttE3etzfdfhuPRW5RrA-htkXx3JSGX8orHqr3rGVtsTkPsbDajuO5ueQw.ttf
134 ms
loading.gif
113 ms
IMG_1423.jpg
1764 ms
p22.me 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
p22.me 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
p22.me 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 P22.me 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 P22.me 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.
p22.me
Open Graph data is detected on the main page of P 22. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: