4.2 sec in total
146 ms
3.6 sec
513 ms
Click here to check amazing Pochos content. Otherwise, check out these important facts you probably never knew about pochos.com
Fishing charters, half to full day for great fishing in Cabo, the best way to enjoy a trip in Cabo San Lucas
Visit pochos.comWe analyzed Pochos.com page load time and found that the first response time was 146 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pochos.com performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value6.2 s
11/100
25%
Value4.6 s
70/100
10%
Value1,890 ms
9/100
30%
Value0.507
16/100
15%
Value6.2 s
62/100
10%
146 ms
53 ms
294 ms
7 ms
29 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 9% of them (12 requests) were addressed to the original Pochos.com, 26% (33 requests) were made to Static.xx.fbcdn.net and 10% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 928.5 kB (57%)
1.6 MB
708.3 kB
In fact, the total size of Pochos.com main page is 1.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 942.1 kB which makes up the majority of the site volume.
Potential reduce by 49.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 49.3 kB or 70% of the original size.
Potential reduce by 4.2 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. Pochos images are well optimized though.
Potential reduce by 637.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 637.0 kB or 68% of the original size.
Potential reduce by 238.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. Pochos.com needs all CSS files to be minified and compressed as it can save up to 238.1 kB or 83% of the original size.
Number of requests can be reduced by 66 (59%)
112
46
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pochos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
pochos.com
146 ms
index_en.html
53 ms
index.html
294 ms
buttons.js
7 ms
loader.js
29 ms
addthis_widget.js
38 ms
facebook-icon.png
47 ms
pochos_header_home.jpg
256 ms
left_bgTop.gif
101 ms
grn_strike.gif
99 ms
mintgrn.png
99 ms
New-Reel-Busy-Home-Teaser.jpg
249 ms
AugustHotBirte.jpg
135 ms
left_bgBottom.gif
146 ms
pochos_footerbg.gif
145 ms
wejs
107 ms
WidgetEmbed-selfserveprop
103 ms
cdswidSSP-v2414594452a.css%20%27%29%3B
17 ms
cdswidgets_m-c-v2102084671a.js
411 ms
cdswidSSP-v2414594452a.css
254 ms
s2UhQsONfKI
90 ms
CCzGndql2q4
113 ms
www-embed-player-vflfNyN_r.css
119 ms
www-embed-player.js
426 ms
base.js
470 ms
likebox.php
784 ms
jgLm_0U3Ftc
100 ms
300lo.json
442 ms
getAllAppDefault.esi
395 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
129 ms
ad_status.js
181 ms
ebiMDO3r-8l.css
382 ms
jGc-59L_9lo.css
465 ms
6qHpHChjY_J.css
529 ms
ztINr5qMqM_.css
695 ms
uVjHKJ0glvg.css
682 ms
ZY-3seVVf0G.css
669 ms
W9IvqTWpWa9.css
575 ms
q68gy-v_YMF.js
723 ms
FJmpeSpHpjS.js
755 ms
0wM5s1Khldu.js
692 ms
1bNoFZUdlYZ.js
750 ms
njO1TPvGzoR.js
751 ms
1QuX41zDRrx.js
751 ms
Oagsvfb4VWi.js
778 ms
LTv6ZK-5zxz.js
976 ms
1FCa-btixu2.js
842 ms
IjqSyiwKeaX.js
777 ms
rBxSIHk4zIe.js
847 ms
n6VgtouijQL.js
796 ms
7BE0CZr3HTs.js
846 ms
pQrUxxo5oQp.js
910 ms
_UYztdBNTjs.js
863 ms
-7JBD_ybv4q.js
1042 ms
Kt4tkgSRvHH.js
913 ms
sh.8e5f85691f9aaa082472a194.html
113 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
187 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
186 ms
getSegment.php
72 ms
checkOAuth.esi
62 ms
t.dhj
112 ms
t.dhj
46 ms
18 ms
2214
47 ms
pixel
18 ms
pixel
17 ms
pixel
18 ms
pixel
37 ms
pixel
43 ms
pixel
27 ms
pixel
38 ms
cm
48 ms
x35248
141 ms
pixel
39 ms
s-3271.xgi
32 ms
match-result
36 ms
match-result
67 ms
match-result
37 ms
match-result
20 ms
hbpix
471 ms
24 ms
xrefid.xgi
9 ms
20 ms
pixel
40 ms
2981
29 ms
hoverbuttons.6eab8de2ee93b309873157b6d3f977fe.css
8 ms
hoverbuttons.035267d71d894482eb413e5bea488ff5.js
8 ms
155924_226178027519954_1645795630_n.jpg
291 ms
safe_image.php
350 ms
482498_226166634187760_1955771567_n.jpg
346 ms
1910592_1060034084055258_2857009813691089495_n.jpg
415 ms
1914663_156521518071865_1256487278570011981_n.jpg
482 ms
12662711_10207214371655216_3702535973914183500_n.jpg
486 ms
11903810_10155923493985223_2300266343832742665_n.jpg
487 ms
10154030_1468801060016524_191426100_n.jpg
481 ms
1916951_129496920758066_3749671802911354848_n.jpg
482 ms
12508714_906812532748353_8506088020740112393_n.jpg
482 ms
10484046_631636503640769_860269834983512935_n.jpg
613 ms
12496798_688558557926044_1447427221_n.jpg
615 ms
12510340_1122577767760833_6434431949463296698_n.jpg
549 ms
5784_604277623043324_8377675462138674192_n.jpg
547 ms
wL6VQj7Ab77.png
131 ms
s7jcwEQH7Sx.png
132 ms
sSwLTfB7PfP.png
132 ms
QDwYpIaRyfG.png
131 ms
l5aPruN9xMM.png
129 ms
K00K-UgnsKu.png
130 ms
b8XhdWI9eAN.js
77 ms
K_65vAc89SX.png
74 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
14 ms
buttons.ab966a004186897711de4a5ed256c924.css
14 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
8 ms
st.1188278743c14064d5e8ae56c8ada29c.js
17 ms
I6-MnjEovm5.js
78 ms
150_logo-11900-2.png
30 ms
s4.5.gif
72 ms
ga.js
17 ms
mini_Top_Cap.png
12 ms
facebook_32.png
12 ms
mini_BG.png
8 ms
mini_Bottom_Cap.png
9 ms
pinterest_32.png
15 ms
googleplus_32.png
17 ms
twitter_32.png
53 ms
email_32.png
52 ms
sharethis_32.png
50 ms
__utm.gif
14 ms
pochos.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
pochos.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pochos.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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Pochos.com 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 Pochos.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.
pochos.com
Open Graph description is not detected on the main page of Pochos. 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: