Tools & Wizards About Us
lockergnome.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

lockergnome.com

Twitch

Page Load Speed

2.7 sec in total

First Response

543 ms

Resources Loaded

1.9 sec

Page Rendered

218 ms

lockergnome.com screenshot

About Website

Visit lockergnome.com now to see the best up-to-date Lockergnome content for United States and also check out these interesting facts you probably never knew about lockergnome.com

Love tech? Play video games? Enjoy interacting with fellow geeks & nerds? I host this 24/7 broadcast for you to join as a participant! You’ll find us sharing our geeky / nerdy activities, conversation...

Visit lockergnome.com

Key Findings

We analyzed Lockergnome.com page load time and found that the first response time was 543 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

lockergnome.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value10,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value29.2 s

0/100

10%

Network Requests Diagram

www.lockergnome.com

543 ms

cloudflare.min.js

15 ms

css

37 ms

google_service.js

32 ms

style.css

28 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 17% of them (13 requests) were addressed to the original Lockergnome.com, 13% (10 requests) were made to W.soundcloud.com and 9% (7 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (543 ms) belongs to the original domain Lockergnome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (63%)

Content Size

2.0 MB

After Optimization

734.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lockergnome.com main page is 2.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. 70% of websites need less resources to load. Javascripts take 938.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 79.8 kB

  • Original 94.5 kB
  • After minification 94.4 kB
  • After compression 14.7 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 79.8 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 12.1 kB

  • Original 98.4 kB
  • After minification 86.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. Obviously, Lockergnome needs image optimization as it can save up to 12.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 601.5 kB

  • Original 938.9 kB
  • After minification 898.5 kB
  • After compression 337.4 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 601.5 kB or 64% of the original size.

CSS Optimization

-66%

Potential reduce by 562.6 kB

  • Original 858.8 kB
  • After minification 850.4 kB
  • After compression 296.2 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. Lockergnome.com needs all CSS files to be minified and compressed as it can save up to 562.6 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (67%)

Requests Now

67

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lockergnome.com

www.lockergnome.com

543 ms

cloudflare.min.js

cloudflare.min.js

15 ms

css

css

37 ms

google_service.js

google_service.js

32 ms

style.css

style.css

28 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

31 ms

wp-mediaelement.css

wp-mediaelement.css

28 ms

jetpack.css

jetpack.css

28 ms

jquery.min.js

jquery.min.js

36 ms

swfobject.js

swfobject.js

40 ms

adsbygoogle.js

adsbygoogle.js

26 ms

832502567.js

832502567.js

29 ms

photon.js

photon.js

25 ms

1863799.js

1863799.js

32 ms

devicepx-jetpack.js

devicepx-jetpack.js

158 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

25 ms

wp-mediaelement.js

wp-mediaelement.js

24 ms

wp-embed.min.js

wp-embed.min.js

23 ms

e-201609.js

e-201609.js

21 ms

google_ads.js

google_ads.js

17 ms

plusone.js

plusone.js

262 ms

ga.js

ga.js

137 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

127 ms

rss-icon.png

rss-icon.png

102 ms

widgets.js

widgets.js

288 ms

header.png

header.png

101 ms

button.png

button.png

257 ms

videoseries

videoseries

331 ms

354 ms

353 ms

displays.htm

displays.htm

195 ms

gradient.png

gradient.png

193 ms

new_lockergnome_logo.png

new_lockergnome_logo.png

89 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

196 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

259 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

260 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

264 ms

ca-pub-7561297527511227.js

ca-pub-7561297527511227.js

233 ms

zrt_lookup.html

zrt_lookup.html

231 ms

show_ads_impl.js

show_ads_impl.js

179 ms

__ptq.gif

__ptq.gif

165 ms

g.gif

g.gif

131 ms

__utm.gif

__utm.gif

150 ms

subscribe_widget

subscribe_widget

115 ms

ads

ads

154 ms

follow.php

follow.php

93 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

osd.js

osd.js

62 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

168 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

52 ms

www-embed-player.js

www-embed-player.js

83 ms

base.js

base.js

146 ms

www-subscribe-widget-vfl_AxbQf.css

www-subscribe-widget-vfl_AxbQf.css

122 ms

photo.jpg

photo.jpg

32 ms

www-subscribe-widget.js

www-subscribe-widget.js

121 ms

youtube_icon_small-vfliqe9hM.jpg

youtube_icon_small-vfliqe9hM.jpg

120 ms

-1cfYrhulAt.js

-1cfYrhulAt.js

378 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

426 ms

267 ms

266 ms

258 ms

www-hitchhiker-vfluKv9vH.png

www-hitchhiker-vfluKv9vH.png

84 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

75 ms

ad_status.js

ad_status.js

77 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

57 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

89 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

89 ms

interstate-0ab59479718c8235122cad6b16a66953d725c43a.css

interstate-0ab59479718c8235122cad6b16a66953d725c43a.css

214 ms

widget-ea7fb002.css

widget-ea7fb002.css

58 ms

widget-4cab6819.js

widget-4cab6819.js

157 ms

logo-200x120-177df3dd.png

logo-200x120-177df3dd.png

30 ms

ga.js

ga.js

62 ms

visual-single-sound-3fc9613a.js

visual-single-sound-3fc9613a.js

98 ms

error-698b3c1d.js

error-698b3c1d.js

48 ms

jot.html

jot.html

89 ms

__utm.gif

__utm.gif

74 ms

Accessibility Review

lockergnome.com accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

ARIA input fields do not have accessible names

High

[role]s are not contained by their required parent element

High

ARIA tooltip elements do not have accessible names.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

lockergnome.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

lockergnome.com SEO score

54

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

lockergnome.com

Open Graph data is detected on the main page of Lockergnome. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: