6.2 sec in total
217 ms
5.3 sec
701 ms
Click here to check amazing Geolive content for France. Otherwise, check out these important facts you probably never knew about geolive.mobi
You want to track a Mobile Phone? Geolive.mobi Displays the exact location of your Lost or Stolen Phone anywhere in the world.
Visit geolive.mobiWe analyzed Geolive.mobi page load time and found that the first response time was 217 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
geolive.mobi performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value6.0 s
13/100
25%
Value3.9 s
83/100
10%
Value550 ms
54/100
30%
Value0.472
18/100
15%
Value9.0 s
34/100
10%
217 ms
422 ms
220 ms
562 ms
396 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 75% of them (60 requests) were addressed to the original Geolive.mobi, 8% (6 requests) were made to Cdnjs.cloudflare.com and 4% (3 requests) were made to Fullstory.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Geolive.mobi.
Page size can be reduced by 338.4 kB (16%)
2.2 MB
1.8 MB
In fact, the total size of Geolive.mobi main page is 2.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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 124.9 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 124.9 kB or 84% of the original size.
Potential reduce by 213.4 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. Obviously, Geolive needs image optimization as it can save up to 213.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 67 B
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.
Number of requests can be reduced by 35 (48%)
73
38
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geolive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
geolive.mobi
217 ms
geolive.mobi
422 ms
en
220 ms
index.css
562 ms
logo-empty.png
396 ms
ic-pin.svg
395 ms
icon-all-phones.png
403 ms
ic-all-network.png
387 ms
ic-anonymous.png
482 ms
features-graphic-element-1.png
773 ms
features-graphic-element-2.png
795 ms
features-graphic-element-3.png
837 ms
features-graphic-element-4.png
896 ms
features-graphic.png
1049 ms
features-graphic-element-5.png
1048 ms
features-graphic-element-6.png
1219 ms
features-graphic-element-7.png
1110 ms
features-graphic-element-8.png
941 ms
graphic-responsive-web-ui.png
1452 ms
email-decode.min.js
943 ms
bundle.tracing.replay.min.js
41 ms
intlTelInput.css
36 ms
css
42 ms
main.css
1685 ms
jquery.min.js
44 ms
popper.min.js
52 ms
bootstrap.min.js
50 ms
intlTelInput.min.js
52 ms
modernizr.js
1312 ms
main.js
1347 ms
track.js
1500 ms
locatePopup.js
1495 ms
cookie-banner.js
1794 ms
3ds.png
1932 ms
visa.png
1933 ms
mc.svg
1907 ms
graphic-home-phone@3x.webp
1414 ms
ic-benefit-tick@3x.png
1637 ms
graphic-half-phone-how-it-works@3x.webp
1768 ms
ic-step-1@3x.png
1496 ms
ic-step-2@3x.png
1786 ms
ic-step-3@3x.png
1813 ms
ic-benefit-tick@2x.png
1827 ms
flags.png
17 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6o3mp.ttf
23 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6o3mp.ttf
28 ms
bg-header.svg
601 ms
action-btn-track.svg
790 ms
ic-48-hr.png
899 ms
ic-150-geoloc.png
930 ms
ic-gps.png
964 ms
ic-phones.png
965 ms
ic-networks.png
995 ms
ic-assistance.png
1184 ms
ic-track-real-time.png
1284 ms
ic-global-coverage.png
1313 ms
ic-price-add-user.png
1359 ms
ic-price-cloud.png
1349 ms
ic-price-msg.png
1387 ms
ic-price-add-contact.png
1567 ms
ic-price-share-location.png
1657 ms
graphic-benefits.png
1694 ms
ic-benefit-tick.png
1738 ms
ic-footer-phone.png
1762 ms
phonegreen.png
1780 ms
ic-footer-email.png
1954 ms
gtm.js
72 ms
geoip-lookup
1983 ms
graphic-home-phone@3x.png
2571 ms
graphic-half-phone-how-it-works@3x.png
2504 ms
flags.png
2150 ms
analytics.js
33 ms
bat.js
50 ms
fs.js
276 ms
collect
18 ms
collect
37 ms
js
48 ms
ga-audiences
115 ms
fs.js
21 ms
www.fullstory.com
6 ms
geolive.mobi 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
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
geolive.mobi 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
geolive.mobi SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geolive.mobi can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Geolive.mobi 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.
geolive.mobi
Open Graph description is not detected on the main page of Geolive. 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: