1.9 sec in total
268 ms
1.3 sec
333 ms
Visit oocities.org now to see the best up-to-date Oocities content for United States and also check out these interesting facts you probably never knew about oocities.org
oocities - geocities archive geocities mirror
Visit oocities.orgWe analyzed Oocities.org page load time and found that the first response time was 268 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 30% of websites can load faster.
oocities.org performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.1 s
75/100
25%
Value3.5 s
88/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value4.5 s
82/100
10%
268 ms
192 ms
92 ms
18 ms
31 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 21% of them (12 requests) were addressed to the original Oocities.org, 38% (21 requests) were made to Static.xx.fbcdn.net and 21% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (363 ms) relates to the external source Facebook.com.
Page size can be reduced by 61.4 kB (25%)
249.0 kB
187.6 kB
In fact, the total size of Oocities.org main page is 249.0 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. 50% of websites need less resources to load. Images take 171.0 kB which makes up the majority of the site volume.
Potential reduce by 43.9 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 43.9 kB or 82% of the original size.
Potential reduce by 15.3 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. Oocities images are well optimized though.
Potential reduce by 156 B
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 2.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. Oocities.org needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 78% of the original size.
Number of requests can be reduced by 23 (43%)
53
30
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oocities. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
oocities.org
268 ms
www.oocities.org
192 ms
cities.css
92 ms
show_afs_search.js
18 ms
brand
31 ms
brand
56 ms
ga.js
30 ms
google_custom_search_watermark.gif
87 ms
b.png
92 ms
a.jpg
248 ms
1.jpg
249 ms
2.jpg
171 ms
W3c.png
171 ms
dmoz.svg.png
182 ms
sourceforge.jpg
185 ms
ultimatebootcd.gif
255 ms
wiki.png
336 ms
__utm.gif
27 ms
likebox.php
363 ms
FbUd6dZS1Af.css
48 ms
dGJLq38YL-C.css
54 ms
f7m6HODnCDd.css
65 ms
i5_N_HL0uEJ.css
77 ms
Msuaq9yC6iC.css
88 ms
_rx8naC75Dy.js
96 ms
x5F9OMjKyLw.js
95 ms
ICDbTSzjQEg.js
75 ms
TTCre3391I0.js
69 ms
njO1TPvGzoR.js
93 ms
b_6HNn_J2BZ.js
94 ms
7cm7D75Y0Sf.js
120 ms
rFmE1g6Dkoz.js
125 ms
336JejShbZp.js
118 ms
1231103_626329370745567_1171434151_n.jpg
87 ms
safe_image.php
79 ms
safe_image.php
40 ms
safe_image.php
43 ms
safe_image.php
48 ms
1184906_626330004078837_1883907283_n.jpg
39 ms
230959_105578219531030_4471955_n.jpg
47 ms
12366259_10153683392545155_3783410720687967269_n.jpg
48 ms
11140034_10153726746815831_7331128571972335479_n.jpg
51 ms
11224775_529944803827301_16865912417086212_n.jpg
51 ms
486820_10151384606630487_2031686476_n.jpg
47 ms
1914226_100338193320350_6854154_n.jpg
48 ms
10401591_10203725248549594_2789502560296273274_n.jpg
53 ms
10858472_665481806898050_8881728868307946052_n.jpg
54 ms
11831821_508375229314096_6515301577367888688_n.jpg
55 ms
10514674_866137223408498_2378270224110041342_n.jpg
53 ms
wL6VQj7Ab77.png
13 ms
s7jcwEQH7Sx.png
14 ms
QDwYpIaRyfG.png
17 ms
K0srxReVLKP.png
20 ms
a-ZN6WoEOje.png
18 ms
I6-MnjEovm5.js
10 ms
vlXaquuXMrr.js
14 ms
oocities.org 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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
oocities.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
oocities.org 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
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oocities.org 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 Oocities.org 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.
oocities.org
Open Graph description is not detected on the main page of Oocities. 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: