Tools & Wizards About Us
geoloc.be screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

geoloc.be

Geoloc.be : Mobile Phone Geolocation in only 1 minute

Page Load Speed

4.3 sec in total

First Response

312 ms

Resources Loaded

3.5 sec

Page Rendered

492 ms

geoloc.be screenshot

About Website

Visit geoloc.be now to see the best up-to-date Geoloc content and also check out these interesting facts you probably never knew about geoloc.be

You want to track a Mobile Phone? geoloc.be Displays the exact location of your Lost or Stolen Phone anywhere in the world.

Visit geoloc.be

Key Findings

We analyzed Geoloc.be page load time and found that the first response time was 312 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.

Performance Metrics

geoloc.be performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

geoloc.be

312 ms

geoloc.be

417 ms

en

224 ms

index.css

403 ms

logo-empty.svg

372 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 76% of them (38 requests) were addressed to the original Geoloc.be, 12% (6 requests) were made to Cdnjs.cloudflare.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Geoloc.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.0 kB (35%)

Content Size

267.9 kB

After Optimization

172.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Geoloc.be main page is 267.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 153.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 76.1 kB

  • Original 93.2 kB
  • After minification 93.2 kB
  • After compression 17.1 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 76.1 kB or 82% of the original size.

Image Optimization

-12%

Potential reduce by 18.8 kB

  • Original 153.7 kB
  • After minification 134.9 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, Geoloc needs image optimization as it can save up to 18.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 29 (62%)

Requests Now

47

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geoloc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

geoloc.be

geoloc.be

312 ms

geoloc.be

geoloc.be

417 ms

en

en

224 ms

index.css

index.css

403 ms

logo-empty.svg

logo-empty.svg

372 ms

ic-benefit-tick.svg

ic-benefit-tick.svg

415 ms

landing-element-1-en.png

landing-element-1-en.png

375 ms

landing-element-2-en.png

landing-element-2-en.png

456 ms

landing-element-3.png

landing-element-3.png

481 ms

howto-element.png

howto-element.png

671 ms

howto-1.svg

howto-1.svg

680 ms

step-1-bloc.png

step-1-bloc.png

712 ms

howto-2.svg

howto-2.svg

709 ms

step-2-bloc.png

step-2-bloc.png

755 ms

howto-3.svg

howto-3.svg

753 ms

howto-ping.svg

howto-ping.svg

1069 ms

step-3-bloc.png

step-3-bloc.png

1067 ms

step-3-tick.png

step-3-tick.png

1093 ms

graphic-easier-than-ever-en.webp

graphic-easier-than-ever-en.webp

1108 ms

bundle.tracing.replay.min.js

bundle.tracing.replay.min.js

52 ms

intlTelInput.css

intlTelInput.css

42 ms

css

css

44 ms

main.css

main.css

1480 ms

jquery.min.js

jquery.min.js

54 ms

popper.min.js

popper.min.js

57 ms

bootstrap.min.js

bootstrap.min.js

63 ms

intlTelInput.min.js

intlTelInput.min.js

57 ms

modernizr.js

modernizr.js

1151 ms

main.js

main.js

1456 ms

track.js

track.js

1456 ms

cookie-banner.js

cookie-banner.js

1567 ms

review-user-1.png

review-user-1.png

1593 ms

4-stars.png

4-stars.png

1572 ms

quote-purple.svg

quote-purple.svg

1572 ms

5-stars.png

5-stars.png

1852 ms

quote-white.svg

quote-white.svg

1859 ms

review-user-2.png

review-user-2.png

1681 ms

review-user-3.png

review-user-3.png

2011 ms

graphic-cb-mastercard-visa-ssl.png

graphic-cb-mastercard-visa-ssl.png

2050 ms

bg-header.webp

bg-header.webp

461 ms

action-btn-track.svg

action-btn-track.svg

542 ms

ic-48-hr.svg

ic-48-hr.svg

699 ms

ic-benefits-tick.png

ic-benefits-tick.png

726 ms

gtm.js

gtm.js

68 ms

geoip-lookup

geoip-lookup

811 ms

flags.webp

flags.webp

977 ms

js

js

52 ms

analytics.js

analytics.js

24 ms

collect

collect

45 ms

utils.js

utils.js

11 ms

Accessibility Review

geoloc.be accessibility score

73

Accessibility Issues

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

High

[role]s do not have all required [aria-*] attributes

High

[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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

geoloc.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

geoloc.be SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geoloc.be 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 Geoloc.be 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.

Social Sharing Optimization

geoloc.be

Open Graph description is not detected on the main page of Geoloc. 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: