4.1 sec in total
73 ms
3.3 sec
719 ms
Visit runmygeek.com now to see the best up-to-date Runmygeek content and also check out these interesting facts you probably never knew about runmygeek.com
手机应用市场有哪些?✅安卓应用市场哪个好?✅App下载资源网✅整理了最好用的应用市场下载手机版,包括华为应用市场、360应用市场、应用宝、木蚂蚁应用市场等,还有手机应用市场排行榜供大家参考选择哦!需要安卓第三方应用市场的朋友,赶快来看一看吧!
Visit runmygeek.comWe analyzed Runmygeek.com page load time and found that the first response time was 73 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.
runmygeek.com performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value10.9 s
0/100
25%
Value10.6 s
7/100
10%
Value20 ms
100/100
30%
Value0.018
100/100
15%
Value12.1 s
16/100
10%
73 ms
792 ms
46 ms
245 ms
56 ms
Our browser made a total of 216 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Runmygeek.com, 15% (33 requests) were made to Apis.google.com and 9% (20 requests) were made to Blog.runmygeek.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Snapwidget.com.
Page size can be reduced by 4.6 MB (30%)
15.6 MB
11.0 MB
In fact, the total size of Runmygeek.com main page is 15.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. Only a small number of websites need less resources to load. Images take 14.0 MB which makes up the majority of the site volume.
Potential reduce by 218.5 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 218.5 kB or 80% of the original size.
Potential reduce by 3.5 MB
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. Obviously, Runmygeek needs image optimization as it can save up to 3.5 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 801.3 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 801.3 kB or 67% of the original size.
Potential reduce by 110.1 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. Runmygeek.com needs all CSS files to be minified and compressed as it can save up to 110.1 kB or 74% of the original size.
Number of requests can be reduced by 90 (42%)
212
122
The browser has sent 212 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runmygeek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
runmygeek.com
73 ms
www.runmygeek.com
792 ms
3645911276-widget_css_bundle.css
46 ms
authorization.css
245 ms
plusone.js
56 ms
mootools-yui-compressed.js
52 ms
plusone.js
55 ms
recent_comments_widget.js
182 ms
3226477086-widgets.js
18 ms
cb=gapi.loaded_0
54 ms
background.png
439 ms
icon18_wrench_allbkg.png
21 ms
IMAG1683_2_thumb%25255B7%25255D.jpg
142 ms
image_thumb10.png
144 ms
101_5149_thumb4.jpg
141 ms
back.PNG
141 ms
image_thumb%25255B6%25255D.png
146 ms
image_thumb%25255B58%25255D.png
150 ms
image_thumb%25255B41%25255D.png
147 ms
image_thumb%25255B47%25255D.png
144 ms
image_thumb%25255B52%25255D.png
145 ms
image_thumb%25255B38%25255D.png
147 ms
image_thumb3.png
140 ms
image_thumb%25255B12%25255D.png
153 ms
image_thumb%25255B6%25255D.png
151 ms
image_thumb%25255B17%25255D.png
158 ms
10295331_10152372828633724_3553774200936017928_o_thumb%25255B6%25255D.jpg
152 ms
DSC_0054_thumb%25255B5%25255D.jpg
156 ms
IMG_0452_thumb%25255B7%25255D.jpg
159 ms
image_thumb%25255B27%25255D.png
161 ms
image%25255B5%25255D.png
160 ms
rss.png
432 ms
twitter.png
432 ms
search.gif
430 ms
facebook.png
433 ms
gplus.png
433 ms
photosphere.png
458 ms
movescount.png
460 ms
email.png
461 ms
date.png
458 ms
user.png
461 ms
comments.png
458 ms
icon18_edit_allbkg.gif
11 ms
IMG_5682_thumb%25255B8%25255D.jpg
136 ms
image_thumb%25255B19%25255D.png
137 ms
DSC_0108_thumb%25255B4%25255D.jpg
134 ms
PANO_20140703_065859_thumb%25255B6%25255D.jpg
134 ms
image_thumb%25255B23%25255D.png
137 ms
image_thumb%25255B6%25255D.png
145 ms
image_thumb%25255B16%25255D.png
148 ms
1538769_759937917391294_8503243905915914496_n%252520%2525281%252529_thumb%25255B5%25255D.jpg
144 ms
image_thumb%25255B10%25255D.png
154 ms
image_thumb%25255B60%25255D.png
135 ms
IMG_5494_thumb%25255B5%25255D.jpg
133 ms
image_thumb%25255B24%25255D.png
144 ms
image_thumb%25255B29%25255D.png
149 ms
image_thumb%25255B19%25255D.png
146 ms
image_thumb%25255B13%25255D.png
149 ms
DSC_000001_thumb%25255B5%25255D.jpg
141 ms
image_thumb%25255B25%25255D.png
140 ms
image_thumb%25255B18%25255D.png
151 ms
image%25255B41%25255D.png
244 ms
image_thumb%25255B6%25255D.png
153 ms
wlEmoticon-smile%25255B2%25255D.png
148 ms
image_thumb%25255B6%25255D.png
151 ms
wlEmoticon-smile%25255B2%25255D.png
150 ms
1897799_10152163185499613_355965978347906831_n_thumb%25255B9%25255D.jpg
152 ms
image_thumb%25255B24%25255D.png
135 ms
2014%252520-%2525201%252520%2525281%252529_thumb%25255B7%25255D.jpg
138 ms
image_thumb%25255B16%25255D.png
133 ms
image_thumb%25255B13%25255D.png
135 ms
image_thumb%25255B2%25255D.png
142 ms
image_thumb%25255B2%25255D.png
143 ms
image_thumb%25255B10%25255D.png
145 ms
858909_10152372829403724_8903538962886272399_o_thumb%25255B5%25255D.jpg
141 ms
cb=gapi.loaded_1
117 ms
google_top_exp.js
117 ms
img_4_10_139.gif
29 ms
all.js
28 ms
navbar.g
172 ms
blank.html
148 ms
RunmygeekHeader.png
1102 ms
search-bg.png
223 ms
nav-bg.png
222 ms
nav-hover.png
223 ms
418c3037f25b84aefc0e179205e57b6fdb7575dc
166 ms
sidebar-tab.png
185 ms
blogger_index.js
68 ms
icons_peach.png
162 ms
platform:gapi.iframes.style.common.js
59 ms
arrows-light.png
267 ms
likebox.php
266 ms
strava-widget-df7e9c9bf07b52d15d8a5992d76f16ee.css
81 ms
strava-head-e2dcbf12e93fb23d5530f39814fa1160.js
82 ms
en-US-8a0032b97f41c342fc74ac67b548864d.js
82 ms
application-db1db54ec4fecae20b1dd89d9fcad578.js
159 ms
1136 ms
arrow.png
132 ms
292 ms
noavatar92.png
131 ms
avatar92.jpg
241 ms
avatar92.jpg
292 ms
xd_arbiter.php
273 ms
xd_arbiter.php
344 ms
share_buttons_20_3.png
211 ms
blog-post-reactions.g
267 ms
cb=gapi.loaded_0
199 ms
cb=gapi.loaded_1
260 ms
fastbutton
330 ms
count.js
243 ms
widgets.js
535 ms
sprites-widget.png
134 ms
sprites-widget-1db581bbf43b42943796685f3b6a545a.png
133 ms
subscribe_widget
397 ms
ebiMDO3r-8l.css
175 ms
jGc-59L_9lo.css
203 ms
q68gy-v_YMF.js
241 ms
FJmpeSpHpjS.js
269 ms
0wM5s1Khldu.js
269 ms
1bNoFZUdlYZ.js
268 ms
1442378207-rx.js
39 ms
postmessageRelay
167 ms
aggregates
152 ms
aggregates
145 ms
aggregates
145 ms
aggregates
254 ms
aggregates
251 ms
aggregates
249 ms
checks_sprite.png
45 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
57 ms
aggregates
214 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
210 ms
aggregates
205 ms
aggregates
215 ms
aggregates
216 ms
summary
155 ms
3193398744-postmessagerelay.js
392 ms
rpc:shindig_random.js
147 ms
524344_469476779752882_621386982_n.jpg
377 ms
270364_226698170697412_3740340_n.jpg
385 ms
540620_100612450078193_521748808_n.jpg
385 ms
12705699_10156475193550332_5309870027734410867_n.jpg
423 ms
10298857_770394132984820_8248235402001176620_n.jpg
422 ms
12644995_1120289328023652_5382699598668366135_n.jpg
421 ms
12802919_987363468008673_5525359549233907335_n.jpg
500 ms
1621714_487106674732884_1597978480_n.jpg
422 ms
11018613_10206206617948344_4507251908285551240_n.jpg
422 ms
wL6VQj7Ab77.png
78 ms
s7jcwEQH7Sx.png
78 ms
www-subscribe-widget-vfl12QHVw.css
131 ms
photo.jpg
368 ms
www-subscribe-widget.js
137 ms
youtube_icon_small-vfliqe9hM.jpg
363 ms
ga.js
61 ms
nr-885.min.js
251 ms
www-hitchhiker-vflvB63an.png
232 ms
cb=gapi.loaded_2
114 ms
cb=gapi.loaded_3
114 ms
followers
421 ms
fastbutton
191 ms
fastbutton
193 ms
fastbutton
179 ms
fastbutton
182 ms
fastbutton
173 ms
fastbutton
305 ms
fastbutton
289 ms
fastbutton
220 ms
fastbutton
349 ms
fastbutton
317 ms
loading-bar-black.png
88 ms
__utm.gif
133 ms
fleche1.png
107 ms
fleche2.png
107 ms
cb=gapi.loaded_0
157 ms
ff691e9a81
66 ms
postmessageRelay
38 ms
rs=AGLTcCN6UIYAmnu0cr-4slqp9InuL0Hd1w
81 ms
rs=AGLTcCMnDeXbzq1T_DzqIKnxZkbM5OL1-w
74 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
8 ms
cb=gapi.loaded_0
91 ms
cb=gapi.loaded_1
88 ms
combined.css
96 ms
smoothDivScroll.css
94 ms
stack_161235.js
149 ms
jquery.min.js
94 ms
cb=gapi.loaded_0
64 ms
gprofile_button-16.png
38 ms
photo.jpg
168 ms
photo.jpg
189 ms
photo.jpg
181 ms
photo.jpg
152 ms
rs=AGLTcCOJ4AMNA1EZSgGPzZnainRbXAPPWA
33 ms
rs=AGLTcCNIVR3IhVk5e6Kqi348h2cYEewZvQ
76 ms
photo.jpg
184 ms
photo.jpg
185 ms
photo.jpg
182 ms
photo.jpg
183 ms
photo.jpg
204 ms
photo.jpg
207 ms
photo.jpg
209 ms
photo.jpg
192 ms
cpw-7de38e2bb0.png
122 ms
analytics.js
71 ms
stackpile.api-bfb5078e74.js
96 ms
12797694_525904257580696_380918704_n.jpg
242 ms
12798153_1126010507433631_2099196147_n.jpg
330 ms
12826221_1563965610583793_1140114271_n.jpg
381 ms
12797913_1566996240280820_1965147339_n.jpg
386 ms
12822414_201952266830870_237264413_n.jpg
352 ms
12534224_970734876351132_1793929883_n.jpg
384 ms
data
150 ms
collect
5 ms
collect
62 ms
stackpile.api-bfb5078e74.js
24 ms
runmygeek.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.
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
Links do not have a discernible name
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.
runmygeek.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
runmygeek.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Runmygeek.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 Runmygeek.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.
runmygeek.com
Open Graph description is not detected on the main page of Runmygeek. 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: