1.7 sec in total
18 ms
1.3 sec
422 ms
Visit geocities.com now to see the best up-to-date Geocities content for United States and also check out these interesting facts you probably never knew about geocities.com
Latest news coverage, email, free stock quotes, live scores and video are just the beginning. Discover more every day at Yahoo!
Visit geocities.comWe analyzed Geocities.com page load time and found that the first response time was 18 ms and then it took 1.7 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.
geocities.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value9.0 s
1/100
25%
Value7.0 s
32/100
10%
Value1,980 ms
8/100
30%
Value0
100/100
15%
Value16.0 s
6/100
10%
18 ms
133 ms
266 ms
376 ms
129 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Geocities.com, 85% (62 requests) were made to S.yimg.com and 10% (7 requests) were made to Yahoo.com. The less responsive or slowest element that took the longest time to load (376 ms) relates to the external source Yahoo.com.
Page size can be reduced by 983.3 kB (46%)
2.2 MB
1.2 MB
In fact, the total size of Geocities.com main page is 2.2 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. HTML takes 1.2 MB which makes up the majority of the site volume.
Potential reduce by 977.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 977.5 kB or 80% of the original size.
Potential reduce by 1.6 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. Geocities images are well optimized though.
Potential reduce by 4.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 105 B
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. Geocities.com has all CSS files already compressed.
Number of requests can be reduced by 34 (53%)
64
30
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geocities. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
geocities.com
18 ms
yahoo.com
133 ms
yahoo.com
266 ms
www.yahoo.com
376 ms
cmp.js
129 ms
tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js
94 ms
fpDesktop.2e8440661542e9dfceb3228f597ec875.js
94 ms
benji-2.1.34.js
94 ms
wf-caas-1.36.5.js
92 ms
wf-toggle-1.15.4.js
99 ms
react-wafer-featurebar.custom.default.95a7979b4c06295e22960043d003fb49.js
98 ms
wf-clipboard-copy-1.0.2.js
98 ms
wf-video-3.1.2.js
98 ms
wf-bind-1.1.3.js
97 ms
wf-text-1.2.0.js
102 ms
wf-beacon-1.3.4.js
102 ms
wf-fetch-1.19.1.js
102 ms
wf-lightbox-1.10.6.js
101 ms
wf-scrollview-2.22.6.js
101 ms
wf-countdown-1.2.5.js
102 ms
wf-benji-1.1.4.js
103 ms
wf-form-1.34.5.js
103 ms
wf-native-da-1.0.5.js
106 ms
wf-action-1.8.1.js
106 ms
wf-template-1.4.3.js
106 ms
wf-menu-1.3.0.js
104 ms
wf-image-1.4.0.js
106 ms
wf-rapid-1.10.8.js
107 ms
react-wafer-stream.custom.default.34fba140d46159f80d116c63459e57e7.js
110 ms
cd05a83.caas-news_web.min.js
109 ms
privacy-choice-control.png
75 ms
cerebro_min.js
40 ms
9a2c5c30-098a-11ef-9dff-e1c263f5bebb.cf.jpg
50 ms
f984ae90-0984-11ef-becb-95027689166f.cf.jpg
39 ms
0434c400-09cc-11ef-bfff-21e08ad1ce3d.cf.jpg
38 ms
e6bc26d0-09ac-11ef-b9bb-af18ced70162.cf.jpg
42 ms
66b8c860-0959-11ef-be7d-698981377cf0.cf.jpg
40 ms
65fff120-0984-11ef-9ffb-83eda106ca48.cf.jpg
39 ms
Regular.woff
40 ms
Medium.woff
49 ms
Light.woff
50 ms
ExtraLight.woff
50 ms
Semibold.woff
47 ms
e853671f103def33c9808736c47bc0a1.cf.jpg
22 ms
trendingNow.yhome-atomic.c16f97f81be530fa2b48a1ffeffd4678.min.css
9 ms
trendingNow-flameIcon.yhome-variable.a2368adb8251677d29ac1399a6f34c43.min.css
11 ms
analytics-3.54.1.js
90 ms
wf-core-1.65.1.js
39 ms
homepage-pwa-defer-1.1.6.js
37 ms
safe.min.js
39 ms
advertisement_0.0.19.js
143 ms
f208b33c55ddff46767eaf4e799cd5ff.cf.jpg
296 ms
4fafab7d59b54372f34d9bf99ce5a816.cf.jpg
296 ms
7eb451b0-09b2-11ef-bf57-688ce2c0f06b.cf.jpg
297 ms
cf9defcdd87decabdc1b132c3d487c2e.cf.jpg
299 ms
3f3e8a04edc7c92bcd41dcfe9aa6e4a1.cf.jpg
297 ms
66cbded9eb5306f46f8a60bb2c007183.cf.jpg
298 ms
4871f66b7c9152ad088717b37fa7d7ef.cf.jpg
298 ms
245ee5f1654e6e6a0d529368dd31ef6a.cf.jpg
299 ms
cf43573223f3923a7ff8b7a580b364f8.cf.jpg
303 ms
e3818670-0ea6-11ed-8bb7-0ade0841274b.cf.jpg
301 ms
69b912749e4b37d812c69b39eed0729b.cf.jpg
302 ms
2537a240-089f-11ef-bb4e-50e946c7e07b.cf.jpg
301 ms
4806d70c50a1489c3d880c5f22b9aead.cf.jpg
303 ms
60dc9a56db985411298f00295408f5ad.cf.jpg
300 ms
cs_1.6.0.js
201 ms
evplayer.js
134 ms
remote
221 ms
exp.json
47 ms
perf-vitals_3.2.0.js
46 ms
88 ms
148 ms
97d5f9b.caas-news_web.min.css
4 ms
geocities.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
Image elements do not have [alt] attributes
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.
geocities.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
Browser errors were logged to the console
Page has valid source maps
geocities.com 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
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 Geocities.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 Geocities.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.
geocities.com
Open Graph data is detected on the main page of Geocities. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: