1.8 sec in total
174 ms
1.1 sec
494 ms
Welcome to oocities.com homepage info - get ready to check Oocities best content right away, or after learning these important things about oocities.com
oocities - geocities archive geocities mirror
Visit oocities.comWe analyzed Oocities.com page load time and found that the first response time was 174 ms and then it took 1.6 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.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.3 s
69/100
25%
Value3.6 s
86/100
10%
Value80 ms
99/100
30%
Value0.017
100/100
15%
Value4.7 s
80/100
10%
174 ms
194 ms
94 ms
14 ms
25 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Oocities.com, 39% (22 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 (519 ms) relates to the external source Oocities.org.
Page size can be reduced by 61.6 kB (25%)
246.6 kB
185.0 kB
In fact, the total size of Oocities.com main page is 246.6 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. 60% of websites need less resources to load. Images take 168.4 kB which makes up the majority of the site volume.
Potential reduce by 44.0 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 44.0 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.com 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 19 (35%)
54
35
The browser has sent 54 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 7 to 1 for CSS and as a result speed up the page load time.
oocities.com
174 ms
www.oocities.org
194 ms
cities.css
94 ms
show_afs_search.js
14 ms
brand
25 ms
brand
65 ms
ga.js
30 ms
google_custom_search_watermark.gif
87 ms
b.png
93 ms
a.jpg
280 ms
1.jpg
280 ms
2.jpg
179 ms
W3c.png
182 ms
dmoz.svg.png
191 ms
sourceforge.jpg
192 ms
ultimatebootcd.gif
262 ms
wiki.png
519 ms
likebox.php
249 ms
__utm.gif
15 ms
410ucuAGgaJ.css
32 ms
pERLJfhzcxv.css
35 ms
Czh0gDTFcBt.css
42 ms
Ek6lpayKeeB.css
44 ms
EoarYgA68t4.css
59 ms
M9KHpdajqnb.css
34 ms
FAHeNGXgPup.js
42 ms
FJmpeSpHpjS.js
98 ms
0wM5s1Khldu.js
96 ms
1bNoFZUdlYZ.js
111 ms
njO1TPvGzoR.js
96 ms
1QuX41zDRrx.js
116 ms
Oagsvfb4VWi.js
115 ms
m-2AbGY1fWh.js
123 ms
1FCa-btixu2.js
115 ms
1231103_626329370745567_1171434151_n.jpg
103 ms
safe_image.php
119 ms
safe_image.php
44 ms
safe_image.php
48 ms
safe_image.php
45 ms
1184906_626330004078837_1883907283_n.jpg
35 ms
12508999_1674675136135707_6893963001404680847_n.jpg
33 ms
11054299_1600907253487678_8922993422747729751_n.jpg
37 ms
12688237_1692473551011310_6094347810916952720_n.jpg
39 ms
11221285_956260877764704_6770456151338287006_n.jpg
39 ms
1425615_10202445539129316_307242767_n.jpg
38 ms
10354686_10150004552801856_220367501106153455_n.jpg
40 ms
10418347_1707746136140961_7485475717494255124_n.jpg
38 ms
11951760_432596626937876_7949157844762224628_n.jpg
40 ms
1959432_485805511542712_1757864144_n.jpg
42 ms
11831821_508375229314096_6515301577367888688_n.jpg
44 ms
wL6VQj7Ab77.png
31 ms
s7jcwEQH7Sx.png
32 ms
QDwYpIaRyfG.png
26 ms
K0srxReVLKP.png
26 ms
K00K-UgnsKu.png
25 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
5 ms
oocities.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.
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.com 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.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
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.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 Oocities.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.
oocities.com
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: