2.8 sec in total
150 ms
1.5 sec
1.2 sec
Click here to check amazing Geek content for United States. Otherwise, check out these important facts you probably never knew about geek.com
Geeking out since 1995. Providing readers with tech news, reviews, and tips.
Visit geek.comWe analyzed Geek.com page load time and found that the first response time was 150 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
geek.com performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value17.7 s
0/100
25%
Value3.4 s
89/100
10%
Value220 ms
88/100
30%
Value0.151
76/100
15%
Value4.9 s
78/100
10%
150 ms
19 ms
41 ms
41 ms
89 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 36% of them (47 requests) were addressed to the original Geek.com, 5% (6 requests) were made to Images.taboola.com and 5% (6 requests) were made to Zdbb.net. The less responsive or slowest element that took the longest time to load (463 ms) belongs to the original domain Geek.com.
Page size can be reduced by 1.8 MB (19%)
9.3 MB
7.5 MB
In fact, the total size of Geek.com main page is 9.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.1 MB which makes up the majority of the site volume.
Potential reduce by 233.5 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 233.5 kB or 86% of the original size.
Potential reduce by 180.1 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. Geek images are well optimized though.
Potential reduce by 885.2 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 885.2 kB or 65% of the original size.
Potential reduce by 498.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. Geek.com needs all CSS files to be minified and compressed as it can save up to 498.5 kB or 83% of the original size.
Number of requests can be reduced by 77 (63%)
122
45
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.geek.com
150 ms
ga.js
19 ms
css
41 ms
geekgpt.js
41 ms
zd-email.js
89 ms
zdccg.min.js
16 ms
chartbeat_mab.js
35 ms
adreferrer.js
97 ms
tbwidget300x250.css
39 ms
sfp.js
110 ms
site.css
89 ms
jquery.fancybox.css
37 ms
font-awesome.min.css
10 ms
jquery.min.js
35 ms
stickycolumn.js
87 ms
jquery.colorbox.js
36 ms
newsletter.js
43 ms
gallery.js
50 ms
tblwd_b.js
39 ms
zdvtools.min.js
90 ms
zdrefresher.min.js
85 ms
adchoices.js
62 ms
foundation.min.js
63 ms
slick.min.js
60 ms
jquery.infinitescroll.min.js
58 ms
jquery.fancybox.pack.js
57 ms
site.js
87 ms
wp-embed.min.js
64 ms
z0WVjCBSEeGLoxIxOQVEwQ.min.js
57 ms
zdcse.min.js
83 ms
bk-coretag.js
85 ms
abw.js
9 ms
collect
72 ms
gurgle.zdbb.net
146 ms
segments.js
78 ms
ga-audiences
37 ms
pb5.min.js
61 ms
wp-emoji-release.min.js
51 ms
loader.js
17 ms
beacon.js
15 ms
seal
15 ms
128gb-floppy-625x350.jpg
89 ms
featured-2-625x350.jpg
91 ms
geek_logo.svg
29 ms
logo_geek.gif
28 ms
featured-3-625x352.jpg
95 ms
roary-625x350.jpg
92 ms
2864167-assassins_creed_syndicate_combat-punch-625x352.jpg
93 ms
DOOM-2016-Rev_Mancubus_1437988261-625x352.jpg
139 ms
flower-625x350.jpg
94 ms
mercedes_Sclass_01-625x350.jpg
136 ms
nuclearthronemain-625x350.jpg
135 ms
duelystart-625x352.jpg
136 ms
malware2-625x350.jpg
157 ms
Lootcrate-VS-625x350.jpg
136 ms
lc2du0zuzwnaioqdpuwt-625x352.jpg
137 ms
loras-625x350.jpg
166 ms
wrestling-conspiracies-625x350.jpg
138 ms
rerererre-625x352.jpg
137 ms
stela-625x350.jpg
156 ms
7hJiiEHoEeWRqiIAC39GJQ
20 ms
zd_footer_logo.png
25 ms
a.gif
19 ms
activeview
23 ms
set
18 ms
76 ms
impl.198-RELEASE.js
62 ms
noise02.gif
53 ms
FiraSans-Medium.woff
463 ms
FiraSans-Regular.woff
43 ms
FiraSans-Light.woff
79 ms
FiraSans-Bold.woff
138 ms
fontawesome-webfont.woff
6 ms
m
30 ms
next_arrow.svg
46 ms
adchoices.png
357 ms
pcmag.com.svg
35 ms
extremetech.svg
30 ms
computershopper.svg
33 ms
ign_logo.svg
39 ms
toolbox.svg
355 ms
ziff_davis.svg
353 ms
count.js
353 ms
json
338 ms
__utm.gif
17 ms
51BEjEHoEeWRqiIAC39GJQ
326 ms
gC3ekw7UEeWRqiIAC39GJQ
16 ms
__utm.gif
323 ms
gC3ekw7UEeWRqiIAC39GJQ
323 ms
51BEjEHoEeWRqiIAC39GJQ
324 ms
geek.js
291 ms
zd-core-olt.js
289 ms
geek.com-async.js
289 ms
jquery.min.js
287 ms
20087
452 ms
;ord=1456747629344
209 ms
bizarre-game-developers-625x350.jpg
185 ms
count-data.js
152 ms
count-data.js
154 ms
a4d01a7461bf1d009ed1b1e2cd8c6a1a.jpg
134 ms
3aadbb71016ecd7a194bbe2791777e9a.png
133 ms
__utm.gif
29 ms
51BEjEHoEeWRqiIAC39GJQ
28 ms
v60.js
49 ms
walker-min.js
99 ms
__utm.gif
32 ms
;ord=1456747629400
40 ms
991e4f79ccae238f54cbdccee1a718c6.jpg
33 ms
ec43c73f8fed4d1f7bf856b6f0f33893.jpg
34 ms
gC3ekw7UEeWRqiIAC39GJQ
32 ms
gC3ekw7UEeWRqiIAC39GJQ
33 ms
51BEjEHoEeWRqiIAC39GJQ
34 ms
firstevent
34 ms
20214
95 ms
f2ac4c2afaeaed537848e5977eabf612.jpg
24 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
20 ms
79e75903e77441e0c149bcf933e3a99c.jpg
22 ms
19bce6b8f454f5c9ad9eb50c98021ed0.jpg
23 ms
c3bfe62dfd5aad14ccdd9f61cb277b2d.jpg
22 ms
8def1998b42f287dd24239092b2ad1cf.jpeg
23 ms
_6546378.jpg
24 ms
gpt.js
21 ms
bcn
168 ms
20838
25 ms
bcn
187 ms
pubads_impl_81.js
10 ms
check
72 ms
ads
89 ms
container.html
9 ms
pixel
14 ms
32 ms
osd.js
3 ms
geek.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
geek.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
geek.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geek.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 Geek.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.
geek.com
Open Graph description is not detected on the main page of Geek. 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: