Tools & Wizards About Us
geosage.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

geosage.com

Mapping our land more clearly and colourfully

Page Load Speed

587 ms in total

First Response

44 ms

Resources Loaded

216 ms

Page Rendered

327 ms

geosage.com screenshot

About Website

Click here to check amazing Geosage content for United States. Otherwise, check out these important facts you probably never knew about geosage.com

Visit geosage.com

Key Findings

We analyzed Geosage.com page load time and found that the first response time was 44 ms and then it took 543 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

geosage.com performance score

0

Network Requests Diagram

geosage.com

44 ms

3col_leftNav.css

3 ms

buttons.js

7 ms

background_v1.gif

92 ms

getAllAppDefault.esi

69 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 85% of them (17 requests) were addressed to the original Geosage.com, 10% (2 requests) were made to W.sharethis.com and 5% (1 request) were made to Wd-edge.sharethis.com. The less responsive or slowest element that took the longest time to load (92 ms) belongs to the original domain Geosage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.8 kB (48%)

Content Size

312.8 kB

After Optimization

164.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geosage.com main page is 312.8 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. Javascripts take 148.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 24.3 kB

  • Original 29.6 kB
  • After minification 18.5 kB
  • After compression 5.3 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 11.1 kB, which is 37% 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 24.3 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 5.9 kB

  • Original 129.5 kB
  • After minification 123.6 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. Geosage images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 114.4 kB

  • Original 148.7 kB
  • After minification 148.6 kB
  • After compression 34.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 114.4 kB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 4.3 kB

  • Original 5.2 kB
  • After minification 3.0 kB
  • After compression 881 B

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. Geosage.com needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

geosage.com

geosage.com

44 ms

3col_leftNav.css

3col_leftNav.css

3 ms

buttons.js

buttons.js

7 ms

background_v1.gif

background_v1.gif

92 ms

getAllAppDefault.esi

getAllAppDefault.esi

69 ms

Header1.jpg

Header1.jpg

12 ms

geosage.gif

geosage.gif

12 ms

els2000_banner_top.gif

els2000_banner_top.gif

11 ms

landsat_8_ov1.jpg

landsat_8_ov1.jpg

12 ms

Korea_Peninsula_Mosaics_ov_V1.jpg

Korea_Peninsula_Mosaics_ov_V1.jpg

12 ms

basemaps_ov1.jpg

basemaps_ov1.jpg

13 ms

NAIP_RGB_Overview_V1_Small.jpg

NAIP_RGB_Overview_V1_Small.jpg

18 ms

els2000-banner-left-no-title.jpg

els2000-banner-left-no-title.jpg

13 ms

srtm90m_hillshading_ov_small.jpg

srtm90m_hillshading_ov_small.jpg

11 ms

sentinel-2_resized.jpg

sentinel-2_resized.jpg

11 ms

landsat_8_resized.jpg

landsat_8_resized.jpg

12 ms

page1_p11.jpg

page1_p11.jpg

9 ms

page1_p33.jpg

page1_p33.jpg

11 ms

page1_p44.jpg

page1_p44.jpg

11 ms

twitter_counter.png

twitter_counter.png

12 ms

SEO Factors

geosage.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geosage.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Geosage.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

geosage.com

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