4.5 sec in total
112 ms
3.8 sec
522 ms
Welcome to pocketberry.com homepage info - get ready to check Pocketberry best content right away, or after learning these important things about pocketberry.com
Get the latest BlackBerry News, Reviews, Themes and Games all in One Place. Berry Users Welcome.
Visit pocketberry.comWe analyzed Pocketberry.com page load time and found that the first response time was 112 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pocketberry.com performance score
112 ms
786 ms
96 ms
64 ms
64 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 7% of them (8 requests) were addressed to the original Pocketberry.com, 44% (47 requests) were made to Ft1f6y6ru4-flywheel.netdna-ssl.com and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Gstatic.com.
Page size can be reduced by 2.1 MB (38%)
5.7 MB
3.5 MB
In fact, the total size of Pocketberry.com main page is 5.7 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. 85% 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. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 54.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 54.5 kB or 82% of the original size.
Potential reduce by 1.1 MB
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, Pocketberry needs image optimization as it can save up to 1.1 MB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 700.3 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 700.3 kB or 69% of the original size.
Potential reduce by 268.5 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. Pocketberry.com needs all CSS files to be minified and compressed as it can save up to 268.5 kB or 87% of the original size.
Number of requests can be reduced by 42 (43%)
97
55
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocketberry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
pocketberry.com
112 ms
www.pocketberry.com
786 ms
ga.js
96 ms
wp-emoji-release.min.js
64 ms
widget.css
64 ms
styles.css
64 ms
settings.css
60 ms
socialfans-style.css
76 ms
style.css
65 ms
css
149 ms
style.css
87 ms
responsive.css
94 ms
prettyPhoto.css
82 ms
font-awesome.min.css
96 ms
jquery.js
93 ms
jquery-migrate.min.js
125 ms
jquery.themepunch.tools.min.js
124 ms
jquery.themepunch.revolution.min.js
124 ms
socialfans-script.js
123 ms
picturefill.min.js
126 ms
jquery.prettyPhoto.js
124 ms
adsbygoogle.js
198 ms
comment-reply.min.js
121 ms
jquery.form.min.js
124 ms
scripts.js
123 ms
bunyad-theme.js
123 ms
jquery.flexslider-min.js
193 ms
wp-embed.min.js
193 ms
KonaLibInline.js
194 ms
__utm.gif
111 ms
PocketBerryLogo1.png
36 ms
PocketBerryStickyLogo.png
35 ms
Navigation-Shortcuts_1-Copy-702x336.png
182 ms
Priv-By-BlackBerry-702x336.png
97 ms
Priv_AccessoryOverlook-702x336.png
369 ms
2015-10-23-09_51_11-ShopBlackBerry-Online-Store-BlackBerry-PRIV1-558x336.png
330 ms
2015-02-16-18_18_05-BlackBerry%C2%AE-Classic-Highlights-ATT-YouTube-702x336.png
436 ms
2015-10-23-09_51_11-ShopBlackBerry-Online-Store-BlackBerry-PRIV1-351x185.png
178 ms
logo-good-home-312x115-168x137.png
176 ms
IMG_20150203_171947-168x137.png
320 ms
Navigation-Shortcuts_1-Copy-351x185.png
434 ms
Priv-By-BlackBerry-351x185.png
366 ms
Priv_AccessoryOverlook-351x185.png
365 ms
logo-good-home-312x115-351x185.png
367 ms
Passport-Classic-ATT-351x185.png
459 ms
2015-02-16-18_18_05-BlackBerry%C2%AE-Classic-Highlights-ATT-YouTube-351x185.png
603 ms
ATT-BlackBerry-Classic-and-Passport-351x185.png
549 ms
Classic-Hi-Res.png
641 ms
Capture15_47_32.jpg
452 ms
bbiphone.png
457 ms
tmobile-blackberry-bold-9900-110x96.jpg
463 ms
torch-giveaway-110x96.jpg
464 ms
BlackBerry-Bold-9700-Giveaway-copy.jpg
502 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
83 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
85 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
166 ms
collect
340 ms
fontawesome-webfont.woff
437 ms
ca-pub-7389636685146402.js
332 ms
zrt_lookup.html
343 ms
show_ads_impl.js
244 ms
Navigation-Shortcuts_1-Copy-702x336.png
242 ms
Priv-By-BlackBerry-702x336.png
231 ms
2015-02-16-18_18_05-BlackBerry%C2%AE-Classic-Highlights-ATT-YouTube-702x336.png
230 ms
Passport-Classic-ATT-351x185.png
141 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
148 ms
socialfans.woff
148 ms
ads
354 ms
osd.js
58 ms
ads
235 ms
ads
961 ms
count.js
102 ms
KonaHtml5.js
13 ms
likebox.php
906 ms
KonaGet.js
70 ms
css
975 ms
m_js_controller.js
795 ms
abg.js
830 ms
googlelogo_color_112x36dp.png
1113 ms
453413449917857422
779 ms
admin-ajax.php
1037 ms
kyEKgjk51ZE.css
554 ms
kTub4bakEmM.css
569 ms
FAHeNGXgPup.js
753 ms
FJmpeSpHpjS.js
798 ms
0wM5s1Khldu.js
797 ms
1bNoFZUdlYZ.js
795 ms
5896474904448219677
327 ms
s
289 ms
x_button_blue2.png
174 ms
favicon
241 ms
nessie_icon_tiamat_white.png
161 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
159 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
47 ms
26767_379874518911_7565999_n.jpg
160 ms
12208260_973071229422362_7371324304235499340_n.jpg
153 ms
12524350_518853154984262_7123519344725381494_n.jpg
155 ms
11400962_10206110398692992_3764926199315308195_n.jpg
155 ms
11127482_10100176494121710_2564132896426709941_n.jpg
152 ms
270466_108666225893487_2489762_n.jpg
160 ms
12800184_1682643121994657_3318159556413053077_n.jpg
151 ms
11796431_1160073547341164_2665212541994794883_n.jpg
167 ms
944040_1554326248214818_1740898447746213158_n.jpg
167 ms
wL6VQj7Ab77.png
61 ms
s7jcwEQH7Sx.png
60 ms
I6-MnjEovm5.js
87 ms
pQrUxxo5oQp.js
88 ms
ui
132 ms
pocketberry.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocketberry.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 Pocketberry.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.
pocketberry.com
Open Graph description is not detected on the main page of Pocketberry. 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: