Tools & Wizards About Us
gci.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gci.net

GCI.com | Mobile, Internet, and TV on Alaska's Most Advanced Network

Page Load Speed

4.3 sec in total

First Response

338 ms

Resources Loaded

3.6 sec

Page Rendered

312 ms

gci.net screenshot

About Website

Click here to check amazing GCI content for United States. Otherwise, check out these important facts you probably never knew about gci.net

Get Alaska's best internet and mobile with plans from GCI. Whether you're in a rural village or in an urban city, GCI delivers connectivity in your area.

Visit gci.net

Key Findings

We analyzed Gci.net page load time and found that the first response time was 338 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Gci.net rating and web reputation

Performance Metrics

gci.net performance score

0

Network Requests Diagram

gci.net

338 ms

www.gci.com

327 ms

www.gci.com

1058 ms

VisitorIdentification.js

237 ms

bootstrap

757 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gci.net, 73% (40 requests) were made to Gci.com and 9% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Gci.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 407.7 kB (13%)

Content Size

3.2 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gci.net main page is 3.2 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 60.7 kB

  • Original 76.9 kB
  • After minification 60.7 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 16.2 kB, which is 21% 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 60.7 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 90.5 kB

  • Original 2.8 MB
  • After minification 2.7 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. GCI images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 229.0 kB

  • Original 355.0 kB
  • After minification 336.0 kB
  • After compression 126.0 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 229.0 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 27.4 kB

  • Original 33.8 kB
  • After minification 26.5 kB
  • After compression 6.4 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. Gci.net needs all CSS files to be minified and compressed as it can save up to 27.4 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

46

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gci.net

gci.net

338 ms

www.gci.com

www.gci.com

327 ms

www.gci.com

www.gci.com

1058 ms

VisitorIdentification.js

VisitorIdentification.js

237 ms

bootstrap

bootstrap

757 ms

global

global

847 ms

headscripts

headscripts

397 ms

recaptcha.js

recaptcha.js

382 ms

foresee-trigger.js

foresee-trigger.js

423 ms

jquery_ie8

jquery_ie8

412 ms

jquerydependent

jquerydependent

698 ms

jquerydependent2

jquerydependent2

811 ms

jqueryval

jqueryval

444 ms

global

global

564 ms

api.js

api.js

63 ms

Cart-icon.png

Cart-icon.png

133 ms

magglass.png

magglass.png

140 ms

magglass_big.png

magglass_big.png

138 ms

gci.png

gci.png

133 ms

16_02_wireless_hero_s7preorder.jpg

16_02_wireless_hero_s7preorder.jpg

138 ms

16_01_hp_hero_epic.jpg

16_01_hp_hero_epic.jpg

395 ms

15_08_hp_hero_dumpdish.jpg

15_08_hp_hero_dumpdish.jpg

391 ms

16_02_hp_brandmodule_aha.jpg

16_02_hp_brandmodule_aha.jpg

723 ms

16_02_hp_p1_breakuphappiness.jpg

16_02_hp_p1_breakuphappiness.jpg

473 ms

15_10_hppromo_attswitch.jpg

15_10_hppromo_attswitch.jpg

623 ms

15_09_hp_promo_noworries.jpg

15_09_hp_promo_noworries.jpg

260 ms

16_01_hp_p1_akfuture.jpg

16_01_hp_p1_akfuture.jpg

354 ms

16_02_hp_community_iron_dog.jpg

16_02_hp_community_iron_dog.jpg

692 ms

redbar.png

redbar.png

584 ms

social_fb.png

social_fb.png

493 ms

social_instagram.png

social_instagram.png

577 ms

social_linkedin.png

social_linkedin.png

597 ms

social_twitter.png

social_twitter.png

685 ms

social_youtube.png

social_youtube.png

689 ms

footerback.jpg

footerback.jpg

750 ms

Gotham-Book-webfont.woff

Gotham-Book-webfont.woff

714 ms

Gotham-Medium-webfont.woff

Gotham-Medium-webfont.woff

871 ms

Gotham-Bold-webfont.woff

Gotham-Bold-webfont.woff

1020 ms

dc.js

dc.js

88 ms

loading-2.gif

loading-2.gif

647 ms

light-skin-1.png

light-skin-1.png

732 ms

recaptcha__en.js

recaptcha__en.js

76 ms

foresee-surveydef.js

foresee-surveydef.js

688 ms

__utm.gif

__utm.gif

11 ms

fallback

fallback

33 ms

fallback__ltr.css

fallback__ltr.css

10 ms

payload

payload

35 ms

css

css

60 ms

logo_48.png

logo_48.png

11 ms

refresh.png

refresh.png

16 ms

audio.png

audio.png

25 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

54 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

59 ms

foresee-dhtml.css

foresee-dhtml.css

112 ms

nr-852.min.js

nr-852.min.js

49 ms

SEO Factors

gci.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

gci.net

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