Tools & Wizards About Us
geomium.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

geomium.com

Trusted IP Data Provider, from IPv6 to IPv4 - IPinfo.io

Page Load Speed

1.8 sec in total

First Response

16 ms

Resources Loaded

445 ms

Page Rendered

1.4 sec

geomium.com screenshot

About Website

Click here to check amazing Geomium content. Otherwise, check out these important facts you probably never knew about geomium.com

Get accurate IP address information with IPinfo. Trusted by 400,000+ users, we handle more than 40 billion API requests monthly. Sign up for free account today.

Visit geomium.com

Key Findings

We analyzed Geomium.com page load time and found that the first response time was 16 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.

Performance Metrics

geomium.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value1,640 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

geomium.com

16 ms

57 ms

ipinfo.io

109 ms

a8055e9335eef9a7.css

44 ms

bc888e06ecc898de.css

55 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Geomium.com, 84% (59 requests) were made to Website-cdn.ipinfo.io and 6% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (197 ms) relates to the external source G2.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.2 kB (10%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geomium.com main page is 1.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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 70.1 kB

  • Original 81.2 kB
  • After minification 79.6 kB
  • After compression 11.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 70.1 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 8.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. Geomium images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 138 B

  • Original 239.5 kB
  • After minification 239.5 kB
  • After compression 239.4 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.

CSS Optimization

-89%

Potential reduce by 85.7 kB

  • Original 96.3 kB
  • After minification 45.5 kB
  • After compression 10.5 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. Geomium.com needs all CSS files to be minified and compressed as it can save up to 85.7 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (33%)

Requests Now

63

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geomium.com

geomium.com

16 ms

57 ms

ipinfo.io

ipinfo.io

109 ms

a8055e9335eef9a7.css

a8055e9335eef9a7.css

44 ms

bc888e06ecc898de.css

bc888e06ecc898de.css

55 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

115 ms

webpack-cef9611ae7193a4d.js

webpack-cef9611ae7193a4d.js

90 ms

framework-ca706bf673a13738.js

framework-ca706bf673a13738.js

69 ms

main-77d4cfbedce327d5.js

main-77d4cfbedce327d5.js

99 ms

_app-eed0fa88db18900a.js

_app-eed0fa88db18900a.js

89 ms

3159-64d68b7ceaf483da.js

3159-64d68b7ceaf483da.js

70 ms

6513-84146beb0c54932a.js

6513-84146beb0c54932a.js

69 ms

index-d3fa3da94d0e7091.js

index-d3fa3da94d0e7091.js

70 ms

_buildManifest.js

_buildManifest.js

69 ms

_ssgManifest.js

_ssgManifest.js

71 ms

p.css

p.css

50 ms

stars

stars

197 ms

7cd654c7533ce5d2d550ac86472a835b.svg

7cd654c7533ce5d2d550ac86472a835b.svg

24 ms

logo-positive.0a4ba892.svg

logo-positive.0a4ba892.svg

62 ms

icon-menu.bfaebce7.svg

icon-menu.bfaebce7.svg

63 ms

mobile.b3d06ccc.svg

mobile.b3d06ccc.svg

69 ms

geolocation-small.0037d36c.svg

geolocation-small.0037d36c.svg

65 ms

ranges-small.fd2dafde.svg

ranges-small.fd2dafde.svg

71 ms

privacy-small.854788a7.svg

privacy-small.854788a7.svg

73 ms

company-small.e5cfbec7.svg

company-small.e5cfbec7.svg

127 ms

asn-small.77f95094.svg

asn-small.77f95094.svg

74 ms

domains-small.249bd466.svg

domains-small.249bd466.svg

77 ms

carrier-small.6d72c73d.svg

carrier-small.6d72c73d.svg

133 ms

abuse-small.ef56e2d8.svg

abuse-small.ef56e2d8.svg

125 ms

whois-small.7868d282.svg

whois-small.7868d282.svg

134 ms

ipinfo-main-illustration.9e5f5329.svg

ipinfo-main-illustration.9e5f5329.svg

135 ms

logo-plesk-white.5276a2d7.svg

logo-plesk-white.5276a2d7.svg

138 ms

photo-plesk-jan.c2acc0e6.jpeg

photo-plesk-jan.c2acc0e6.jpeg

152 ms

logo-clearbit-white.dedf4224.svg

logo-clearbit-white.dedf4224.svg

127 ms

photo-clearbit-alex.70fcf481.jpeg

photo-clearbit-alex.70fcf481.jpeg

129 ms

logo-npm-white.37bc2bf6.svg

logo-npm-white.37bc2bf6.svg

130 ms

photo-npm-laurie.30cd3e0e.jpeg

photo-npm-laurie.30cd3e0e.jpeg

132 ms

web_personalization.f1019e7f.jpg

web_personalization.f1019e7f.jpg

156 ms

account_based_marketing.9bc49e59.jpg

account_based_marketing.9bc49e59.jpg

135 ms

adtech.89423493.jpg

adtech.89423493.jpg

138 ms

cyber_security.ad089de5.jpg

cyber_security.ad089de5.jpg

168 ms

data_enrichment.0cc4e0c0.jpg

data_enrichment.0cc4e0c0.jpg

135 ms

e-commerce.2456b237.jpg

e-commerce.2456b237.jpg

109 ms

d

d

36 ms

d

d

147 ms

d

d

78 ms

d

d

73 ms

financial_technology.5e76b3bb.jpg

financial_technology.5e76b3bb.jpg

111 ms

gametech.f84282a7.jpg

gametech.f84282a7.jpg

96 ms

government.e7b74c52.jpg

government.e7b74c52.jpg

95 ms

telecommunication.92da052b.jpg

telecommunication.92da052b.jpg

96 ms

traveltech.e83cda25.jpg

traveltech.e83cda25.jpg

96 ms

zapier.a1a375f4.svg

zapier.a1a375f4.svg

119 ms

snowflake.7608b7c5.svg

snowflake.7608b7c5.svg

157 ms

wordpress.dd4ede2f.svg

wordpress.dd4ede2f.svg

93 ms

maltego.5d28177b.svg

maltego.5d28177b.svg

94 ms

splunk.a71e22c9.svg

splunk.a71e22c9.svg

94 ms

paloalto.0919c3d7.svg

paloalto.0919c3d7.svg

109 ms

heroku.7b181a55.svg

heroku.7b181a55.svg

139 ms

polarity.4a5a200c.svg

polarity.4a5a200c.svg

138 ms

api-access.d4d3b4b8.svg

api-access.d4d3b4b8.svg

122 ms

blue_check.d118dbca.svg

blue_check.d118dbca.svg

133 ms

database-download-small.053da0c0.svg

database-download-small.053da0c0.svg

105 ms

discourse-light.91b917f1.svg

discourse-light.91b917f1.svg

107 ms

5.0.png

5.0.png

46 ms

linkedin-light.c8869563.svg

linkedin-light.c8869563.svg

103 ms

github-light.9781e033.svg

github-light.9781e033.svg

65 ms

twitter-light.c8dff709.svg

twitter-light.c8dff709.svg

68 ms

youtube-light.cf5a6d38.svg

youtube-light.cf5a6d38.svg

70 ms

facebook-light.0be4f2a5.svg

facebook-light.0be4f2a5.svg

129 ms

Accessibility Review

geomium.com accessibility score

74

Accessibility Issues

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

Form elements do not have associated labels

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

geomium.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

geomium.com 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

High

Tap targets are not sized appropriately

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 Geomium.com 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 Geomium.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.

Social Sharing Optimization

geomium.com

Open Graph data is detected on the main page of Geomium. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: