3.1 sec in total
101 ms
2.7 sec
311 ms
Click here to check amazing 3 Geez content for United States. Otherwise, check out these important facts you probably never knew about 3geez.com
A discussion forum dedicated to 1st, 2nd, and 3rd Generation Honda Accords and Honda Preludes
Visit 3geez.comWe analyzed 3geez.com page load time and found that the first response time was 101 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
3geez.com performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value5.0 s
26/100
25%
Value5.5 s
55/100
10%
Value1,850 ms
9/100
30%
Value0.012
100/100
15%
Value11.8 s
17/100
10%
101 ms
617 ms
6 ms
202 ms
167 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 39% of them (55 requests) were addressed to the original 3geez.com, 10% (14 requests) were made to Images.intellitxt.com and 4% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain 3geez.com.
Page size can be reduced by 541.1 kB (57%)
947.3 kB
406.2 kB
In fact, the total size of 3geez.com main page is 947.3 kB. 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. Javascripts take 581.0 kB which makes up the majority of the site volume.
Potential reduce by 114.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 114.7 kB or 86% of the original size.
Potential reduce by 6.7 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. 3 Geez images are well optimized though.
Potential reduce by 329.6 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 329.6 kB or 57% of the original size.
Potential reduce by 90.0 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. 3geez.com needs all CSS files to be minified and compressed as it can save up to 90.0 kB or 79% of the original size.
Number of requests can be reduced by 91 (68%)
133
42
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 3 Geez. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
3geez.com
101 ms
617 ms
combo
6 ms
vbulletin-core.js
202 ms
main-rollup.css
167 ms
vbulletin_read_marker.js
188 ms
forumhome-rollup.css
111 ms
sidebar.css
900 ms
widgets.css
111 ms
tagcloud.css
187 ms
vbulletin-sidebar.js
235 ms
additional.css
201 ms
vbulletin_md5.js
264 ms
brand
18 ms
adsbygoogle.js
6 ms
brand
31 ms
element.js
41 ms
vbulletin_facebook.js
229 ms
front.asp
32 ms
analytics.js
5 ms
collect
11 ms
collect
52 ms
animation-min.js
4 ms
3geezlogo2.png
210 ms
vf_3gzfooterB.jpg
471 ms
facebook_login.gif
77 ms
search.png
147 ms
navbit-home.png
71 ms
collapse_40b.png
77 ms
forum_old_lock-48.png
174 ms
subforum_old-48.png
173 ms
lastpost-right.png
175 ms
icon14.png
175 ms
icon5.png
176 ms
icon4.png
207 ms
users_online.png
206 ms
forum_stats.png
234 ms
legend.png
320 ms
forum_new-16.png
235 ms
forum_old-16.png
320 ms
forum_lock-16.png
355 ms
category-16.png
322 ms
forum_link-16.png
321 ms
tab-collapsed-left.png
389 ms
widget-comment.png
392 ms
avatar7439_87.gif
398 ms
avatar989_3.gif
397 ms
avatar21851_1.gif
399 ms
avatar20558_6.gif
400 ms
avatar10148_6.gif
438 ms
unknown.gif
439 ms
avatar5893_4.gif
468 ms
widget-forum.png
499 ms
avatar286_3.gif
468 ms
avatar9769_4.gif
496 ms
avatar18637_1.gif
497 ms
gradient-grey-down.png
495 ms
newbtn_middle.png
493 ms
selected-tab-gradient-with-top-alpha.png
491 ms
arrow.png
560 ms
google_custom_search_watermark.gif
55 ms
ca-pub-5073010023022288.js
52 ms
zrt_lookup.html
51 ms
show_ads_impl.js
52 ms
translateelement.css
105 ms
main.js
114 ms
grey-up.png
509 ms
rss_40b.png
545 ms
gradient-greytowhite.png
502 ms
ads
271 ms
osd.js
32 ms
top-highlight.png
475 ms
ads
226 ms
gradient-black-down.png
402 ms
bottom-shadow.png
459 ms
sdk.js
258 ms
load
36 ms
vglnk.js
54 ms
element_main.js
48 ms
jload
171 ms
itxtcss_1446206988.css
76 ms
underscore-min-ns-1.4.2.js
80 ms
core_1446569672.js
82 ms
data_1444835675.js
83 ms
debug_1395261999.js
81 ms
fx_1395261999.js
80 ms
fx2_1395261999.js
85 ms
itxt_1426253035.js
84 ms
metrics_1395261999.js
85 ms
tmpl_1443709758.js
84 ms
ui_1447845393.js
87 ms
ui_mobile_1423653241.js
84 ms
pixel.gif
63 ms
pixel.gif
70 ms
translate_24dp.png
118 ms
l
112 ms
cleardot.gif
107 ms
px.gif
42 ms
loading.gif
82 ms
abg.js
79 ms
132 ms
adj
116 ms
beacon
114 ms
mon
78 ms
te_ctrl3.gif
54 ms
dt
33 ms
144 ms
xd_arbiter.php
144 ms
xd_arbiter.php
274 ms
45 ms
0
90 ms
surly.js
71 ms
index.html
291 ms
verify_selector.js
180 ms
blank.gif
179 ms
ba.html
48 ms
pixel
45 ms
lidar.js
33 ms
sbhK2lTE.js
32 ms
4.gif
61 ms
cTrvNaRi.html
15 ms
pixel
82 ms
pixel
83 ms
4311.js
31 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
17 ms
setuid
142 ms
ping
25 ms
verifyr.js
78 ms
sd
9 ms
optimize
55 ms
domains
94 ms
beacon.js
38 ms
0
31 ms
bg.png
37 ms
adchoices.en.png
84 ms
Rejuvenation_728x90_logo.gif
51 ms
MommyMakeover_728x90_bg.jpg
92 ms
box_19_top-right.png
39 ms
ci.png
32 ms
xd_arbiter.php
91 ms
3geez.com accessibility score
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
[aria-*] attributes do not match their roles
[role]s do not have all required [aria-*] attributes
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
3geez.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
3geez.com SEO score
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
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 3geez.com 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 3geez.com 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.
3geez.com
Open Graph description is not detected on the main page of 3 Geez. 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: