4.9 sec in total
870 ms
3.4 sec
640 ms
Click here to check amazing Gphonefans content for Taiwan. Otherwise, check out these important facts you probably never knew about gphonefans.net
首頁
Visit gphonefans.netWe analyzed Gphonefans.net page load time and found that the first response time was 870 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gphonefans.net performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value4.0 s
50/100
25%
Value4.8 s
66/100
10%
Value730 ms
40/100
30%
Value0
100/100
15%
Value5.9 s
65/100
10%
870 ms
31 ms
7 ms
931 ms
557 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 47% of them (48 requests) were addressed to the original Gphonefans.net, 10% (10 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Gphonefans.net.
Page size can be reduced by 371.3 kB (23%)
1.6 MB
1.3 MB
In fact, the total size of Gphonefans.net main page is 1.6 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 53.6 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 53.6 kB or 76% of the original size.
Potential reduce by 45.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. Gphonefans images are well optimized though.
Potential reduce by 182.6 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 182.6 kB or 53% of the original size.
Potential reduce by 89.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. Gphonefans.net needs all CSS files to be minified and compressed as it can save up to 89.5 kB or 81% of the original size.
Number of requests can be reduced by 44 (44%)
100
56
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gphonefans. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
gphonefans.net
870 ms
jquery.min.js
31 ms
adsbygoogle.js
7 ms
style_18_common.css
931 ms
style_18_portal_index.css
557 ms
common.js
745 ms
forum.js
559 ms
portal.js
374 ms
mobanbus_pace.js
376 ms
jQuery.js
1114 ms
mobanbusjs.js
559 ms
logging.js
741 ms
md5.js
742 ms
bus_fixed.js
743 ms
sdk.js
71 ms
148 ms
mobanbus.js
766 ms
logo.png
214 ms
87c994fdbfd868669a5d1659d7fc8098.jpg
377 ms
0193f38f310cb1fcc2a78be0306f5543.jpg
611 ms
4fd8aa58aabec610d8bfc8d9178ffa6d.jpg
612 ms
ab75181b53618ce0911b3bccdf500d13.jpg
613 ms
7c88a10f173b0b122e33dc642ce68679.jpg
229 ms
563499c32e089bc3d2b1decd503854f8.jpg
804 ms
285340700fb88d40b366bedf5fc13804.jpg
415 ms
3bba55d5182732eed6a92f9f8d3f6266.jpg
610 ms
49bd53509f6bc3db772b9438f2a892b7.jpg
802 ms
2f68a3b5f464e5a5733b8c4b2ae49a06.jpg
804 ms
default_small.png
826 ms
adc9ed3827b6df142064a7e9c9692b29.jpg
802 ms
c99c5dade8fd99f4c888610ebe9a6795.jpg
802 ms
b87364ba2fcd89b4fb6282005c01042a.jpg
1004 ms
e6ee7b5840da0cf5cebfadb06aa805f7.jpg
1004 ms
6bb95127e5bbfdf17bb0658aaa6aeffe.jpg
1004 ms
af1a563bded2b0de2a905263850e5bb7.jpg
1008 ms
7024f843204f2ee2c68e663beaecf971.jpg
1007 ms
a40a0b2bbaa1af504351c8d342722af2.jpg
1007 ms
7f529152bf10f845b5c61ea331ba4e05.jpg
1174 ms
5ecc32805219c80fae4f0dcc748dc8bf.jpg
1177 ms
36de56a71563f8a591f0331f4f23e3d5.jpg
1174 ms
88559062231f41a6e98aa563df95d733.jpg
1179 ms
2e8e23acf90380424b3136b3d86d0e5d.jpg
1176 ms
acf580d34db4711ff9e26d5bb9d9df49.jpg
1176 ms
864072f4de86901a9bf91c8741238acd.jpg
1359 ms
92ef80ed5d21a1c384deff8670ecb80f.jpg
1358 ms
ca-pub-9342790973897850.js
99 ms
zrt_lookup.html
94 ms
show_ads_impl.js
56 ms
focus_bg.png
1333 ms
bus_slider.png
1335 ms
connect-icons.png
1292 ms
ads
403 ms
osd.js
8 ms
dot.gif
1241 ms
ads
452 ms
ads
373 ms
ads
307 ms
ga.js
30 ms
__utm.gif
19 ms
__utm.gif
63 ms
scrolltop.png
1240 ms
pla
39 ms
xd_arbiter.php
74 ms
xd_arbiter.php
132 ms
e2e7b72ef0540a9ae475a8445e87ea43.jpg
1183 ms
410b7ca4fcd2227cde35fdd1b7ae9dab.jpg
1185 ms
page.php
156 ms
11843839964176452914
122 ms
abg.js
60 ms
m_js_controller.js
65 ms
googlelogo_color_112x36dp.png
135 ms
s_0ROEw3z8GL_180908036.html
104 ms
s
67 ms
x_button_blue2.png
70 ms
favicon
145 ms
nessie_icon_tiamat_white.png
32 ms
favicon
97 ms
I3s9kgwIvys.css
104 ms
dgd0S1ND-P9.css
137 ms
_rx8naC75Dy.js
199 ms
x5F9OMjKyLw.js
240 ms
ICDbTSzjQEg.js
239 ms
TTCre3391I0.js
237 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
11 ms
cl
111 ms
creative_add_on.js
212 ms
new_contactcenter_1296_wbr_display_ad_300_250_A_11_15.jpg
130 ms
lidar.js
88 ms
sbhK2lTE.js
87 ms
cTrvNaRi.html
42 ms
surly.js
124 ms
1455048_590263261037951_312213980_n.jpg
118 ms
74066_120539041343711_2422653_n.jpg
121 ms
wL6VQj7Ab77.png
103 ms
s7jcwEQH7Sx.png
103 ms
ba.html
12 ms
4.gif
15 ms
activeview
32 ms
I6-MnjEovm5.js
26 ms
vlXaquuXMrr.js
36 ms
2532.js
14 ms
box_19_top-right.png
5 ms
ci.png
5 ms
gphonefans.net accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
gphonefans.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
gphonefans.net 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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gphonefans.net 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 Chinese. Our system also found out that Gphonefans.net 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.
gphonefans.net
Open Graph description is not detected on the main page of Gphonefans. 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: