Analyze

gsb.stanford.edu: Stanford Graduate School of Business | Change lives. Change organizations. Change the world.

Change lives. Change organizations. Change the world.

Page load speed analysis

  • 58/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    248 ms

  • Resources loaded

    6.2 sec

  • Page rendered

    317 ms

  • Total page load time

    6.8 sec

Visit gsb.stanford.edu now to see the best up-to-date Gsb Stanford content for United States and also check out these interesting facts you probably never knew about gsb.stanford.edu

We analyzed Gsb.stanford.edu page load time and found that the first response time was 248 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Page optimization

  • HTML 101.6 kB
    Images 3.5 MB
    Javascripts 449.0 kB
    CSS 882.4 kB

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

    • Original 101.6 kB
    • After minification 98.0 kB
    • After compression 16.2 kB

    HTML optimization

    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 85.3 kB or 84% of the original size.

    • Original 3.5 MB
    • After optimization 3.5 MB

    Image optimization

    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. Gsb Stanford images are well optimized though.

    • Original 449.0 kB
    • After minification 371.8 kB
    • After compression 124.9 kB

    JavaScript optimization

    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 324.0 kB or 72% of the original size.

    • Original 882.4 kB
    • After minification 873.5 kB
    • After compression 90.0 kB

    CSS optimization

    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. Gsb.stanford.edu needs all CSS files to be minified and compressed as it can save up to 792.4 kB or 90% of the original size.

Network requests diagram

  • gsb.stanford.edu
  • www.gsb.stanford.edu
  • css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
  • css_qCCuq_8nLoouMQeLizR_e8g0dwBEfjrnYwV_AgVv2RU.css
  • css_bD94bVCRBj4zzv_lSfb-pZ4t4YRcBNajOjrHafBFb3Y.css
  • css_YTivQCTt7Eg-ubvGArSP10YEknGEEMFMwhsAdvB2ddQ.css
  • css_O1DpxmVbNcFRc_bfEvTvhrL-pevxawisj1BshJ30dJ8.css
  • jquery.min.js
  • jquery.once.js
  • drupal.js
  • jquery.flexslider-min.js
  • gsb_feature_slideshow_fpp.flexslider.js
  • gsb_tweetfeed.js
  • ajax.js
  • jquery_update.js
  • caption-filter.js
  • alumni_cas_auth.js
  • fancybox.js
  • jquery.fancybox.pack.js
  • jquery.mousewheel-3.0.6.pack.js
  • gsb_filter_with_states.js
  • progress.js
  • field_group.js
  • gsb_feature_social_feed.js
  • gsb_feature_academic_calendar_display.js
  • jquery.sharrre.js
  • responsive-tables.js
  • menu_minipanels.callbacks.js
  • gsb_forms.js
  • modernizr.custom.86301.js
  • custom.js
  • responsive-menu.js
  • ios-orientationchange-fix.js
  • show-more-less.js
  • jquery.customSelect.min.js
  • search.js
  • jquery.mmenu.min.all.js
  • jquery.mmenu.offcanvas.min.js
  • blast-attribution-cookie.js
  • menu_minipanels.js
  • jquery.qtip-1.0.0-rc3.min.js
  • megamenu_styles.js
  • logo-print.jpg
  • photo-slideshow-ignite-vets-0216.jpg
  • photo-slideshow-ignite-full-time-0216_0.jpg
  • photo-slideshow-berg-creative-ideas-0116.jpg
  • photo-sideshow-larcker-runs-sv-boards-0116.jpg
  • photo-slideshow-politics-candidates-cater-0216.jpg
  • photo-image-cta-lead-corp-innovation-1114.jpg
  • gtm.js
  • search.svg
  • logo.svg
  • bg-quad-home-2015-05-26-1.png
  • bg-event-cal-2015-08-21-1.jpg
  • bg-social-feed-2015-05-26-1.png
  • gfsf_user_timeline
  • 236F40_0_0.woff
  • 236F40_2_0.woff
  • 236F40_C_0.woff
  • icons.svg
  • icons.woff
  • analytics.js
  • roundtrip.js
  • fbevents.js
  • mentad-visit-notification.js
  • visit.js
  • linkid.js
  • collect
  • collect
  • collect
  • collect
  • KVSUBOBXFFB35IC6HV2VCZ.js
  • api.js
  • www.gsb.stanford.edu
  • out
  • tr
  • out
  • out
  • out
  • out
  • out
  • out
  • out
  • u.php
  • sync
  • adsct
  • pixel
  • 377928.gif
  • sd
  • pixel
  • in

Our browser made a total of 95 requests to load all elements on the main page. We found that 64% of them (61 requests) were addressed to the original Gsb.stanford.edu, 9% (9 requests) were made to D.adroll.com and 4% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Gsb.stanford.edu.

Additional info on gsb.stanford.edu

Requests

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

44

Javascripts

25

Images

5

CSS

6

AJAX

80

All

Possible request optimization

1

Javascripts

14

Images

1

CSS

6

AJAX

58

Optimized

22

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://www.gsb.stanford.edu/ before it reached this domain.

IP address

Gsb.stanford.edu uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

DNS records

Type Host Target/ip TTL Other
A

gsb.stanford.edu

171.67.37.93 1800
MX

gsb.stanford.edu

mxa-00000d03.gslb.pphosted.com 1800 Pri: 10
MX

gsb.stanford.edu

mxb-00000d03.gslb.pphosted.com 1800 Pri: 10
TXT

gsb.stanford.edu

1800 Txt: v=verifydomain MS=ms13BC86
TXT

gsb.stanford.edu

1800 Txt: v=spf1 ip4:171.67.219.64/27 ip4:171.67.224.0/28 ip4:171.67.214.160/27 ip4:171.67.216.240/28 include:aspmx.pardot.com ~all

Language and encoding

Good result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

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

HTTPS certificate

SSL Certificate

Gsb.stanford.edu has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 45.3% of all visits is United States. It’s good for Gsb.stanford.edu that their server is also located in United States, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Normal result

Social Sharing Optimization

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this:

gsb.stanford.edu

Share this report in social media

Analyze another website

Analyze