Tools & Wizards About Us
thinkgeo.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

thinkgeo.com

ThinkGeo, GIS Mapping Made Easy

Page Load Speed

1.1 sec in total

First Response

73 ms

Resources Loaded

782 ms

Page Rendered

290 ms

thinkgeo.com screenshot

About Website

Click here to check amazing Think Geo content for Indonesia. Otherwise, check out these important facts you probably never knew about thinkgeo.com

We are a GIS software company offering quick and powerful cloud, mobile, web and desktop mapping solutions. Our clients are in more than 40 industries including agriculture, energy, transportation, go...

Visit thinkgeo.com

Key Findings

We analyzed Thinkgeo.com page load time and found that the first response time was 73 ms and then it took 1.1 sec 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

thinkgeo.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

thinkgeo.com

73 ms

25QiNzfo0iXeduYk860eXPmsnimeDcHNw1hpEv4cmpMfe0q2fFHN4UJLFRbh52jhWDm8wDS3FejU5eIawhmcwhwtwA485e9aZsnEMKG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdP37O1sG-AonZhmzZemldkoDSWmyScmDSeBRZPoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CdeNRjAUGdaFXOYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCieyTdcl1ZAv0jhNlOYsG-AonZhmzZemldkoDSWmyScmDSeBRZPoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWw0dA9CiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaO1sG-AonZhmzOcFzdPUaiaS0ieyTdcl1ZANqZAuzO1FUiABkZWF3jAF8OcFzdPJ--WsROABhjAoXOAiyScs8OAizieyTjku3Scv7f6KXC3JbMg62JMJ7f6KuC3JbMg6BJMJ7f6KDC3JbMg6YJMHbMiV_3L9B.js

80 ms

legacy.js

146 ms

modern.js

222 ms

extract-css-runtime-57b3a735eff7ee71b8d6-min.en-US.js

219 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Thinkgeo.com, 31% (10 requests) were made to Assets.squarespace.com and 22% (7 requests) were made to Images.squarespace-cdn.com. The less responsive or slowest element that took the longest time to load (524 ms) relates to the external source Images.squarespace-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.4 kB (8%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thinkgeo.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 173.6 kB

  • Original 199.2 kB
  • After minification 166.1 kB
  • After compression 25.5 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. This page needs HTML code to be minified as it can gain 33.1 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 173.6 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 3.0 kB

  • Original 993.3 kB
  • After minification 990.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. Think Geo images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.6 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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

-1%

Potential reduce by 140 B

  • Original 15.6 kB
  • After minification 15.6 kB
  • After compression 15.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. Thinkgeo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (54%)

Requests Now

28

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thinkgeo.com

thinkgeo.com

73 ms

25QiNzfo0iXeduYk860eXPmsnimeDcHNw1hpEv4cmpMfe0q2fFHN4UJLFRbh52jhWDm8wDS3FejU5eIawhmcwhwtwA485e9aZsnEMKG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdP37O1sG-AonZhmzZemldkoDSWmyScmDSeBRZPoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CdeNRjAUGdaFXOYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCieyTdcl1ZAv0jhNlOYsG-AonZhmzZemldkoDSWmyScmDSeBRZPoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWw0dA9CiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaO1sG-AonZhmzOcFzdPUaiaS0ieyTdcl1ZANqZAuzO1FUiABkZWF3jAF8OcFzdPJ--WsROABhjAoXOAiyScs8OAizieyTjku3Scv7f6KXC3JbMg62JMJ7f6KuC3JbMg6BJMJ7f6KDC3JbMg6YJMHbMiV_3L9B.js

25QiNzfo0iXeduYk860eXPmsnimeDcHNw1hpEv4cmpMfe0q2fFHN4UJLFRbh52jhWDm8wDS3FejU5eIawhmcwhwtwA485e9aZsnEMKG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdP37O1sG-AonZhmzZemldkoDSWmyScmDSeBRZPoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CdeNRjAUGdaFXOYFUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCieyTdcl1ZAv0jhNlOYsG-AonZhmzZemldkoDSWmyScmDSeBRZPoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1Oco8ifUaiaS0jWw0dA9CiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaO1sG-AonZhmzOcFzdPUaiaS0ieyTdcl1ZANqZAuzO1FUiABkZWF3jAF8OcFzdPJ--WsROABhjAoXOAiyScs8OAizieyTjku3Scv7f6KXC3JbMg62JMJ7f6KuC3JbMg6BJMJ7f6KDC3JbMg6YJMHbMiV_3L9B.js

80 ms

legacy.js

legacy.js

146 ms

modern.js

modern.js

222 ms

extract-css-runtime-57b3a735eff7ee71b8d6-min.en-US.js

extract-css-runtime-57b3a735eff7ee71b8d6-min.en-US.js

219 ms

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

221 ms

cldr-resource-pack-e94539391642d3b99900-min.en-US.js

cldr-resource-pack-e94539391642d3b99900-min.en-US.js

219 ms

common-vendors-stable-4a7e52840bc34052dfdc-min.en-US.js

common-vendors-stable-4a7e52840bc34052dfdc-min.en-US.js

238 ms

common-vendors-86bbdb120aef73a4474d-min.en-US.js

common-vendors-86bbdb120aef73a4474d-min.en-US.js

297 ms

common-42f0b0cfaa5e6f13ccce-min.en-US.js

common-42f0b0cfaa5e6f13ccce-min.en-US.js

389 ms

performance-db4af166b7e3b954c247-min.en-US.js

performance-db4af166b7e3b954c247-min.en-US.js

313 ms

site.css

site.css

88 ms

js

js

214 ms

js

js

295 ms

static.css

static.css

142 ms

site-bundle.d000490d56799ef0c7f535a69682ca3c.js

site-bundle.d000490d56799ef0c7f535a69682ca3c.js

211 ms

thinkgeo-logo.png

thinkgeo-logo.png

237 ms

GIS+map+of+the+world+rendered+using+WPF

GIS+map+of+the+world+rendered+using+WPF

506 ms

routing-optimization-mobile.png

routing-optimization-mobile.png

502 ms

GIS+map+showing+COVID+virus+using+dot+density+style

GIS+map+showing+COVID+virus+using+dot+density+style

524 ms

consulting-stylejson-editor.png

consulting-stylejson-editor.png

465 ms

customers.png

customers.png

501 ms

new-map-berlin-zoo.webp

new-map-berlin-zoo.webp

485 ms

thinkgeo-logo.png

thinkgeo-logo.png

180 ms

js

js

234 ms

js

js

189 ms

analytics.js

analytics.js

243 ms

icon-searchqueries-20-light.png

icon-searchqueries-20-light.png

13 ms

d

d

83 ms

d

d

120 ms

d

d

119 ms

collect

collect

24 ms

Accessibility Review

thinkgeo.com accessibility score

88

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

Links do not have a discernible name

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

thinkgeo.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

thinkgeo.com SEO score

91

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 Thinkgeo.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 Thinkgeo.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

thinkgeo.com

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