1.9 sec in total
111 ms
1.5 sec
283 ms
Click here to check amazing My Location content for United States. Otherwise, check out these important facts you probably never knew about mylocation.org
Your location as seen from the Internet using your IP address and the new HTML5 geolocation feature.
Visit mylocation.orgWe analyzed Mylocation.org page load time and found that the first response time was 111 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
mylocation.org performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value7.9 s
3/100
25%
Value8.5 s
18/100
10%
Value6,850 ms
0/100
30%
Value0.194
63/100
15%
Value14.6 s
8/100
10%
111 ms
34 ms
61 ms
107 ms
101 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 25% of them (17 requests) were addressed to the original Mylocation.org, 22% (15 requests) were made to Maps.google.com and 14% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (344 ms) relates to the external source S6.monohost.com.
Page size can be reduced by 567.0 kB (45%)
1.3 MB
706.5 kB
In fact, the total size of Mylocation.org main page is 1.3 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. Javascripts take 832.7 kB which makes up the majority of the site volume.
Potential reduce by 31.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 31.6 kB or 77% of the original size.
Potential reduce by 9.3 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. My Location images are well optimized though.
Potential reduce by 505.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 505.0 kB or 61% of the original size.
Potential reduce by 21.2 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. Mylocation.org needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 78% of the original size.
Number of requests can be reduced by 32 (51%)
63
31
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Location. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
mylocation.org
111 ms
jquery-ui-1.10.3.custom.min.css
34 ms
main.min.css
61 ms
jquery-1.8.2.min.js
107 ms
jquery-ui-1.10.3.custom.min.js
101 ms
geoPosition.min.js
63 ms
common.min.js
64 ms
main.min.js
63 ms
show_ads.js
6 ms
adsbygoogle.js
14 ms
ir
239 ms
ca-pub-3759852878453234.js
259 ms
zrt_lookup.html
250 ms
show_ads_impl.js
131 ms
piwik.js
344 ms
js
178 ms
logo.png
150 ms
mapbg.png
151 ms
pic.jpg
203 ms
ui-bg_diagonals-small_50_93c3cd_40x40.png
151 ms
ui-bg_flat_75_ffffff_40x100.png
150 ms
ui-bg_diagonals-small_40_db4865_40x40.png
149 ms
ui-icons_ffffff_256x240.png
201 ms
social-icons.png
202 ms
ads
276 ms
osd.js
72 ms
ads
272 ms
common.js
13 ms
map.js
69 ms
util.js
68 ms
marker.js
70 ms
StaticMapService.GetMapImage
193 ms
onion.js
104 ms
openhand_8_8.cur
89 ms
6179071417667143862
93 ms
abg.js
171 ms
m_js_controller.js
183 ms
googlelogo_color_112x36dp.png
309 ms
ViewportInfoService.GetViewportInfo
209 ms
stats.js
56 ms
controls.js
47 ms
spotlight-poi.png
213 ms
css
167 ms
s
128 ms
x_button_blue2.png
127 ms
transparent.png
145 ms
favicon
153 ms
nessie_icon_thin_arrow_big_white.png
70 ms
google4.png
74 ms
mapcnt6.png
73 ms
sv5.png
75 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
28 ms
tmapctrl.png
82 ms
cb_scout5.png
86 ms
tmapctrl4.png
83 ms
imgs8.png
84 ms
vt
67 ms
vt
60 ms
vt
61 ms
vt
61 ms
vt
66 ms
vt
64 ms
vt
58 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
58 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
57 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
95 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
95 ms
AuthenticationService.Authenticate
16 ms
iy3g62we17qmype9
103 ms
mylocation.org 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
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
<frame> or <iframe> elements do not have a title
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
mylocation.org 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
mylocation.org 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mylocation.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Mylocation.org 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.
mylocation.org
Open Graph data is detected on the main page of My Location. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: