6.9 sec in total
1.6 sec
4.9 sec
471 ms
Welcome to briankp.com homepage info - get ready to check Briankp best content right away, or after learning these important things about briankp.com
Selamat datang di website saya, briankp.com
Visit briankp.comWe analyzed Briankp.com page load time and found that the first response time was 1.6 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
briankp.com performance score
1577 ms
196 ms
384 ms
138 ms
141 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 82% of them (63 requests) were addressed to the original Briankp.com, 10% (8 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Briankp.com.
Page size can be reduced by 1.7 MB (30%)
5.8 MB
4.0 MB
In fact, the total size of Briankp.com main page is 5.8 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. 55% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 50.1 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 50.1 kB or 79% of the original size.
Potential reduce by 121.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. Briankp images are well optimized though.
Potential reduce by 434.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 434.0 kB or 72% of the original size.
Potential reduce by 1.1 MB
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. Briankp.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 89% of the original size.
Number of requests can be reduced by 36 (55%)
66
30
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Briankp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
briankp.com
1577 ms
wp-emoji-release.min.js
196 ms
briankp.com
384 ms
autoAlbums.css
138 ms
datetimepicker.css
141 ms
styles.css
162 ms
public.css
224 ms
magnific-popup.css
267 ms
js_composer.css
919 ms
masterslider.main.css
477 ms
custom.css
318 ms
style.css
677 ms
font.min.css
585 ms
jquery.fancybox.css
452 ms
jquery.js
694 ms
jquery-migrate.min.js
571 ms
rotate-patch.js
597 ms
autoAlbums.min.js
754 ms
autoAlbums.js
697 ms
waypoints.min.js
706 ms
datetimepicker.js
883 ms
jquery.magnific-popup.min.js
854 ms
jquery.cookie.js
816 ms
public.js
826 ms
modernizr.js
862 ms
css
29 ms
wp-power-stats.js
995 ms
jquery.form.min.js
996 ms
scripts.js
996 ms
odio-global-plugins.js
1052 ms
odio.js
998 ms
comment-reply.min.js
996 ms
jquery.fancybox.pack.js
1090 ms
jquery.fancybox-media.js
998 ms
jquery.easing.min.js
1048 ms
masterslider.min.js
1294 ms
js_composer_front.js
1160 ms
waypoints.min.js
1113 ms
font-awesome.css
38 ms
blog_bg.png
242 ms
loader_w2.gif
279 ms
briankpdotcom.png
561 ms
blank.gif
284 ms
AHF_40382-100x80.jpg
332 ms
IMG_8495-100x80.jpg
560 ms
sheila-on-7-Konser-Cinta-Musik-Indonesia-2927-100x80.jpg
561 ms
musim-yang-baik.jpg
838 ms
blank-large.gif
561 ms
Sabian_cymbals_logo.svg.png
729 ms
DW-Logo-2000-copy.png
613 ms
PDP-LOGO-BW-plain1-copy.png
567 ms
Brian-KP-02.jpg
1070 ms
sheila-on-7-Konser-Cinta-Musik-Indonesia-2927.jpg
1709 ms
Sheila-on-7-Konser-Cinta-Musik-Indonesia-7833.jpg
1200 ms
AHF_4358.jpg
1363 ms
handnmove.cur
810 ms
footer_bg.jpg
1224 ms
dark_grunge_wall.png
1108 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
48 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
49 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
51 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
49 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
51 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
50 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
49 ms
ozythemes.svg
1747 ms
ozythemes.woff
1459 ms
MonoSocialIconsFont-1.10.svg
1607 ms
MonoSocialIconsFont-1.10.ttf
1656 ms
12825737_838586606270146_930679209_n.jpg
340 ms
12822504_1714265528788544_760405894_n.jpg
344 ms
10362167_1698916987014616_1485453714_n.jpg
251 ms
11809920_193269551050611_1274076327_n.jpg
342 ms
loading-2.gif
1095 ms
progress.gif
1246 ms
AHF_40382.jpg
1794 ms
briankp.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Briankp.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 Briankp.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.
briankp.com
Open Graph data is detected on the main page of Briankp. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: