mocospace.com

mocospace.com is SSL secured

Free website and domain report on mocospace.com

Last Updated: 13th December, 2022 Update Now
Overview

Snoop Summary for mocospace.com

This is a free and comprehensive report about mocospace.com. The domain mocospace.com is currently hosted on a server located in United States with the IP address 208.95.216.41, where USD is the local currency and the local language is English. Our records indicate that mocospace.com is owned/operated by JNJ Mobile, Inc.. Mocospace.com is expected to earn an estimated $17 USD per day from advertising revenue. The sale of mocospace.com would possibly be worth $12,281 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Mocospace.com is very popular with an estimated 5,898 daily unique visitors. This report was last updated 13th December, 2022.

About mocospace.com

Site Preview: mocospace.com mocospace.com
Title: MocoSpace
Description: A mobile social networking site where people can connect with old friends and make new ones on the Web or on their mobile phones!
Keywords and Tags: popular, social networking
Related Terms:
Fav Icon:
Age: Over 18 years old
Domain Created: 22nd September, 2005
Domain Updated: 10th August, 2015
Domain Expires: 22nd September, 2024
Review

Snoop Score

3/5 (Great!)

Valuation

$12,281 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 88,811
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 5,898
Monthly Visitors: 179,517
Yearly Visitors: 2,152,770
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $17 USD
Monthly Revenue: $512 USD
Yearly Revenue: $6,135 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: mocospace.com 13
Domain Name: mocospace 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.26 seconds
Load Time Comparison: Faster than 67% of sites

PageSpeed Insights

Avg. (All Categories) 74
Performance 67
Accessibility 97
Best Practices 83
SEO 91
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.mocospace.com/login
Updated: 13th December, 2022

1.17 seconds
First Contentful Paint (FCP)
88%
7%
5%

0.01 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
67

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for mocospace.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 2.2 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Mocospace.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mocospace.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mocospace.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mocospace.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mocospace.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn-img.mocospace.com/wk/unify_CSS.jsp?css.unify.0=%2Fstatic%2Fr282354%2Fhtml%2Fcss%2Fdesktop.pack.css&css.unify.1=%2Fstatic%2Fr281008%2Fhtml%2Fcss%2FjqModal.css&css.unify.2=%2Fstatic%2Fr241002%2Fhtml%2Fcss%2Fajax-tooltip-onlinestatus.css&css.unify.3=%2Fstatic%2Fr262109%2Fwk%2Fcss%2Fdialog_sticker_purchase.css&css.unify.4=%2Fstatic%2Fr261285%2Fwk%2Fcss%2Ffonts.css&css.unify.5=%2Fstatic%2Fr232249%2Fwk%2Fcss%2Ffonts-style.css&css.unify.6=%2Fstatic%2Fr270318%2Fhtml%2Fcss%2Fdark-before.css&css.unify.7=%2Fstatic%2Fr282375%2Fhtml%2Fcss%2Fdark.css&css.unify.8=%2Fstatic%2Fr270318%2Fhtml%2Fcss%2Fdark-after.css
12229
11676
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 172 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn-img.mocospace.com/static/r282354/html/images/sprite.png
183985
156214.8
https://cdn-img.mocospace.com/static/r281573/html/images/background.jpg
38029
20328.25
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 170 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.mocospace.com/login
167.375
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mocospace.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://cdn-img.mocospace.com/static/r281573/html/images/background.jpg
0
Avoids enormous network payloads — Total size was 738 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn-img.mocospace.com/static/r282354/html/images/sprite.png
184271
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
164358
https://accounts.google.com/gsi/client
77863
https://www.googletagmanager.com/gtag/js?id=G-ZYE6NDZXXF&l=dataLayer&cx=c
76959
https://www.googletagmanager.com/gtag/js?id=UA-721106-1
45310
https://cdn-img.mocospace.com/static/r282524/html/js/mocospace_en.js
39658
https://cdn-img.mocospace.com/static/r281573/html/images/background.jpg
38314
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
37859
https://cdn-img.mocospace.com/static/r282524/html/js/jquery.min_en.js
29902
https://www.google-analytics.com/analytics.js
20663
Avoids an excessive DOM size — 110 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
110
Maximum DOM Depth
10
Maximum Child Elements
12
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mocospace.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.googletagmanager.com/gtag/js?id=G-ZYE6NDZXXF&l=dataLayer&cx=c
390.902
376.099
6.701
https://www.mocospace.com/login
369.874
63.88
55.95
https://cdn-img.mocospace.com/static/r282524/html/js/jquery.min_en.js
282.68
146.134
2.178
Unattributable
210.569
5.359
0
https://www.googletagmanager.com/gtag/js?id=UA-721106-1
200.755
190.576
8.068
https://cdn-img.mocospace.com/static/r282524/wk/js/ads/uspapi_en.js
198.413
77.032
2.483
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
108.122
97.247
10.681
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
94.66
90.912
3.536
https://accounts.google.com/gsi/client
87.414
13.068
74.122
Minimizes main-thread work — 2.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1106.256
Other
371.762
Style & Layout
252.02
Script Parsing & Compilation
170.903
Rendering
82.857
Parse HTML & CSS
18.518
Garbage Collection
7.418
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 27 requests • 738 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
27
755328
Script
13
507033
Image
4
224426
Stylesheet
4
16478
Document
1
5594
Other
5
1797
Media
0
0
Font
0
0
Third-party
13
436360
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 13 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.googletagmanager.com/gtag/js?id=G-ZYE6NDZXXF&l=dataLayer&cx=c
1823
300
https://cdn-img.mocospace.com/static/r282524/wk/js/ads/uspapi_en.js
994
182
https://www.googletagmanager.com/gtag/js?id=UA-721106-1
1462
107
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
1587
106
https://cdn-img.mocospace.com/static/r282524/html/js/jquery.min_en.js
1693
100
https://cdn-img.mocospace.com/static/r282524/wk/js/ads/uspapi_en.js
1189
99
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
899
95
https://www.googletagmanager.com/gtag/js?id=UA-721106-1
1374
88
https://accounts.google.com/gsi/client
1288
86
https://www.googletagmanager.com/gtag/js?id=G-ZYE6NDZXXF&l=dataLayer&cx=c
2123
86
Unattributable
265
77
Unattributable
190
68
https://www.mocospace.com/login
551
67
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mocospace.com/
http/1.1
0
81.742999958806
197
0
301
text/plain
https://www.mocospace.com/
http/1.1
82.488999934867
309.6169999335
295
0
302
text/html
https://www.mocospace.com/login
http/1.1
310.15899998602
476.5489998972
5594
14226
200
text/html
Document
https://cdn-img.mocospace.com/static/r281573/html/css/index.css
h2
490.46799994539
499.95799991302
1387
2875
200
text/css
Stylesheet
https://accounts.google.com/gsi/client
h2
491.48199998308
583.87400000356
77863
194789
200
application/javascript
Script
https://www.google.com/recaptcha/api.js
h2
800.2329999581
887.27299997117
1143
850
200
text/javascript
Script
https://cdn-img.mocospace.com/wk/unify_CSS.jsp?css.unify.0=%2Fstatic%2Fr282354%2Fhtml%2Fcss%2Fdesktop.pack.css&css.unify.1=%2Fstatic%2Fr281008%2Fhtml%2Fcss%2FjqModal.css&css.unify.2=%2Fstatic%2Fr241002%2Fhtml%2Fcss%2Fajax-tooltip-onlinestatus.css&css.unify.3=%2Fstatic%2Fr262109%2Fwk%2Fcss%2Fdialog_sticker_purchase.css&css.unify.4=%2Fstatic%2Fr261285%2Fwk%2Fcss%2Ffonts.css&css.unify.5=%2Fstatic%2Fr232249%2Fwk%2Fcss%2Ffonts-style.css&css.unify.6=%2Fstatic%2Fr270318%2Fhtml%2Fcss%2Fdark-before.css&css.unify.7=%2Fstatic%2Fr282375%2Fhtml%2Fcss%2Fdark.css&css.unify.8=%2Fstatic%2Fr270318%2Fhtml%2Fcss%2Fdark-after.css
h2
492.64999991283
582.9289999092
12229
55525
200
text/css
Stylesheet
https://cdn-img.mocospace.com/static/r282524/wk/js/ads/usprivacy-string_en.js
h2
493.27499989886
580.14299999923
892
1251
200
application/javascript
Script
https://cdn-img.mocospace.com/static/r282524/wk/js/ads/uspapi_en.js
h2
493.97299997509
499.53099992126
1795
3818
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-721106-1
h2
800.40199996438
888.2019999437
45310
114697
200
application/javascript
Script
https://cdn-img.mocospace.com/static/r282524/html/js/jquery.min_en.js
h2
494.32199995499
577.3909999989
29902
84380
200
application/javascript
Script
https://cdn-img.mocospace.com/static/r282524/html/js/mocospace_en.js
h2
494.50999998953
579.47799994145
39658
144632
200
text/javascript
Script
https://cdn-img.mocospace.com/static/r228345/html/images/no_photo.png
h2
800.55599997286
820.8989999257
1168
777
200
image/png
Image
https://cdn-img.mocospace.com/static/r282524/html/js/index_en.js
h2
778.93899998162
786.21699998621
2710
7152
200
text/javascript
Script
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
h2
798.8989999285
880.86399994791
37859
100177
200
text/javascript
Script
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.css
h2
799.91199995857
880.01500000246
2306
4958
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.js
h2
800.08099996485
886.4229999017
7921
20693
200
application/javascript
Script
https://cdn-img.mocospace.com/static/r282524/html/css/auto_complete.css
h2
793.1910000043
799.03699993156
556
436
200
text/css
Stylesheet
https://cdn-img.mocospace.com/static/r282354/html/images/sprite.png
h2
888.99799995124
896.96399995591
184271
183985
200
image/png
Image
https://cdn-img.mocospace.com/static/r281573/html/images/background.jpg
h2
895.96599992365
901.28899994306
38314
38029
200
image/jpeg
Image
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
h2
1109.8849999253
1190.135999932
164358
410403
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-ZYE6NDZXXF&l=dataLayer&cx=c
h2
1488.1609999575
1577.5759998942
76959
217894
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1502.2289999761
1576.2309998972
20663
50230
200
text/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-ZYE6NDZXXF&gtm=2oebu0&_p=618385026&cid=513110246.1670902195&ul=en-us&sr=800x600&_s=1&sid=1670902195&sct=1&seg=0&dl=https%3A%2F%2Fwww.mocospace.com%2Flogin&dt=Chat%2C%20Meet%20People&en=page_view&_fv=1&_nsi=1&_ss=1
2092.5679999636
2216.6349999607
0
0
-1
Ping
https://www.google-analytics.com/j/collect?v=1&_v=j98&aip=1&a=618385026&t=pageview&_s=1&dl=https%3A%2F%2Fwww.mocospace.com%2Flogin&ul=en-us&de=UTF-8&dt=Chat%2C%20Meet%20People&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YADAAUABAAAAACAAI~&jid=402239484&gjid=665761530&cid=513110246.1670902195&tid=UA-721106-1&_gid=1200935031.1670902195&_r=1&gtm=2oubu0&z=474776704
h2
2215.8289999934
2220.7449999405
616
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j98&tid=UA-721106-1&cid=513110246.1670902195&jid=402239484&gjid=665761530&_gid=1200935031.1670902195&_u=YADAAUAAAAAAACAAI~&z=574062372
h2
2291.7389998911
2295.7549999701
689
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j98&tid=UA-721106-1&cid=513110246.1670902195&jid=402239484&_u=YADAAUAAAAAAACAAI~&z=1921689069
h2
2299.1059999913
2310.3809999302
673
42
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
486.125
19.498
510.828
67.766
586.03
8.223
596.875
181.757
781.201
13.47
802.632
197.268
999.919
7.292
1008.529
85.889
1192.193
9.182
1204.366
94.66
1299.04
88.257
1391.093
5.778
1396.937
106.845
1503.809
84.077
1588.131
17.874
1606.649
76.607
1686.78
106.135
1797.7
299.803
2099.909
86.09
2186.903
31.833
2218.76
65.427
3311.667
67.294
4077.946
100.152
4548.448
29.73
4730.974
47.529
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 590 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mocospace.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://cdn-img.mocospace.com/static/r281573/html/css/index.css
1387
230
Reduce unused JavaScript — Potential savings of 282 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
164358
128521
https://accounts.google.com/gsi/client
77863
62867
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
37859
34490
https://cdn-img.mocospace.com/static/r282524/html/js/mocospace_en.js
39658
33350
https://www.googletagmanager.com/gtag/js?id=G-ZYE6NDZXXF&l=dataLayer&cx=c
76959
29453
Avoid multiple page redirects — Potential savings of 420 ms
Redirects can cause additional delays before the page can begin loading. Mocospace.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mocospace.com/
190
https://www.mocospace.com/
230
https://www.mocospace.com/login
0
Serve static assets with an efficient cache policy — 7 resources found
Mocospace.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://cdn-img.mocospace.com/static/r282524/html/js/jquery.min_en.js
0
29902
https://cdn-img.mocospace.com/static/r282524/wk/js/ads/uspapi_en.js
0
1795
https://cdn-img.mocospace.com/static/r282524/wk/js/ads/usprivacy-string_en.js
0
892
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
3698000
37859
https://www.google-analytics.com/analytics.js
7200000
20663
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.js
604800000
7921
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.css
604800000
2306

Metrics

Total Blocking Time — 590 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

Max Potential First Input Delay — 300 ms
Users could experience a delay when interacting with the page.

Other

Reduce the impact of third-party code — Third-party code blocked the main thread for 430 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
122269
356.46
164358
44.909
79679
24.122
21279
0
10227
0
689
0
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mocospace.com on mobile screens.
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mocospace.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mocospace.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mocospace.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
2.1.4
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://cdn-img.mocospace.com/static/r282524/html/js/jquery.min_en.js
https://cdn-img.mocospace.com/static/r282524/html/js/jquery.min.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://mocospace.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mocospace.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mocospace.com on mobile screens.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mocospace.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mocospace.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 77
Performance 64
Accessibility 90
Best Practices 83
SEO 80
PWA 70
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.mocospace.com/login
Updated: 13th December, 2022

1.08 seconds
First Contentful Paint (FCP)
90%
6%
4%

0.02 seconds
First Input Delay (FID)
94%
5%
1%

Simulate loading on mobile
64

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for mocospace.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0.005
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Mocospace.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mocospace.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mocospace.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mocospace.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 23 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mocospace.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/styles__ltr.css
25184
23699
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 21 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn-img.mocospace.com/static/r281814/wk/images/logo_2x.png
29388
21173.35
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 230 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.mocospace.com/login
234.343
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mocospace.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 20 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.mocospace.com/login
20258
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 768 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
164357
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
164357
https://accounts.google.com/gsi/client
77863
https://cdn-img.mocospace.com/static/r282524/wk/js/mocospace_en.js
53560
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234426_887570&as=zqPaTkBirtFDVIFmdjFCXA
39232
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234416_878483&as=zqPaTkBirtFDVIFmdjFCXA
39225
https://www.googletagmanager.com/gtag/js?id=null
38168
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
37859
https://cdn-img.mocospace.com/static/r281814/wk/images/logo_2x.png
29672
https://fonts.gstatic.com/s/googlesans/v14/4UabrENHsxJlGDuGo1OIlLU94YtzCwM.ttf
28404
Avoids an excessive DOM size — 185 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
185
Maximum DOM Depth
14
Maximum Child Elements
38
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mocospace.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 26 requests • 768 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
26
786505
Script
7
491674
Document
4
113978
Other
7
67331
Font
3
51796
Image
2
32772
Stylesheet
3
28954
Media
0
0
Third-party
18
678031
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0048307291666667
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 19 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
7505
242
https://accounts.google.com/gsi/client
4409
227
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
1862
190
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
7793
145
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LeoN-oZAAAAAOMVUZ7Q5by7KSBY2wewHMztgXJZ&co=aHR0cHM6Ly93d3cubW9jb3NwYWNlLmNvbTo0NDM.&hl=en&v=pn3ro1xnhf4yB8qmnrhh9iD2&size=invisible&sa=signup_wk&cb=8n5sji5iocd5
6114
144
https://www.googletagmanager.com/gtag/js?id=null
3629
111
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
7409
96
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234416_878483&as=zqPaTkBirtFDVIFmdjFCXA
5229
93
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234426_887570&as=zqPaTkBirtFDVIFmdjFCXA
5759
90
https://www.mocospace.com/login
1692
87
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
7938
87
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.js
2670
77
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
3740
74
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234416_878483&as=zqPaTkBirtFDVIFmdjFCXA
5159
70
Unattributable
682
61
https://www.mocospace.com/login
1590
59
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LeoN-oZAAAAAOMVUZ7Q5by7KSBY2wewHMztgXJZ&co=aHR0cHM6Ly93d3cubW9jb3NwYWNlLmNvbTo0NDM.&hl=en&v=pn3ro1xnhf4yB8qmnrhh9iD2&size=invisible&sa=signup_wk&cb=8n5sji5iocd5
6059
55
Unattributable
630
52
https://www.mocospace.com/login
1779
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mocospace.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mocospace.com/
http/1.1
0
46.946000074968
171
0
301
text/plain
https://www.mocospace.com/
http/1.1
47.419999958947
264.809000073
783
0
302
text/html
https://www.mocospace.com/login
http/1.1
265.15999995172
498.51000006311
12303
35176
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=null
h2
515.2980000712
550.46800011769
38168
95042
200
application/javascript
Script
https://www.google.com/recaptcha/api.js
h2
515.94000007026
552.02000006102
1143
850
200
text/javascript
Script
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
h2
516.10599993728
560.35599997267
37859
100177
200
text/javascript
Script
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.css
h2
516.19899994694
539.22299994156
2298
4958
200
text/css
Stylesheet
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.js
h2
516.66900003329
539.60000001825
7927
20693
200
application/javascript
Script
https://cdn-img.mocospace.com/static/r282524/wk/js/mocospace_en.js
h2
531.54999995604
552.55299992859
53560
0
200
text/javascript
Other
https://cdn-img.mocospace.com/static/r282524/wk/js/people-listing_en.js
h2
531.68200002983
551.14399990998
5350
0
200
text/javascript
Other
https://cdn-img.mocospace.com/wk/unify_CSS.jsp?filter=not_abf&css.unify.0=%2Fstatic%2Fr282237%2Fwk%2Fcss%2Fpeople.css&css.unify.1=%2Fstatic%2Fr280159%2Fwk%2Fcss%2Fpeople-listing.css&css.unify.2=%2Fstatic%2Fr279381%2Fwk%2Fcss%2Fpagination.css
h2
531.77100000903
551.35599989444
1424
0
200
text/css
Other
https://cdn-img.mocospace.com/wk/unify_CSS.jsp?filter=not_abf&css.unify.0=%2Fstatic%2Fr282069%2Fwk%2Fcss%2Fwebkit.pack.css&css.unify.1=%2Fstatic%2Fr282164%2Fwk%2Fcss%2Fad-core.css
h2
531.85999998823
550.92000006698
5211
0
200
text/css
Other
https://cdn-img.mocospace.com/static/r281814/wk/images/logo_2x.png
h2
557.7110000886
569.07800002955
29672
29388
200
image/png
Image
data
567.15800007805
567.29299994186
0
266
200
image/svg+xml
Image
https://accounts.google.com/gsi/client
h2
616.13099998794
669.46100001223
77863
194789
200
application/javascript
Script
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
h2
645.30299999751
670.72400008328
164357
410403
200
text/javascript
Script
https://accounts.google.com/gsi/style
h2
764.16200003587
789.43199990317
1472
533
200
text/css
Stylesheet
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234416_878483&as=zqPaTkBirtFDVIFmdjFCXA
h2
770.89500008151
834.40800011158
39225
106494
200
text/html
Document
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234426_887570&as=zqPaTkBirtFDVIFmdjFCXA
h2
782.62499999255
871.77899992093
39232
106494
200
text/html
Document
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LeoN-oZAAAAAOMVUZ7Q5by7KSBY2wewHMztgXJZ&co=aHR0cHM6Ly93d3cubW9jb3NwYWNlLmNvbTo0NDM.&hl=en&v=pn3ro1xnhf4yB8qmnrhh9iD2&size=invisible&sa=signup_wk&cb=8n5sji5iocd5
h2
887.98000011593
937.40499997512
23218
44333
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/styles__ltr.css
h2
988.81500004791
1002.6420000941
25184
52913
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
h2
989.6899999585
1011.3329999149
164357
410403
200
text/javascript
Script
https://fonts.gstatic.com/s/googlesans/v14/4UabrENHsxJlGDuGo1OIlLU94YtzCwM.ttf
h2
1030.463000061
1038.1159998942
28404
51972
200
font/ttf
Font
https://www.gstatic.com/recaptcha/api2/logo_48.png
h2
1151.346999919
1157.1279999334
3100
2228
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1153.3190000337
1159.1680001002
11676
10748
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
1155.107999919
1159.4680000562
11716
10788
200
font/woff2
Font
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=pn3ro1xnhf4yB8qmnrhh9iD2
h2
1179.3670000043
1201.0280000977
832
102
200
text/javascript
Other
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
507.18
14.87
522.356
10.715
533.501
9.03
542.54
43.601
586.925
25.065
613.482
12.957
628.941
8.289
639.65
27.874
668.478
18.475
693.819
19.167
720.882
56.854
777.806
16.729
798.317
94.825
897.001
17.544
914.569
8.985
926.781
23.288
950.363
22.401
973.343
13.743
987.104
11.726
1011.429
8.832
1020.291
7.039
1029.353
5.677
1056.951
5.957
1077.184
24.045
1101.71
60.402
1167.019
10.475
1179.517
35.969
1217.144
12.352
1234.136
72.574
1306.814
5.358
1322.001
15.291
1337.305
43.488
1385.995
12.648
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.3 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 240 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.4 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 650 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mocospace.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.css
2298
780
Serve static assets with an efficient cache policy — 4 resources found
Mocospace.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
3698000
37859
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.js
604800000
7927
https://www.gstatic.com/recaptcha/api2/logo_48.png
604800000
3100
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.css
604800000
2298
Reduce JavaScript execution time — 2.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
1024.256
782.928
118.048
https://www.mocospace.com/login
740.832
216.916
20.252
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LeoN-oZAAAAAOMVUZ7Q5by7KSBY2wewHMztgXJZ&co=aHR0cHM6Ly93d3cubW9jb3NwYWNlLmNvbTo0NDM.&hl=en&v=pn3ro1xnhf4yB8qmnrhh9iD2&size=invisible&sa=signup_wk&cb=8n5sji5iocd5
455.612
361.58
12.212
Unattributable
267.292
6.3
0
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234426_887570&as=zqPaTkBirtFDVIFmdjFCXA
214.648
47.416
41.848
https://accounts.google.com/gsi/client
205.996
114.324
28.964
https://accounts.google.com/gsi/button?theme=filled_blue&size=large&width=0&client_id=505839483613.apps.googleusercontent.com&iframe_id=gsi_234416_878483&as=zqPaTkBirtFDVIFmdjFCXA
176.776
50.024
78.008
https://www.googletagmanager.com/gtag/js?id=null
139.68
123.384
7.252
/_/gsi/_/js/k=gsi.gsi.en_US.TOmXd8heOhk.O/am=ag/d=1/rs=AF0KOtUzbN1wsccnopkIH2g7oiyaJseGFA/m=credential_button_library
100.796
83.372
0
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
73.9
29.888
43.32
https://cdn.jsdelivr.net/npm/cookieconsent@3/build/cookieconsent.min.js
73.344
70.484
1.692
Minimize main-thread work — 3.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1890.236
Other
437.084
Style & Layout
386.256
Script Parsing & Compilation
352.104
Rendering
226.352
Parse HTML & CSS
158.948
Garbage Collection
36.28

Metrics

Time to Interactive — 7.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 680 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Reduce unused JavaScript — Potential savings of 196 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/pn3ro1xnhf4yB8qmnrhh9iD2/recaptcha__en.js
164357
87027
https://accounts.google.com/gsi/client
77863
54744
https://fpcdn.io/v3/gF2Toq6eljIhFGDjTOvS/iife.min.js
37859
34490
https://www.googletagmanager.com/gtag/js?id=null
38168
24886
Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Mocospace.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mocospace.com/
630
https://www.mocospace.com/
780
https://www.mocospace.com/login
0
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/googlesans/v14/4UabrENHsxJlGDuGo1OIlLU94YtzCwM.ttf
7.6529998332262
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
5.8490000665188
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
4.3600001372397
Reduce the impact of third-party code — Third-party code blocked the main thread for 730 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
356998
420.16
182985
236.668
38168
53.448
10225
19.128
51796
0
First Contentful Paint (3G) — 4620 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
90

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mocospace.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mocospace.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that mocospace.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://mocospace.com/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 400 (Bad Request)
Failed to load resource: the server responded with a status of 400 (Bad Request)
TypeError: Cannot read properties of undefined (reading 'mb') at bj.l (/_/gsi/_/js/k=gsi.gsi.en_US.TOmXd8heOhk.O/am=ag/d=1/rs=AF0KOtUzbN1wsccnopkIH2g7oiyaJseGFA/m=credential_button_library:329:40)
TypeError: Cannot read properties of undefined (reading 'mb') at bj.l (/_/gsi/_/js/k=gsi.gsi.en_US.TOmXd8heOhk.O/am=ag/d=1/rs=AF0KOtUzbN1wsccnopkIH2g7oiyaJseGFA/m=credential_button_library:329:40)
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mocospace.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mocospace.com on mobile screens.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 64% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
13x13
38x28
45x28
47x28
52x28

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Mobile Friendly

Document doesn't use legible font sizes — 52.39% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.terms
44.41%
11px
footer
2.32%
11px
.rc-anchor-normal .rc-anchor-pt, .rc-anchor-invisible .rc-anchor-pt, .rc-anchor-compact .rc-anchor-pt
0.68%
8px
.password_toggle
0.19%
11px
52.39%
≥ 12px

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
70

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mocospace.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mocospace.com on mobile screens.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 208.95.216.41
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
JNJ Mobile, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: JNJ Mobile, Inc.
Country: US
City:
State: Massachusetts
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.203.184.117
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 85/100
WOT Child Safety: 69/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.mocospace.com
Issued By: Go Daddy Secure Certificate Authority - G2
Valid From: 1st July, 2022
Valid To: 2nd August, 2023
Subject: CN = *.mocospace.com
Hash: a4ba3cbd
Issuer: CN = Go Daddy Secure Certificate Authority - G2
OU = http://certs.godaddy.com/repository/
O = GoDaddy.com, Inc.
S = US
Version: 2
Serial Number: 5961730497184415344
Serial Number (Hex): 52BC524CF34A3E70
Valid From: 1st July, 2024
Valid To: 2nd August, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:40:C2:BD:27:8E:CC:34:83:30:A2:33:D7:FB:6C:B3:F0:B4:2C:80:CE
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.godaddy.com/gdig2s1-4246.crl

Certificate Policies: Policy: 2.16.840.1.114413.1.7.23.1
CPS: http://certificates.godaddy.com/repository/
Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.godaddy.com/
CA Issuers - URI:http://certificates.godaddy.com/repository/gdig2.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Jul 1 11:13:11.465 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:70:8C:A5:51:A7:96:DD:E0:0C:77:BB:9E:
A5:E5:15:B8:91:F6:97:4C:10:6D:9F:CF:9C:38:0E:D1:
7C:31:20:5D:02:21:00:A5:33:E6:F0:49:0B:5C:28:10:
15:13:6C:F4:38:D3:61:28:DC:D7:15:B3:A2:BA:63:44:
AA:04:A7:D4:03:91:FD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Jul 1 11:13:11.746 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7A:36:CE:2C:79:FC:FD:59:82:08:91:3B:
7D:54:DD:F1:97:2E:BC:76:5B:14:09:72:88:D1:E3:54:
35:6B:41:6F:02:21:00:FA:8C:0C:43:36:02:F3:96:48:
14:BE:C7:0E:05:D8:B6:B1:D8:36:8F:E6:F4:6E:7A:B1:
AD:6D:F8:9A:A1:B0:AC
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Jul 1 11:13:11.849 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:1F:42:3B:83:2F:A6:7A:C6:84:65:A8:F6:68:
C3:D6:BF:36:5F:24:BC:6B:B7:0C:00:8B:F4:92:58:5F:
34:52:75:02:21:00:D3:F7:46:95:6B:0A:1E:F9:44:9E:
8B:97:31:03:4D:AA:6A:7B:35:94:2E:D8:EF:4D:48:5D:
7C:D7:35:87:6F:29
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mocospace.com
DNS:*.mocospace.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mocospace.com. 208.95.216.41 IN 21600

NS Records

Host Nameserver Class TTL
mocospace.com. global-ns1.mocospace.com. IN 21600
mocospace.com. global-ns2.mocospace.com. IN 21600
mocospace.com. global-ns3.mocospace.com. IN 21600
mocospace.com. global-ns4.mocospace.com. IN 21600

MX Records

Priority Host Server Class TTL
10 mocospace.com. mx02.mocospace.com. IN 21600
10 mocospace.com. mx03.mocospace.com. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
mocospace.com. global-ns1.mocospace.com. ops.corp.mocospace.com. 21600

TXT Records

Host Value Class TTL
mocospace.com. v=spf1 IN 300

HTTP Response Headers

Whois Lookup

Created: 22nd September, 2005
Changed: 10th August, 2015
Expires: 22nd September, 2024
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: global-ns1.mocospace.com
global-ns2.mocospace.com
global-ns3.mocospace.com
global-ns4.mocospace.com
Owner Name: Jamieson Hall
Owner Organization: JNJ Mobile, Inc.
Owner Street: 6 Liberty Sq PMB 96493
Owner Post Code: 02109
Owner City: Boston
Owner State: Massachusetts
Owner Country: US
Owner Phone: +1.6175421614
Owner Email: webmaster@corp.mocospace.com
Admin Name: Jamieson Hall
Admin Organization: JNJ Mobile, Inc.
Admin Street: 6 Liberty Sq PMB 96493
Admin Post Code: 02109
Admin City: Boston
Admin State: Massachusetts
Admin Country: US
Admin Phone: +1.6175421614
Admin Email: webmaster@corp.mocospace.com
Tech Name: Jamieson Hall
Tech Organization: JNJ Mobile, Inc.
Tech Street: 6 Liberty Sq PMB 96493
Tech Post Code: 02109
Tech City: Boston
Tech State: Massachusetts
Tech Country: US
Tech Phone: +1.6175421614
Tech Email: webmaster@corp.mocospace.com
Full Whois: Domain Name: MOCOSPACE.COM
Registry Domain ID: 214199255_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2015-08-10T21:36:03Z
Creation Date: 2005-09-22T14:56:13Z
Registrar Registration Expiration Date: 2024-09-22T14:56:13Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Jamieson Hall
Registrant Organization: JNJ Mobile, Inc.
Registrant Street: 6 Liberty Sq PMB 96493
Registrant City: Boston
Registrant State/Province: Massachusetts
Registrant Postal Code: 02109
Registrant Country: US
Registrant Phone: +1.6175421614
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: webmaster@corp.mocospace.com
Registry Admin ID: Not Available From Registry
Admin Name: Jamieson Hall
Admin Organization: JNJ Mobile, Inc.
Admin Street: 6 Liberty Sq PMB 96493
Admin City: Boston
Admin State/Province: Massachusetts
Admin Postal Code: 02109
Admin Country: US
Admin Phone: +1.6175421614
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: webmaster@corp.mocospace.com
Registry Tech ID: Not Available From Registry
Tech Name: Jamieson Hall
Tech Organization: JNJ Mobile, Inc.
Tech Street: 6 Liberty Sq PMB 96493
Tech City: Boston
Tech State/Province: Massachusetts
Tech Postal Code: 02109
Tech Country: US
Tech Phone: +1.6175421614
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: webmaster@corp.mocospace.com
Name Server: GLOBAL-NS1.MOCOSPACE.COM
Name Server: GLOBAL-NS2.MOCOSPACE.COM
Name Server: GLOBAL-NS3.MOCOSPACE.COM
Name Server: GLOBAL-NS4.MOCOSPACE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-12-13T03:29:44Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
global-ns1.mocospace.com 205.251.192.107
global-ns2.mocospace.com 205.251.195.158
global-ns3.mocospace.com 205.251.197.232
global-ns4.mocospace.com 205.251.199.200
Related

Subdomains

Domain Subdomain
m
ww

Similar Sites

Domain Valuation Snoop Score
$11,001 USD 2/5
$8,921 USD 3/5
$9,584 USD 2/5
$1,023 USD 2/5
$12,895 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address