5.4 sec in total
245 ms
1.8 sec
3.4 sec
Click here to check amazing Pulipuli content for Taiwan. Otherwise, check out these important facts you probably never knew about pulipuli.info
布丁布丁吃布丁分享網頁技術、讀書心得的園地。
Visit pulipuli.infoWe analyzed Pulipuli.info page load time and found that the first response time was 245 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pulipuli.info performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value8.2 s
2/100
25%
Value4.3 s
75/100
10%
Value5,220 ms
0/100
30%
Value0
100/100
15%
Value10.8 s
22/100
10%
245 ms
79 ms
133 ms
91 ms
96 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pulipuli.info, 9% (11 requests) were made to Apis.google.com and 6% (8 requests) were made to Blogblog.com. The less responsive or slowest element that took the longest time to load (721 ms) relates to the external source Lh3.googleusercontent.com.
Page size can be reduced by 1.0 MB (22%)
4.7 MB
3.7 MB
In fact, the total size of Pulipuli.info main page is 4.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. 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. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 258.7 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 258.7 kB or 77% of the original size.
Potential reduce by 242.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. Pulipuli images are well optimized though.
Potential reduce by 512.5 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 512.5 kB or 65% of the original size.
Potential reduce by 9 B
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. Pulipuli.info has all CSS files already compressed.
Number of requests can be reduced by 33 (27%)
122
89
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pulipuli. 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 4 to 1 for CSS and as a result speed up the page load time.
blog.pulipuli.info
245 ms
3645911276-widget_css_bundle.css
79 ms
authorization.css
133 ms
blogger-template.min.css
91 ms
blogger-index.css
96 ms
plusone.js
117 ms
addthis_widget.js
55 ms
jquery.min.js
47 ms
pulipuli.blogspot.com.min.js
69 ms
all.js
305 ms
3226477086-widgets.js
66 ms
blogger-template.min.css
209 ms
pulipuli.blogspot.com.min.js
617 ms
blogger-index.css
250 ms
bg_body.gif
330 ms
icon18_edit_allbkg.gif
29 ms
2016-03-02_081809_thumb.png
355 ms
pixel.gif
552 ms
pixel.png
178 ms
pudding%28500px%29_thumb%5B5%5D.gif
177 ms
icon18_wrench_allbkg.png
25 ms
14---5_thumb.png
322 ms
20140721_174009_thumb%25255B2%25255D.jpg
320 ms
IMAG0262_thumb.jpg
321 ms
image_thumb%25255B9%25255D.png
464 ms
image_thumb.png
466 ms
2016-03-01_174458_thumb.png
465 ms
2016-03-01_174458_thumb%25255B1%25255D.png
538 ms
2016-03-01_175828_thumb.png
465 ms
2016-03-01_175905_thumb.png
466 ms
2016-03-01_175905%252520-%252520Copy_thumb.png
500 ms
2016-03-01_180536_thumb.png
541 ms
2016-03-01_180622_thumb%25255B1%25255D.png
541 ms
2016-03-01_180808_thumb%25255B1%25255D.png
539 ms
2016-03-01_180847_thumb.png
538 ms
2016-03-01_202007_thumb.png
538 ms
2016-03-01_202607_thumb.png
540 ms
2016-03-01_202607%252520-%252520Copy_thumb.png
542 ms
2016-03-01_203301_thumb.png
551 ms
2016-03-01_203350_thumb.png
539 ms
2016-03-01_203511_thumb.png
547 ms
2016-03-01_203730_thumb.png
547 ms
2016-03-01_203914_thumb.png
608 ms
2016-03-01_204426_thumb.png
552 ms
2016-03-01_204508_thumb.png
552 ms
2016-03-01_204745_thumb.png
638 ms
2016-03-01_204837_thumb.png
633 ms
2016-03-01_205157_thumb.png
633 ms
2016-03-01_205644_thumb.png
636 ms
2016-03-01_205606_thumb.png
635 ms
2016-03-01_205926_thumb.png
630 ms
2016-03-01_210038_thumb.png
720 ms
2016-03-01_210138_thumb.png
714 ms
2016-03-01_210400_thumb.png
715 ms
2016-03-01_210646_thumb.png
713 ms
2016-03-01_210935_thumb.png
712 ms
2016-03-01_211040_thumb.png
712 ms
2016-03-01_212042_thumb.png
719 ms
2016-03-01_160300_thumb.png
721 ms
2016-03-01_160424_thumb.png
720 ms
cb=gapi.loaded_0
291 ms
cb=gapi.loaded_1
427 ms
google_top_exp.js
315 ms
icon_header.gif
289 ms
bg_content.gif
291 ms
icon_list_item_left.gif
289 ms
blogger-icon-set.png
505 ms
bg_sidebar.gif
159 ms
bg_sidebar_arrow.gif
270 ms
icon_sidebar_heading_left.gif
270 ms
icon_list_item.gif
268 ms
subscribe-icon-set.png
371 ms
2016-03-01_160300_thumb%25255B1%25255D.png
391 ms
stats
219 ms
300lo.json
127 ms
2016-03-01_160530_thumb.png
278 ms
2016-03-01_160559_thumb.png
273 ms
2016-03-01_160706_thumb.png
276 ms
100 ms
sh.8e5f85691f9aaa082472a194.html
145 ms
blank.html
66 ms
navbar.g
70 ms
2016-03-01_164515_thumb.png
252 ms
bg_header_footer.png
148 ms
xd_arbiter.php
311 ms
xd_arbiter.php
535 ms
2016-03-01_165326_thumb.png
207 ms
2016-03-01_165429_thumb.png
205 ms
2016-03-01_165803_thumb.png
259 ms
2016-03-01_170044_thumb%25255B1%25255D.png
268 ms
2016-03-01_170617_thumb.png
265 ms
2016-03-01_170847_thumb.png
265 ms
2016-03-01_170941_thumb.png
261 ms
2016-03-01_102258_thumb.png
263 ms
coffee%252520-%25252048.png
261 ms
2016-03-01_102635_thumb.png
262 ms
padding_header_footer.png
99 ms
icons_peach.png
178 ms
platform:gapi.iframes.style.common.js
95 ms
arrows-light.png
178 ms
2016-03-01_102859_thumb.png
254 ms
2016-03-01_102949_thumb.png
252 ms
2016-03-01_102258_thumb%25255B2%25255D.png
251 ms
blogger-icon-set.png
169 ms
subscribe-icon-set.png
173 ms
2016-03-01_103348_thumb.png
257 ms
2016-03-01_103420_thumb.png
257 ms
layers.e5ea973510bf60b3db41.js
77 ms
2016-03-01_103730_thumb.png
228 ms
2016-03-01_104145_thumb.png
204 ms
2016-03-01_102258_thumb%25255B1%25255D.png
204 ms
chart
89 ms
2016-03-01_105109_thumb.png
202 ms
2016-03-01_110748_thumb.png
205 ms
2016-03-01_111127_thumb.png
204 ms
1%252520-%2525201_thumb%25255B1%25255D.png
216 ms
cb=gapi.loaded_0
70 ms
cb=gapi.loaded_1
68 ms
fastbutton
131 ms
2016-02-21_002650_thumb.png
146 ms
2016-03-01_113439_thumb.png
143 ms
pablo%252520%2525282%252529_thumb.png
132 ms
postmessageRelay
117 ms
cb=gapi.loaded_0
65 ms
cb=gapi.loaded_1
64 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
41 ms
3193398744-postmessagerelay.js
22 ms
rpc:shindig_random.js
28 ms
cb=gapi.loaded_0
3 ms
pulipuli.info accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
pulipuli.info 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pulipuli.info SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pulipuli.info 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pulipuli.info 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.
pulipuli.info
Open Graph description is not detected on the main page of Pulipuli. 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: