5.5 sec in total
1.1 sec
4.3 sec
183 ms
Welcome to mobile-phone.com.tw homepage info - get ready to check Mobile Phone best content for Taiwan right away, or after learning these important things about mobile-phone.com.tw
您可以藉由台灣地區電信公司手機行動電話號碼09********黃頁,了解此電話號碼是屬於台灣哪家電信公司所有,並搜尋此電話號碼是否為您親戚、朋友、同事、同學的手機,並知道電話號碼的所有人、姓名、地址、位置。
Visit mobile-phone.com.twWe analyzed Mobile-phone.com.tw page load time and found that the first response time was 1.1 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mobile-phone.com.tw performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value5.0 s
27/100
25%
Value12.3 s
3/100
10%
Value3,420 ms
2/100
30%
Value0.4
25/100
15%
Value16.3 s
5/100
10%
1062 ms
66 ms
589 ms
24 ms
44 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 12% of them (7 requests) were addressed to the original Mobile-phone.com.tw, 20% (12 requests) were made to Pagead2.googlesyndication.com and 15% (9 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Mobile-phone.com.tw.
Page size can be reduced by 47.8 kB (7%)
669.9 kB
622.1 kB
In fact, the total size of Mobile-phone.com.tw main page is 669.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 482.0 kB which makes up the majority of the site volume.
Potential reduce by 33.4 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 33.4 kB or 79% of the original size.
Potential reduce by 9.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. Mobile Phone images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.4 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. Mobile-phone.com.tw has all CSS files already compressed.
Number of requests can be reduced by 38 (72%)
53
15
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Phone. 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 5 to 1 for CSS and as a result speed up the page load time.
mobile-phone.com.tw
1062 ms
js
66 ms
bootstrap.css
589 ms
css
24 ms
css
44 ms
style.css
490 ms
jquery-1.11.1.min.js
507 ms
bootstrap.min.js
512 ms
adsbygoogle.js
161 ms
lazysizes.min.js
731 ms
mobile-phone.jpg
2568 ms
show_ads_impl.js
386 ms
zrt_lookup.html
37 ms
ads
822 ms
ads
484 ms
ads
680 ms
gen_204
153 ms
pixel
160 ms
15960947152522928367
43 ms
abg_lite.js
33 ms
omrhp.js
30 ms
Q12zgMmT.js
38 ms
window_focus.js
43 ms
qs_click_protection.js
47 ms
ufs_web_display.js
42 ms
icon.png
33 ms
62bHydCX.html
103 ms
activeview
100 ms
pixel
137 ms
pixel
130 ms
pixel
81 ms
14669872687542355869
82 ms
gen_204
111 ms
5V18NYvu480-MhEwM9GnRWI4eEDE4R9vNdKnUFhfqY0.js
17 ms
activeview
84 ms
bounce
66 ms
rum
67 ms
reactive_library.js
174 ms
ca-pub-8880509461572798
83 ms
pixel
30 ms
pixel
28 ms
rum
32 ms
e10d98ca8348a1bc72c6a647c7a3d6dd.js
31 ms
34003fe632427c457541f7d0476ab8d7.js
35 ms
load_preloaded_resource.js
10 ms
bbe3fbefe89164063f731512d72e756f.js
49 ms
abg_lite.js
11 ms
02221ee50246d3c2837239ae1fe911f3.js
118 ms
fullscreen_api_adapter.js
7 ms
interstitial_ad_frame.js
13 ms
d5c175e96e8fc864528f80175c8e991e.js
45 ms
feedback_grey600_24dp.png
38 ms
settings_grey600_24dp.png
42 ms
s
63 ms
css
32 ms
activeview
127 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
29 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
30 ms
14763004658117789537
13 ms
mobile-phone.com.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.
mobile-phone.com.tw 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
Browser errors were logged to the console
Page has valid source maps
mobile-phone.com.tw 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
![]()
JA
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile-phone.com.tw 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 Mobile-phone.com.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.
mobile-phone.com.tw
Open Graph data is detected on the main page of Mobile Phone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: