8.6 sec in total
1.1 sec
6.7 sec
786 ms
Click here to check amazing FunP content for Taiwan. Otherwise, check out these important facts you probably never knew about funp.com
台灣第一數位媒體經銷商 - Facebook Google Microsoft 網路廣告台灣合作伙伴
Visit funp.comWe analyzed Funp.com page load time and found that the first response time was 1.1 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
funp.com performance score
name
value
score
weighting
Value21.7 s
0/100
10%
Value44.9 s
0/100
25%
Value60.0 s
0/100
10%
Value10,820 ms
0/100
30%
Value0.039
99/100
15%
Value51.7 s
0/100
10%
1121 ms
1402 ms
1092 ms
448 ms
439 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Funp.com, 44% (48 requests) were made to Cacafly.com and 32% (35 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Cacafly.com.
Page size can be reduced by 673.6 kB (23%)
3.0 MB
2.3 MB
In fact, the total size of Funp.com main page is 3.0 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 93.0 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. This page needs HTML code to be minified as it can gain 12.4 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 93.0 kB or 88% of the original size.
Potential reduce by 158.7 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. FunP images are well optimized though.
Potential reduce by 344.4 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 344.4 kB or 66% of the original size.
Potential reduce by 77.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. Funp.com needs all CSS files to be minified and compressed as it can save up to 77.5 kB or 84% of the original size.
Number of requests can be reduced by 45 (44%)
103
58
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FunP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
funp.com
1121 ms
cacafly.com
1402 ms
cacafly.min.css
1092 ms
magnific_popup.css
448 ms
styles.css
439 ms
frontend.css
444 ms
pagenavi-css.css
464 ms
jquery.min.js
32 ms
gtm4wp-form-move-tracker.js
455 ms
js
85 ms
gmap.js
447 ms
modernizr.js
458 ms
appendAround.js
453 ms
jquery.hc-sticky.min.js
433 ms
jquery.magnific_popup.min.js
669 ms
bootstrap.min.js
965 ms
stepper.js
644 ms
off-canvas.js
649 ms
animation.js
647 ms
all.js
964 ms
jquery.form.min.js
966 ms
scripts.js
966 ms
logo.svg
245 ms
%E7%B6%93%E7%87%9F%E6%B2%BF%E9%9D%A9.png
710 ms
Between-x-cacaFly-1480x500.png
1804 ms
carousel-arrow-prev.svg
252 ms
carousel-arrow-next.svg
250 ms
instagram-locket1-738x369.jpg
709 ms
shutterstock_142162594-3961x1981.jpg
3241 ms
service-fb-ads.svg
520 ms
service-fb-page.svg
517 ms
service-msn.svg
710 ms
service-skype.svg
705 ms
service-google.svg
927 ms
service-youtube.svg
929 ms
customer-type1.svg
933 ms
customer-type2.svg
930 ms
customer-type3.svg
1134 ms
customer-type4.svg
1137 ms
block-mask.png
2003 ms
common.js
117 ms
map.js
131 ms
util.js
190 ms
marker.js
188 ms
contact-form-sent.svg
1091 ms
StaticMapService.GetMapImage
427 ms
StaticMapService.GetMapImage
245 ms
StaticMapService.GetMapImage
247 ms
gtm.js
159 ms
debug.js
437 ms
nav-icon-index-hover.svg
1194 ms
nav-icon-about-hover.svg
1197 ms
nav-icon-fb-hover.svg
1215 ms
nav-icon-msn-hover.svg
1411 ms
nav-icon-google-hover.svg
1413 ms
nav-icon-contact-hover.svg
1448 ms
nav-icon-english-hover.svg
1630 ms
nav-extra-icon-fb.svg
1634 ms
nav-extra-icon-phone.svg
1672 ms
ajax-loader.gif
1848 ms
infowindow.js
75 ms
onion.js
44 ms
openhand_8_8.cur
123 ms
ViewportInfoService.GetViewportInfo
159 ms
stats.js
79 ms
controls.js
76 ms
ViewportInfoService.GetViewportInfo
150 ms
ViewportInfoService.GetViewportInfo
148 ms
analytics.js
85 ms
fbevents.js
139 ms
transparent.png
47 ms
css
211 ms
spotlight-poi.png
101 ms
google4.png
118 ms
mapcnt6.png
203 ms
sv5.png
209 ms
collect
177 ms
collect
214 ms
243 ms
tmapctrl.png
190 ms
tmapctrl4.png
165 ms
imgs8.png
167 ms
vt
129 ms
vt
125 ms
vt
149 ms
vt
103 ms
vt
99 ms
vt
98 ms
vt
102 ms
vt
126 ms
vt
126 ms
vt
126 ms
vt
126 ms
vt
125 ms
vt
182 ms
vt
145 ms
vt
145 ms
vt
143 ms
vt
143 ms
vt
142 ms
vt
174 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
82 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
128 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
168 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
178 ms
168 ms
AuthenticationService.Authenticate
280 ms
xd_arbiter.php
167 ms
xd_arbiter.php
287 ms
funp.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
funp.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
funp.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
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
Tap targets are not sized appropriately
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funp.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Funp.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.
funp.com
Open Graph data is detected on the main page of FunP. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: