Tools & Wizards About Us
ip-api.com screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

ip-api.com

IP-API.com - Geolocation API

Page Load Speed

928 ms in total

First Response

21 ms

Resources Loaded

627 ms

Page Rendered

280 ms

ip-api.com screenshot

About Website

Welcome to ip-api.com homepage info - get ready to check IP API best content for India right away, or after learning these important things about ip-api.com

Free IP Geolocation API - lookup any IP address

Visit ip-api.com

Key Findings

We analyzed Ip-api.com page load time and found that the first response time was 21 ms and then it took 907 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

ip-api.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

ip-api.com

21 ms

page.css

4 ms

logo.png

21 ms

bg.jpg

22 ms

json

484 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 79% of them (11 requests) were addressed to the original Ip-api.com, 7% (1 request) were made to Jl8lcxkg184ep48k6r345tb5b9u1700g.edns.ip-api.com and 7% (1 request) were made to Demo.ip-api.com. The less responsive or slowest element that took the longest time to load (509 ms) relates to the external source Cache.ip-api.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.4 kB (9%)

Content Size

125.5 kB

After Optimization

114.1 kB

  • HTML
  • Images

In fact, the total size of Ip-api.com main page is 125.5 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. 20% of websites need less resources to load. Images take 113.5 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 7.9 kB

  • Original 12.1 kB
  • After minification 12.1 kB
  • After compression 4.2 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 7.9 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 3.6 kB

  • Original 113.5 kB
  • After minification 109.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. IP API images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • AJAX
  • Images
  • CSS

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IP API. According to our analytics all requests are already optimized.

Network Requests Diagram

ip-api.com

ip-api.com

21 ms

page.css

page.css

4 ms

logo.png

logo.png

21 ms

bg.jpg

bg.jpg

22 ms

json

json

484 ms

69 ms

open-sans-v16-latin-300.woff

open-sans-v16-latin-300.woff

4 ms

open-sans-v16-latin-regular.woff

open-sans-v16-latin-regular.woff

7 ms

open-sans-v16-latin-600.woff

open-sans-v16-latin-600.woff

7 ms

dosis-v8-latin-500.woff

dosis-v8-latin-500.woff

7 ms

dosis-v8-latin-regular.woff

dosis-v8-latin-regular.woff

7 ms

dosis-v8-latin-200.woff

dosis-v8-latin-200.woff

9 ms

dosis-v8-latin-600.woff

dosis-v8-latin-600.woff

9 ms

-77.4874,39.0438,10

-77.4874,39.0438,10

509 ms

Accessibility Review

ip-api.com accessibility score

93

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

ip-api.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

ip-api.com SEO score

95

Search Engine Optimization Advices

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 Ip-api.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 Ip-api.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

ip-api.com

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