Tools & Wizards About Us
gm2.fnal.gov screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

gm2.fnal.gov

Page Load Speed

1.1 sec in total

First Response

101 ms

Resources Loaded

870 ms

Page Rendered

171 ms

gm2.fnal.gov screenshot

About Website

Welcome to gm2.fnal.gov homepage info - get ready to check Gm 2 Fnal best content for China right away, or after learning these important things about gm2.fnal.gov

Visit gm2.fnal.gov

Key Findings

We analyzed Gm2.fnal.gov page load time and found that the first response time was 101 ms and then it took 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

gm2.fnal.gov performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

gm2.fnal.gov

101 ms

muon-g-2.fnal.gov

124 ms

slideshow.js

78 ms

bootstrap.min.css

161 ms

global.css

178 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gm2.fnal.gov, 62% (26 requests) were made to Fnal.gov and 29% (12 requests) were made to Muon-g-2.fnal.gov. The less responsive or slowest element that took the longest time to load (328 ms) relates to the external source Muon-g-2.fnal.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 433.5 kB (38%)

Content Size

1.1 MB

After Optimization

699.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gm2.fnal.gov main page is 1.1 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. 30% of websites need less resources to load. Images take 633.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 17.6 kB

  • Original 21.6 kB
  • After minification 14.1 kB
  • After compression 4.1 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 7.6 kB, which is 35% 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 17.6 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 63.2 kB

  • Original 633.5 kB
  • After minification 570.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. Gm 2 Fnal images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 200.6 kB

  • Original 295.3 kB
  • After minification 261.9 kB
  • After compression 94.8 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 200.6 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 152.2 kB

  • Original 182.5 kB
  • After minification 155.7 kB
  • After compression 30.3 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. Gm2.fnal.gov needs all CSS files to be minified and compressed as it can save up to 152.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gm2.fnal.gov

gm2.fnal.gov

101 ms

muon-g-2.fnal.gov

muon-g-2.fnal.gov

124 ms

slideshow.js

slideshow.js

78 ms

bootstrap.min.css

bootstrap.min.css

161 ms

global.css

global.css

178 ms

legacy.css

legacy.css

173 ms

pages.css

pages.css

152 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

207 ms

bootstrap.js

bootstrap.js

185 ms

twitter-widgets.js

twitter-widgets.js

259 ms

holder.js

holder.js

215 ms

bootstrap-hover-dropdown.min.js

bootstrap-hover-dropdown.min.js

206 ms

fnal-script.js

fnal-script.js

209 ms

collapse.js

collapse.js

232 ms

transition.js

transition.js

257 ms

responsive-tabs.js

responsive-tabs.js

253 ms

screen_1200_and_up.css

screen_1200_and_up.css

201 ms

Collab-Nov2014.jpg

Collab-Nov2014.jpg

176 ms

Arch-Hogan.jpg

Arch-Hogan.jpg

143 ms

ground-breaking-g-2.jpg

ground-breaking-g-2.jpg

148 ms

KellyDrill.jpg

KellyDrill.jpg

158 ms

MC1.jpg

MC1.jpg

180 ms

FirstYoke.jpg

FirstYoke.jpg

152 ms

banner.jpg

banner.jpg

328 ms

g-2Logo-sm.png

g-2Logo-sm.png

270 ms

g-2.jpg

g-2.jpg

271 ms

Ring-on-truck-RHahn.jpg

Ring-on-truck-RHahn.jpg

288 ms

logo-fnal-blue.png

logo-fnal-blue.png

268 ms

logo-fnal.png

logo-fnal.png

268 ms

logo-facebook-xsmall.png

logo-facebook-xsmall.png

267 ms

logo-doe.png

logo-doe.png

269 ms

logo-fra.png

logo-fra.png

269 ms

css

css

23 ms

sprite-toggle.png

sprite-toggle.png

58 ms

btn-pointer-blue.png

btn-pointer-blue.png

73 ms

ga.js

ga.js

22 ms

__utm.gif

__utm.gif

12 ms

print.css

print.css

50 ms

screen_0-480.css

screen_0-480.css

52 ms

screen_481-767.css

screen_481-767.css

55 ms

screen_768-991.css

screen_768-991.css

51 ms

screen_992-1199.css

screen_992-1199.css

50 ms

Accessibility Review

gm2.fnal.gov accessibility score

68

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

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

gm2.fnal.gov 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

SEO Factors

gm2.fnal.gov SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gm2.fnal.gov can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Gm2.fnal.gov 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

gm2.fnal.gov

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