21.3 sec in total
2.4 sec
18.5 sec
382 ms
Click here to check amazing Geimian content for Taiwan. Otherwise, check out these important facts you probably never knew about geimian.com
给面(Geimian.com)是一个景语花草的地方,舒心悦目。给面小站微信公众号:geimianle
Visit geimian.comWe analyzed Geimian.com page load time and found that the first response time was 2.4 sec and then it took 18.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
geimian.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value5.5 s
18/100
25%
Value3.9 s
82/100
10%
Value1,040 ms
25/100
30%
Value0
100/100
15%
Value5.7 s
69/100
10%
2443 ms
9222 ms
12 ms
2506 ms
397 ms
Our browser made a total of 264 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Geimian.com, 16% (41 requests) were made to Tpc.googlesyndication.com and 15% (40 requests) were made to Tupian.geimian.com. The less responsive or slowest element that took the longest time to load (9.2 sec) relates to the external source Tupian.geimian.com.
Page size can be reduced by 182.8 kB (15%)
1.2 MB
1.0 MB
In fact, the total size of Geimian.com main page is 1.2 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. 60% of websites need less resources to load. Images take 960.3 kB which makes up the majority of the site volume.
Potential reduce by 49.8 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 49.8 kB or 78% of the original size.
Potential reduce by 10.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. Geimian images are well optimized though.
Potential reduce by 123.0 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 123.0 kB or 63% of the original size.
Number of requests can be reduced by 185 (70%)
263
78
The browser has sent 263 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geimian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 86 to 1 for JavaScripts and as a result speed up the page load time.
www.geimian.com
2443 ms
mini.js
9222 ms
gpt.js
12 ms
hm.js
2506 ms
logo.gif
397 ms
2016-03-14_163500-100x100.jpg
794 ms
2016-03-18_112205-100x100.jpg
794 ms
8c3d104cb30b449efb00c459ad980133-100x100.jpg
795 ms
2016-03-17_185611-100x100.jpg
803 ms
2016-03-17_152041-100x100.jpg
804 ms
2016-03-17_110600-100x100.jpg
878 ms
2016-03-16_200227-100x100.jpg
1222 ms
2016-03-15_112150-100x100.jpg
1184 ms
2016-03-15_105216-100x100.jpg
1185 ms
2016-03-15_102228-100x100.jpg
1197 ms
2016-03-14_201051-100x100.jpg
1199 ms
2016-03-14_170910-100x100.jpg
1310 ms
2016-03-14_130140-100x100.jpg
1581 ms
2016-03-14_105121-100x100.jpg
1582 ms
2016-03-14_085350-100x100.jpg
1589 ms
2016-03-12_105954-100x100.jpg
1601 ms
topbeijingdatu.jpg
2382 ms
mengceng.png
1732 ms
pubads_impl_82.js
74 ms
wxgzh.jpg
1943 ms
shtsbz.png
1944 ms
container.html
9 ms
2015-02-21_2242111.jpg
2280 ms
20150414_194453_103.jpg
2701 ms
2015-09-12_092745.jpg
2517 ms
2015-09-14_134436.jpg
3475 ms
2015-07-23_092822.jpg
3515 ms
2015-06-05_172813.jpg
3290 ms
20150214_210425_110gm.jpg
3098 ms
2015-10-09_183607.jpg
3412 ms
2015-05-23_002924.jpg
3109 ms
20150324_211002_3581.jpg
3918 ms
2015-12-04_105630.jpg
3937 ms
640.jpg
4532 ms
2015-05-23_000224.jpg
4294 ms
20150414_192605_018.jpg
4413 ms
2015-07-04_152439.jpg
4310 ms
ads
63 ms
ajs.php
33 ms
osd.js
6 ms
lg.php
24 ms
ads
38 ms
container.html
6 ms
ajs.php
66 ms
match.aspx
19 ms
lg.php
25 ms
ads
30 ms
container.html
6 ms
match.aspx
10 ms
mmexport1412166625444.jpeg
4663 ms
ajs.php
30 ms
lg.php
27 ms
match.aspx
25 ms
ads
35 ms
container.html
5 ms
ajs.php
61 ms
lg.php
21 ms
ads
64 ms
container.html
5 ms
match.aspx
10 ms
ajs.php
59 ms
lg.php
27 ms
ads
38 ms
container.html
8 ms
ajs.php
50 ms
tabbj.png
3680 ms
fding.gif
4059 ms
lg.php
19 ms
ads
45 ms
container.html
7 ms
ajs.php
58 ms
107 ms
lg.php
26 ms
ads
43 ms
container.html
9 ms
ajs.php
63 ms
lg.php
21 ms
106 ms
ads
38 ms
container.html
4 ms
ajs.php
61 ms
lg.php
18 ms
107 ms
ads
32 ms
container.html
4 ms
ajs.php
60 ms
lg.php
20 ms
108 ms
ads
71 ms
container.html
5 ms
ajs.php
24 ms
lg.php
29 ms
109 ms
ads
40 ms
container.html
6 ms
ajs.php
58 ms
lg.php
23 ms
106 ms
ads
36 ms
container.html
8 ms
ajs.php
68 ms
lg.php
27 ms
106 ms
ads
32 ms
container.html
6 ms
ajs.php
63 ms
lg.php
31 ms
119 ms
ads
31 ms
container.html
6 ms
ajs.php
34 ms
lg.php
24 ms
ads
35 ms
container.html
6 ms
activeview
12 ms
ajs.php
22 ms
lg.php
23 ms
107 ms
ads
34 ms
container.html
7 ms
ajs.php
20 ms
activeview
23 ms
lg.php
23 ms
ads
36 ms
container.html
9 ms
ajs.php
58 ms
activeview
13 ms
lg.php
26 ms
106 ms
ads
60 ms
container.html
7 ms
activeview
14 ms
ajs.php
59 ms
lg.php
27 ms
137 ms
ads
36 ms
container.html
8 ms
ajs.php
77 ms
activeview
14 ms
lg.php
16 ms
118 ms
ads
35 ms
container.html
14 ms
hm.gif
436 ms
activeview
14 ms
ajs.php
21 ms
lg.php
24 ms
ads
33 ms
container.html
11 ms
ajs.php
20 ms
activeview
15 ms
lg.php
23 ms
107 ms
ads
34 ms
container.html
4 ms
ajs.php
59 ms
lg.php
21 ms
106 ms
ads
36 ms
container.html
5 ms
activeview
24 ms
ajs.php
62 ms
lg.php
29 ms
115 ms
ads
35 ms
container.html
11 ms
activeview
14 ms
ajs.php
22 ms
lg.php
29 ms
ads
33 ms
container.html
8 ms
activeview
16 ms
ajs.php
24 ms
lg.php
27 ms
121 ms
ads
36 ms
container.html
6 ms
ajs.php
43 ms
lg.php
14 ms
activeview
18 ms
ads
37 ms
container.html
6 ms
ajs.php
60 ms
activeview
14 ms
lg.php
21 ms
106 ms
ads
36 ms
container.html
6 ms
ajs.php
61 ms
activeview
14 ms
lg.php
17 ms
118 ms
ads
34 ms
container.html
6 ms
activeview
13 ms
ajs.php
21 ms
lg.php
27 ms
ads
38 ms
container.html
8 ms
ajs.php
26 ms
activeview
24 ms
lg.php
30 ms
119 ms
ads
37 ms
container.html
6 ms
ajs.php
21 ms
activeview
29 ms
lg.php
26 ms
ads
31 ms
container.html
8 ms
ajs.php
20 ms
activeview
27 ms
lg.php
23 ms
107 ms
ads
33 ms
container.html
13 ms
ajs.php
61 ms
lg.php
30 ms
106 ms
ads
33 ms
container.html
7 ms
activeview
14 ms
ajs.php
58 ms
lg.php
46 ms
106 ms
ads
35 ms
container.html
23 ms
ajs.php
63 ms
activeview
12 ms
lg.php
28 ms
111 ms
ads
34 ms
container.html
18 ms
activeview
16 ms
ajs.php
59 ms
lg.php
20 ms
106 ms
ads
36 ms
container.html
17 ms
activeview
15 ms
activeview
17 ms
ajs.php
60 ms
lg.php
23 ms
108 ms
ads
32 ms
container.html
16 ms
activeview
63 ms
ajs.php
20 ms
lg.php
29 ms
ads
45 ms
container.html
7 ms
activeview
25 ms
ajs.php
63 ms
lg.php
13 ms
106 ms
ads
34 ms
container.html
15 ms
activeview
19 ms
activeview
56 ms
geimian.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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.
geimian.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
geimian.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geimian.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Geimian.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.
geimian.com
Open Graph description is not detected on the main page of Geimian. 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: