Tools & Wizards About Us
slashgear.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

slashgear.com

SlashGear | Tech, Cars, Gaming, Science, & Reviews

Page Load Speed

2.4 sec in total

First Response

546 ms

Resources Loaded

1.3 sec

Page Rendered

499 ms

slashgear.com screenshot

About Website

Welcome to slashgear.com homepage info - get ready to check Slash Gear best content for United States right away, or after learning these important things about slashgear.com

The latest news and reviews in the world of tech, automotive, gaming, science, and entertainment - since 2005.

Visit slashgear.com

Key Findings

We analyzed Slashgear.com page load time and found that the first response time was 546 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

slashgear.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

www.slashgear.com

546 ms

bootstrap.min.css

107 ms

sg-css.min.css

84 ms

font-awesome.min.css

70 ms

jetpack.css

88 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Slashgear.com, 55% (46 requests) were made to Cdn.slashgear.com and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (546 ms) belongs to the original domain Slashgear.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (34%)

Content Size

3.6 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Slashgear.com main page is 3.6 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 54.0 kB

  • Original 63.6 kB
  • After minification 50.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 13.7 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 54.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 9.3 kB

  • Original 1.9 MB
  • After minification 1.9 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. Slash Gear images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 562.9 kB

  • Original 848.9 kB
  • After minification 842.9 kB
  • After compression 286.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 562.9 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 619.2 kB

  • Original 777.8 kB
  • After minification 728.0 kB
  • After compression 158.5 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. Slashgear.com needs all CSS files to be minified and compressed as it can save up to 619.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (43%)

Requests Now

76

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.slashgear.com

www.slashgear.com

546 ms

bootstrap.min.css

bootstrap.min.css

107 ms

sg-css.min.css

sg-css.min.css

84 ms

font-awesome.min.css

font-awesome.min.css

70 ms

jetpack.css

jetpack.css

88 ms

jquery.min.js

jquery.min.js

27 ms

custom.minv3.css

custom.minv3.css

89 ms

home.min.v3.css

home.min.v3.css

89 ms

slashgear.com.js

slashgear.com.js

37 ms

devicepx-jetpack.js

devicepx-jetpack.js

57 ms

bootstrap.min.js

bootstrap.min.js

86 ms

superfish177.min.js

superfish177.min.js

196 ms

sgcs.min.js

sgcs.min.js

197 ms

wp-embed.min.js

wp-embed.min.js

197 ms

e-201609.js

e-201609.js

6 ms

analytics.js

analytics.js

94 ms

slashgear.png

slashgear.png

65 ms

RazerBladeStealth_review_slashgear_hero1-450x250.jpg

RazerBladeStealth_review_slashgear_hero1-450x250.jpg

63 ms

best-450x250.jpg

best-450x250.jpg

63 ms

vuklagaga-450x250.jpg

vuklagaga-450x250.jpg

64 ms

thetas_review-450x250.jpg

thetas_review-450x250.jpg

65 ms

xperiax_go-450x250.jpg

xperiax_go-450x250.jpg

69 ms

2.jpg

2.jpg

67 ms

wigig-1-450x250.jpg

wigig-1-450x250.jpg

196 ms

mit-solar-bubble-450x250.jpg

mit-solar-bubble-450x250.jpg

68 ms

mband2-450x250.jpg

mband2-450x250.jpg

69 ms

Foxconn-1-450x250.jpg

Foxconn-1-450x250.jpg

70 ms

CcSgP4QVIAMAGR3-450x250.jpg

CcSgP4QVIAMAGR3-450x250.jpg

183 ms

spacex-3rd-450x250.jpg

spacex-3rd-450x250.jpg

182 ms

samsung-galaxy-s7-s7edge-sg-61-1-450x250.jpg

samsung-galaxy-s7-s7edge-sg-61-1-450x250.jpg

182 ms

hololens-app-1-450x250.jpg

hololens-app-1-450x250.jpg

184 ms

IMG_4090-450x250.jpg

IMG_4090-450x250.jpg

185 ms

ps4v-820x420-450x250.jpg

ps4v-820x420-450x250.jpg

190 ms

apple-v-samsung-800x500-1-450x250.jpg

apple-v-samsung-800x500-1-450x250.jpg

189 ms

sp707-imac_connection_ports-450x250.jpg

sp707-imac_connection_ports-450x250.jpg

190 ms

Lamborghini-Huracan-Spider-Hero-0-450x250.jpg

Lamborghini-Huracan-Spider-Hero-0-450x250.jpg

194 ms

2016-honda-civic-coupe-hero-0-450x250.jpg

2016-honda-civic-coupe-hero-0-450x250.jpg

195 ms

hondadrivemode-200x200.jpg

hondadrivemode-200x200.jpg

193 ms

applecar-728x420-200x200.jpg

applecar-728x420-200x200.jpg

191 ms

Ford-Camo-200x200.jpg

Ford-Camo-200x200.jpg

192 ms

Lenovo-YOGA-260-Main-Image-450x250.jpg

Lenovo-YOGA-260-Main-Image-450x250.jpg

195 ms

Steelie-1-450x250.jpg

Steelie-1-450x250.jpg

196 ms

BmgH82c-200x200.jpg

BmgH82c-200x200.jpg

197 ms

thetas_review-200x200.jpg

thetas_review-200x200.jpg

249 ms

yugioh-200x200.png

yugioh-200x200.png

262 ms

best-200x200.jpg

best-200x200.jpg

252 ms

Lenovo-YOGA-260-Main-Image-200x200.jpg

Lenovo-YOGA-260-Main-Image-200x200.jpg

252 ms

Lenovo-Project-Tango-MWC-16-2-200x200.jpg

Lenovo-Project-Tango-MWC-16-2-200x200.jpg

253 ms

slashgear.com-async.js

slashgear.com-async.js

33 ms

nsgpt.jsonp

nsgpt.jsonp

32 ms

gpt.js

gpt.js

30 ms

tag.js

tag.js

181 ms

dincond-medium-webfont.woff

dincond-medium-webfont.woff

169 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

182 ms

fallout-4-survival-450x250.jpg

fallout-4-survival-450x250.jpg

241 ms

imrta-450x250.jpg

imrta-450x250.jpg

247 ms

js

js

41 ms

applecase-200x200.jpg

applecase-200x200.jpg

226 ms

apple-lock-900x420-1-200x200.jpg

apple-lock-900x420-1-200x200.jpg

225 ms

g.gif

g.gif

24 ms

collect

collect

21 ms

pubads_impl_81.js

pubads_impl_81.js

20 ms

ga.js

ga.js

18 ms

beacon.js

beacon.js

18 ms

walker-min.js

walker-min.js

125 ms

gurgle.zdbb.net

gurgle.zdbb.net

131 ms

v60.js

v60.js

136 ms

bk-coretag.js

bk-coretag.js

16 ms

vrheadset-200x200.jpg

vrheadset-200x200.jpg

204 ms

__utm.gif

__utm.gif

99 ms

ads

ads

215 ms

container.html

container.html

91 ms

__utm.gif

__utm.gif

76 ms

set

set

79 ms

in.php

in.php

182 ms

check

check

44 ms

20838

20838

42 ms

pixel

pixel

17 ms

pixel

pixel

16 ms

pixel

pixel

16 ms

2981

2981

20 ms

26 ms

osd.js

osd.js

11 ms

Accessibility Review

slashgear.com accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

slashgear.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

slashgear.com SEO score

91

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

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Slashgear.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 Slashgear.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

slashgear.com

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