6 sec in total
1.9 sec
3.6 sec
547 ms
Click here to check amazing Geek content for Nigeria. Otherwise, check out these important facts you probably never knew about geek.ng
This domain may be for sale!
Visit geek.ngWe analyzed Geek.ng page load time and found that the first response time was 1.9 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
geek.ng performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value5.8 s
15/100
25%
Value5.5 s
55/100
10%
Value1,080 ms
24/100
30%
Value0.184
66/100
15%
Value11.2 s
20/100
10%
1860 ms
133 ms
127 ms
162 ms
140 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 68% of them (73 requests) were addressed to the original Geek.ng, 4% (4 requests) were made to Google-analytics.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Geek.ng.
Page size can be reduced by 805.7 kB (53%)
1.5 MB
702.2 kB
In fact, the total size of Geek.ng main page is 1.5 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. CSS take 513.0 kB which makes up the majority of the site volume.
Potential reduce by 90.8 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 90.8 kB or 80% of the original size.
Potential reduce by 1.8 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 309.3 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 309.3 kB or 62% of the original size.
Potential reduce by 403.8 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.ng needs all CSS files to be minified and compressed as it can save up to 403.8 kB or 79% of the original size.
Number of requests can be reduced by 53 (54%)
98
45
The browser has sent 98 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 30 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
geek.ng
1860 ms
wp-emoji-release.min.js
133 ms
style.css
127 ms
dashicons.min.css
162 ms
font-awesome.min.css
140 ms
extra.min.css
155 ms
devices.css
152 ms
buddypress.min.css
243 ms
styles.css
225 ms
style.css
227 ms
styles.css
262 ms
easy-social-share-buttons.css
310 ms
essb-social-fanscounter.css
263 ms
css
49 ms
style.css
318 ms
app.css
325 ms
aps-styles.css
364 ms
nivo-lightbox.css
347 ms
0a8dd671bf298fb1870d0fc3bfb9eea0a6fcaf3c.css
350 ms
jetpack.css
419 ms
jquery.js
551 ms
jquery-migrate.min.js
415 ms
confirm.min.js
461 ms
widget-members.min.js
449 ms
jquery-query.min.js
478 ms
jquery-cookie.min.js
517 ms
jquery-scroll-to.min.js
538 ms
buddypress.min.js
578 ms
responsive-menu.js
581 ms
elevatezoom-min.js
588 ms
gray.css
616 ms
css
28 ms
jquery.min.js
81 ms
ezjquery-noconflict.js
150 ms
imp2.js
530 ms
banger6.js
565 ms
brand
32 ms
a.js;p=11087206432074;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=
135 ms
jquery.form.min.js
662 ms
scripts.js
666 ms
qppr_frontend_script.min.js
783 ms
devicepx-jetpack.js
115 ms
nivo-lightbox.min.js
780 ms
e-201609.js
21 ms
tb.php
154 ms
simple-slider.min.js
770 ms
brand
140 ms
aps-main-script.js
705 ms
wp-embed.min.js
701 ms
ga.js
55 ms
gpt.js
33 ms
iphone-5s.jpg
30 ms
image-44.jpeg
30 ms
imose-q2.jpg
33 ms
wondershare-tunesgo...jpg
34 ms
imp.gif
148 ms
image-44-285x215.jpeg
206 ms
image-43-285x215.jpeg
199 ms
iphone-5s-285x215.jpg
208 ms
wondershare-tunesgo..-285x215.jpg
277 ms
android-malware1-285x215.jpg
209 ms
android-malware-285x215.jpg
280 ms
image-32-285x215.jpeg
278 ms
image-37-285x215.jpeg
318 ms
airtel-285x215.jpg
320 ms
infinity-blade-III-285x215.jpeg
353 ms
6fb05fdd9e1937fba290cef67f3a61dc-bpthumb.png
350 ms
GetResponse-320x180.png
385 ms
0d09325c8feec0e37a6424ab274d9199-bpthumb.jpg
838 ms
wondershare-tunesgo..-320x180.jpg
480 ms
654055e2623df2bd4a88eae1c1af8ae7-bpthumb.png
418 ms
iphone-5s-320x180.jpg
477 ms
3f90eb4694e86d60ede9ae0080c1a19a-bpthumb.jpg
532 ms
phone-internal-storage-320x180.jpg
809 ms
image-44-320x180.jpeg
808 ms
image-43-320x180.jpeg
810 ms
image-42-320x180.jpeg
810 ms
image-38-320x180.jpeg
832 ms
image-37-320x180.jpeg
832 ms
android-malware-320x180.jpg
832 ms
Asus-Zenfone-Selfie-120x120.png
831 ms
innjoo-2-120x120.jpg
830 ms
xiaomi-redmi-2-120x120.png
916 ms
phone-internal-storage.jpg
20 ms
sdk.js
192 ms
xiaomi-mi-4-120x120.jpg
907 ms
xiaomi-mi-4i1-120x120.jpg
915 ms
Tecno-Phantom-5-front-120x120.jpg
953 ms
pubads_impl_81.js
86 ms
__utm.gif
36 ms
__utm.gif
56 ms
__utm.gif
58 ms
logo2.png
831 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
50 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
52 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
116 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
116 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
41 ms
fontawesome-webfont.woff
902 ms
container.html
79 ms
88 ms
xd_arbiter.php
211 ms
xd_arbiter.php
504 ms
google_custom_search_watermark.gif
112 ms
27315-MPU-300x250-MSG-B-English-3.jpg
551 ms
essb-socialfans.woff
509 ms
g.gif
22 ms
geek.ng 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
geek.ng best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
geek.ng SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geek.ng 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.ng 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.ng
Open Graph data is detected on the main page of Geek. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: