Tools & Wizards About Us
citrix.glhec.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

citrix.glhec.org

Netscaler Gateway

Page Load Speed

2.4 sec in total

First Response

267 ms

Resources Loaded

1.9 sec

Page Rendered

197 ms

citrix.glhec.org screenshot

About Website

Visit citrix.glhec.org now to see the best up-to-date Citrix Glhec content for United States and also check out these interesting facts you probably never knew about citrix.glhec.org

Visit citrix.glhec.org

Key Findings

We analyzed Citrix.glhec.org page load time and found that the first response time was 267 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

citrix.glhec.org performance score

0

Network Requests Diagram

citrix.glhec.org

267 ms

citrix.glhec.org

189 ms

index.html

106 ms

rdx.css

97 ms

base.css

167 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that all of those requests were addressed to Citrix.glhec.org and no external sources were called. The less responsive or slowest element that took the longest time to load (447 ms) belongs to the original domain Citrix.glhec.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (74%)

Content Size

3.0 MB

After Optimization

774.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Citrix.glhec.org main page is 3.0 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. 20% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 4.6 kB

  • Original 6.8 kB
  • After minification 6.6 kB
  • After compression 2.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 4.6 kB or 67% of the original size.

Image Optimization

-2%

Potential reduce by 2.1 kB

  • Original 132.5 kB
  • After minification 130.5 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. Citrix Glhec images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 1.9 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 578.9 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 1.9 MB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 310.0 kB

  • Original 373.0 kB
  • After minification 358.9 kB
  • After compression 63.1 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. Citrix.glhec.org needs all CSS files to be minified and compressed as it can save up to 310.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (64%)

Requests Now

14

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

citrix.glhec.org

citrix.glhec.org

267 ms

citrix.glhec.org

citrix.glhec.org

189 ms

index.html

index.html

106 ms

rdx.css

rdx.css

97 ms

base.css

base.css

167 ms

citrix-fonts.css

citrix-fonts.css

125 ms

custom.css

custom.css

124 ms

rdx.js

rdx.js

447 ms

login.js

login.js

122 ms

views.js

views.js

129 ms

gateway_login_view.js

gateway_login_view.js

137 ms

gateway_login_form_view.js

gateway_login_form_view.js

137 ms

resources.js

resources.js

173 ms

nsshare.js

nsshare.js

161 ms

bg_bubbles.jpg

bg_bubbles.jpg

97 ms

in_progress.gif

in_progress.gif

34 ms

header_gradient.png

header_gradient.png

35 ms

ns_gateway_logo_center.png

ns_gateway_logo_center.png

34 ms

Button_LogOn_idle.png

Button_LogOn_idle.png

34 ms

header_overlay_square_pattern.png

header_overlay_square_pattern.png

35 ms

SEO Factors

citrix.glhec.org 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 Citrix.glhec.org 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 Citrix.glhec.org 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

citrix.glhec.org

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