10.3 sec in total
1.6 sec
7.8 sec
932 ms
Click here to check amazing Jojam content for Taiwan. Otherwise, check out these important facts you probably never knew about jojam.tw
This domain may be for sale!
Visit jojam.twWe analyzed Jojam.tw page load time and found that the first response time was 1.6 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jojam.tw performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value3.9 s
51/100
25%
Value4.1 s
79/100
10%
Value370 ms
71/100
30%
Value0.272
45/100
15%
Value4.1 s
86/100
10%
1612 ms
601 ms
616 ms
602 ms
615 ms
Our browser made a total of 178 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Jojam.tw, 19% (34 requests) were made to Mainpage.pixfs.net and 7% (12 requests) were made to Imageproxy.pimg.tw. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source S.pimg.tw.
Page size can be reduced by 263.6 kB (8%)
3.4 MB
3.2 MB
In fact, the total size of Jojam.tw main page is 3.4 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. 75% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 89.9 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 89.9 kB or 79% of the original size.
Potential reduce by 65.0 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. Jojam images are well optimized though.
Potential reduce by 76.9 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 76.9 kB or 28% of the original size.
Potential reduce by 31.7 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. Jojam.tw needs all CSS files to be minified and compressed as it can save up to 31.7 kB or 76% of the original size.
Number of requests can be reduced by 60 (34%)
177
117
The browser has sent 177 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jojam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.pixnet.net
1612 ms
construction.min.css
601 ms
index.min.css
616 ms
new-navigation.min.css
602 ms
new_guide.css
615 ms
jquery.min.js
144 ms
zh_TW.js
161 ms
pix.min.js
685 ms
pixlogger.min.js
695 ms
jquery.timers.js
688 ms
jquery.cookie.js
708 ms
jquery.onAppear.min.js
708 ms
checklogin.php
1310 ms
checklogin.min.js
692 ms
swfobject.js
694 ms
mainpage.min.js
606 ms
ad.min.js
687 ms
ie9.js
667 ms
c.js
235 ms
yepnope.1.5.4-min.js
173 ms
scripts.min.js
140 ms
reload.js
148 ms
event.js
158 ms
jquery.scrolldepth.min.js
159 ms
mixpanel-init.js
157 ms
tools.min.js
11 ms
590x393.jpg
1605 ms
92x0.png
1641 ms
92x0.png
1563 ms
92x0.png
1631 ms
92x0.png
382 ms
92x0.png
1633 ms
92x0.png
1554 ms
openid-button-pixnet.png
101 ms
1454644140-2265992571.png
1609 ms
zoomcrop
1151 ms
590x393.jpg
1596 ms
350x263.jpg
1546 ms
230x263.jpg
2690 ms
170x173.jpg
1526 ms
170x173.jpg
1538 ms
350x263.png
3206 ms
230x263.jpg
3205 ms
170x173.jpg
3203 ms
350x263.jpg
1708 ms
170x173.jpg
1607 ms
170x173.jpg
1615 ms
350x263.jpg
1736 ms
230x263.jpg
1708 ms
170x173.png
1709 ms
350x263.jpg
1709 ms
230x263.jpg
1722 ms
170x173.jpg
1718 ms
350x263.jpg
1718 ms
170x173.jpg
1727 ms
170x173.jpg
1732 ms
350x263.png
1795 ms
230x263.jpg
1737 ms
170x173.jpg
1739 ms
170x173.jpg
1771 ms
350x263.jpg
1809 ms
230x263.png
1798 ms
170x173.jpg
1806 ms
170x173.jpg
1812 ms
350x263.png
1821 ms
170x173.jpg
1816 ms
190x263.jpg
1821 ms
190x263.jpg
1828 ms
190x263.jpg
1828 ms
170x173.jpg
1837 ms
350x263.jpg
1850 ms
openid-button-google.png
67 ms
openid-button-facebook.png
67 ms
openid-button-live.png
63 ms
openid-button-yahoo.png
64 ms
footer_logo.png
64 ms
92x0.png
626 ms
1454641090-3224293991.jpg
1550 ms
92x0.png
1583 ms
zoomcrop
1112 ms
zoomcrop
1111 ms
zoomcrop
1113 ms
zoomcrop
1111 ms
zoomcrop
1110 ms
zoomcrop
1507 ms
zoomcrop
1493 ms
zoomcrop
1491 ms
zoomcrop
1505 ms
zoomcrop
1490 ms
zoomcrop
1540 ms
atrk.js
321 ms
new-nav-bg.png
76 ms
main-channel-hover.png
104 ms
channel-bg.png
98 ms
more-arrow-down.png
97 ms
logo.png
98 ms
searchicon.png
98 ms
searchselecticon.png
98 ms
hoticon.png
283 ms
featuretitlebg.png
282 ms
arrowleft.png
284 ms
arrowright.png
285 ms
orange-arrow.jpg
281 ms
login_send.jpg
281 ms
arrow-up.png
481 ms
articletitlebg.png
481 ms
dc.js
1061 ms
pa.gif
1817 ms
mixpanel-2.2.min.js
1407 ms
pi.min.js
428 ms
js
2127 ms
count.php
1546 ms
count.php
1634 ms
count.php
1630 ms
count.php
1644 ms
count.php
1628 ms
count.php
1681 ms
count.php
1684 ms
count.php
1837 ms
count.php
1838 ms
atrk.gif
1166 ms
pi.gif
1378 ms
__utm.gif
227 ms
__utm.gif
91 ms
__utm.gif
110 ms
__utm.gif
109 ms
__utm.gif
103 ms
170x173.jpg
334 ms
190x263.jpg
362 ms
190x263.jpg
359 ms
190x263.jpg
322 ms
170x173.jpg
346 ms
170x173.jpg
296 ms
350x263.png
295 ms
60 ms
170x173.jpg
206 ms
190x263.jpg
218 ms
190x263.jpg
235 ms
190x263.png
213 ms
170x173.jpg
217 ms
170x173.png
225 ms
170x173.jpg
225 ms
190x263.jpg
219 ms
190x263.jpg
218 ms
170x173.jpg
218 ms
170x173.jpg
235 ms
230x263.jpg
212 ms
170x173.jpg
193 ms
170x173.jpg
177 ms
350x263.jpg
204 ms
230x263.jpg
160 ms
170x173.jpg
174 ms
170x173.jpg
170 ms
1bd1d029cb6c98267795e86eb4ac42af-a58519babc3457a6.jpg
1013 ms
661344ec9e0d85c8ee0f7183ac1c6b7d-9b56ae1924c73c9d.html
1286 ms
adsbygoogle.js
154 ms
adsbygoogle.js
229 ms
info-li.jpg
199 ms
blog_li.gif
99 ms
bf465612ce82452c2de4588752b52d30-b039a93814ba49c2.jpg
893 ms
604576691b17b182bd76177833f25ac5-8bf05696f17fd3e8.gif
928 ms
b4144ea0c45a5ad54a4b3eaffdca66fa-adda42243e2873a1.png
893 ms
d6ac7f09c286dc9065d8942901b7a816-a6bb86b1edca1802.jpg
928 ms
ca-pub-2647689032095179.js
69 ms
zrt_lookup.html
81 ms
show_ads_impl.js
307 ms
ads
283 ms
osd.js
108 ms
ads
275 ms
m_js_controller.js
46 ms
abg.js
112 ms
googlelogo_color_112x36dp.png
132 ms
15322343910875618778
67 ms
13255652248101393325
68 ms
s
40 ms
x_button_blue2.png
19 ms
runtime.js
76 ms
-Wxc5n6ag8mSVPmrosQZJ6hEHpQooK3Qr1Gxv0lUkvE.js
4 ms
jojam.tw accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
jojam.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
jojam.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jojam.tw can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Jojam.tw 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.
jojam.tw
Open Graph description is not detected on the main page of Jojam. 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: