Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

wikiwiki.jp

wikiwiki.jp is SSL secured

Free website and domain report on wikiwiki.jp

Last Updated: 21st January, 2022 Update Now
Overview

Snoop Summary for wikiwiki.jp

This is a free and comprehensive report about wikiwiki.jp. The domain wikiwiki.jp is currently hosted on a server located in Tokyo, Tokyo in Japan with the IP address 3.112.121.254, where the local currency is JPY and Japanese is the local language. Our records indicate that wikiwiki.jp is privately registered by Whois Privacy Protection Service by onamae.com. Wikiwiki.jp is expected to earn an estimated $6,058 USD per day from advertising revenue. The sale of wikiwiki.jp would possibly be worth $4,422,375 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Wikiwiki.jp is insanely popular with an estimated 650,641 daily unique visitors. This report was last updated 21st January, 2022.

About wikiwiki.jp

Site Preview: wikiwiki.jp wikiwiki.jp
Title: 無料 レンタル Wiki サービス WIKIWIKI
Description:
Keywords and Tags: eso wiki, iruna jp wiki, outward wiki, pandora saga wiki jp, personal pages, popular, u 511 艦 これ, warframe wiki, zenith warframe, かん これ, なん, なん j, スプラ wiki, ヒューストン, 夢 100 オリオン, 艦 これ wiki
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

4/5 (Excellent!)

Valuation

$4,422,375 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,588
Alexa Reach: 0.0160%
SEMrush Rank (US): 45,179
SEMrush Authority Score: 76
Moz Domain Authority: 60
Moz Page Authority: 54

Rank By Country

Country Alexa Rank
Hong Kong Flag Hong Kong 2,748
Japan Flag Japan 353
United States Flag United States 15,260

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 60,060 0
Traffic: 47,932 0
Cost: $2,096 USD $0 USD
Traffic

Visitors

Daily Visitors: 650,641
Monthly Visitors: 19,803,462
Yearly Visitors: 237,483,965
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Hong Kong Flag Hong Kong Daily: 8,458
Monthly: 257,445
Yearly: 3,087,292 		1.3%
Japan Flag Japan Daily: 581,673
Monthly: 17,704,295
Yearly: 212,310,665 		89.4%
Other Daily: 14,965
Monthly: 455,480
Yearly: 5,462,131 		2.3%
United States Flag United States Daily: 45,545
Monthly: 1,386,242
Yearly: 16,623,878 		7%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $6,058 USD
Monthly Revenue: $184,387 USD
Yearly Revenue: $2,211,182 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Hong Kong Flag Hong Kong Daily: $5 USD
Monthly: $158 USD
Yearly: $1,895 USD 		0.1%
Japan Flag Japan Daily: $1,375 USD
Monthly: $41,864 USD
Yearly: $502,033 USD 		22.7%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD 		<0.1%
United States Flag United States Daily: $4,677 USD
Monthly: $142,366 USD
Yearly: $1,707,255 USD 		77.2%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 16,525,093
Referring Domains: 8,653
Referring IPs: 15,061
Wikiwiki.jp has 16,525,093 backlinks according to SEMrush. 88% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve wikiwiki.jp's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of wikiwiki.jp's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: http://blog.livedoor.jp/plhfmbe/
Target: https://wikiwiki.jp/livejupiter/%E3%83%89%E3%83%B3%E3%82%AF%E3%83%A9%E3%82%A4(%E6%B3%A3%E3%81%8F%E3%81%AE%E3%81%AF%E3%81%8A%E3%82%88%E3%81%97)
2
Source: http://sidem.clover-search.com/2016/09/27/2014hjs-special-summer/
Target: https://wikiwiki.jp/sidem/%EF%BE%8A%EF%BE%9E%EF%BE%9A%EF%BE%9D%EF%BE%80%EF%BD%B2%EF%BE%9D%EF%BE%83%EF%BE%9E%EF%BD%B0%EF%BD%B7%EF%BD%AC%EF%BE%9D%EF%BE%8D%EF%BE%9F%EF%BD%B0%EF%BE%9D%20%E6%84%9B%E6%83%85%E3%81%9F%E3%81%A3%E3%81%B7%E3%82%8A!315%EF%BD%B6%EF%BD%B6%EF%BD%B5%E8%82%B2%E6%88%90%E5%A4%A7%E4%BD%9C%E6%88%A6!
3
Source: https://search.goo.ne.jp/web.jsp?IE=sjis&MT=%83h%83%89%83S%83%93%83e%83C%83%8B%81%40%81%40DS&PT=isaonet&btnG=%8C%9F%8D%F5&from=isaonet
Target: https://wikiwiki.jp/dqdic3rd/%E3%80%90%E3%81%AF%E3%81%8C%E3%81%AD%E3%81%AE%E3%83%A0%E3%83%81%E3%80%91
4
Source: https://search.goo.ne.jp/web.jsp?IE=sjis&MT=%83h%83%89%83S%83%93%83e%83C%83%8B%81%40%81%40DS&PT=isaonet&btnG=%8C%9F%8D%F5&from=isaonet
Target: https://wikiwiki.jp/dqdic3rd/%E3%80%90%E3%81%AF%E3%81%8C%E3%81%AD%E3%81%AE%E3%83%A0%E3%83%81%E3%80%91
5
Source: https://search.goo.ne.jp/web.jsp?IE=utf-8&MT=%E5%8A%A0%E8%97%A4%E3%82%B3%E3%83%9F%E3%83%83%E3%82%B7%E3%83%A7%E3%83%8A%E3%83%BC&PT=nikkansports&from=nikkansports
Target: https://wikiwiki.jp/livejupiter/%E3%82%AB%E3%83%83%E3%83%88%E3%83%AC

Top Ranking Keywords (US)

1
Keyword: なん j
Ranked Page: https://wikiwiki.jp/livejupiter/%E3%81%AA%E3%82%93J%E3%83%8D%E3%82%BF%E5%B9%B4%E8%A1%A8
2
Keyword: warframe wiki
Ranked Page: https://wikiwiki.jp/warframe/
3
Keyword: なん
Ranked Page: https://wikiwiki.jp/livejupiter/
4
Keyword: なん
Ranked Page: https://wikiwiki.jp/livejupiter/%E3%81%AA%E3%82%93J%E3%83%8D%E3%82%BF%E5%B9%B4%E8%A1%A8
5
Keyword: eso wiki
Ranked Page: https://wikiwiki.jp/tesowiki/

Domain Analysis

Value Length
Domain: wikiwiki.jp 11
Domain Name: wikiwiki 8
Extension (TLD): jp 2

Page Speed Analysis

Average Load Time: 0.46 seconds
Load Time Comparison: Faster than 96% of sites

PageSpeed Insights

Avg. (All Categories) 74
Performance 79
Accessibility 95
Best Practices 85
SEO 91
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://wikiwiki.jp/
Updated: 21st January, 2022

0.60 seconds
First Contentful Paint (FCP)
93%
4%
3%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
79

Performance

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

Metrics

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 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).
Cumulative Layout Shift — 0.012
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
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://wikiwiki.jp/
http/1.1
0
330.74299991131
270
0
301
text/html
https://wikiwiki.jp/
h2
331.04499988258
1299.6900007129
50858
50495
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-19502774-1
h2
1312.5809999183
1324.919000268
37286
92933
200
application/javascript
Script
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
h2
1312.9080003127
2927.6950005442
312345
312100
200
text/css
Stylesheet
https://wikiwiki.jp/pa/img/logo.png
h2
1318.2830000296
2272.7040005848
62002
61781
200
image/png
Image
https://wikiwiki.jp/pa/img/icon-setting-white.png
h2
1318.57100036
1952.7139998972
2938
2719
200
image/png
Image
https://wikiwiki.jp/pa/img/icon-menu-white.png
h2
1318.7610004097
1952.395000495
912
694
200
image/png
Image
https://wikiwiki.jp/pa/img/main-visual.jpg
h2
1319.005000405
2762.6470001414
752501
752277
200
image/jpeg
Image
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
h2
1319.171000272
2917.1980004758
677399
677175
200
image/jpeg
Image
https://wikiwiki.jp/pa/img/wikiwiki_game_logo.png
h2
1319.2930007353
2597.9100000113
13188
12967
200
image/png
Image
https://platform.twitter.com/widgets.js
http/1.1
1319.5670004934
1375.5670003593
29709
98744
200
application/javascript
Script
https://cse.google.com/cse.js?cx=bcf91dfa96f3c4721
h2
1317.89100077
1378.4380005673
4140
10257
200
text/javascript
Script
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
h2
1318.1060003117
2918.7610000372
148101
147842
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1351.2180000544
1355.8380007744
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=784779698&t=pageview&_s=1&dl=https%3A%2F%2Fwikiwiki.jp%2F&ul=en-us&de=UTF-8&dt=%E7%84%A1%E6%96%99%20%E3%83%AC%E3%83%B3%E3%82%BF%E3%83%AB%20Wiki%20%E3%82%B5%E3%83%BC%E3%83%93%E3%82%B9%20WIKIWIKI&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=1608706725&gjid=343611339&cid=1514509435.1642758253&tid=UA-19502774-1&_gid=763713011.1642758253&_r=1&gtm=2ou1j0&z=1325581552
h2
1522.9660002515
1526.6460003331
609
1
200
text/plain
XHR
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
h2
2953.1670007855
3901.8149999902
556303
556068
200
application/font-woff
Font
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-btn-primary.png
h2
2953.5860000178
3134.279999882
1448
1229
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16-pc.png
h2
2954.4520005584
3600.2879999578
167324
167101
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/header-back.png
h2
2954.824000597
3132.6220007613
2027
1808
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/h2.png
h2
2956.4390005544
3125.2870000899
638
420
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-recent-wiki.png
h2
2956.8810006604
3133.9710000902
20603
20382
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-hot-wiki.png
h2
2958.0860007554
3275.7020005956
20759
20538
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/purpose.png
h2
2962.625999935
3599.0329999477
293
77
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-for-beginner.png
h2
2963.010000065
3124.2970004678
870
652
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-contact.png
h2
2963.6900005862
3144.2929999903
870
652
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-btn-secondary.png
h2
2964.4010001794
3437.9790006205
1328
1109
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
h2
2965.9090004861
3597.9369999841
550139
549904
200
application/font-woff
Font
https://wikiwiki.jp/pa/assets/_6c9a1b73/webfonts/fa-solid-900.woff2
h2
2966.2279998884
3439.3390007317
141838
141600
200
application/octet-stream
Font
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
h2
2971.6180004179
3143.1730007753
551507
551272
200
application/font-woff
Font
https://www.google.com/cse/static/element/ff97a008b4153450/cse_element__ja.js?usqp=CAM%3D
h2
3005.8510005474
3015.6610002741
103345
309124
200
text/javascript
Script
https://www.google.com/cse/static/element/ff97a008b4153450/default+ja.css
h2
3007.3000006378
3013.6259999126
10010
41765
200
text/css
Stylesheet
https://www.google.com/cse/static/style/look/v4/minimalist.css
h2
3008.832000196
3013.0449999124
2370
5084
200
text/css
Stylesheet
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
http/1.1
3034.7540006042
3126.6590002924
105957
327158
200
text/html
Document
https://cse.google.com/adsense/search/async-ads.js
h2
3133.0770002678
3151.1949999258
51855
139240
200
text/javascript
Script
https://www.google.com/cse/static/css/v2/clear.png
h2
3153.9110001177
3157.8090004623
1896
1018
200
image/png
Image
https://www.googleapis.com/generate_204
h2
3166.3960004225
3170.2330000699
224
0
204
text/plain
Image
https://clients1.google.com/generate_204
h2
3167.6300000399
3170.8170007914
224
0
204
text/plain
Image
https://syndication.twitter.com/settings?session_id=009cf5639fbca9c3324aa7bd997609587102ba3d
h2
3281.6900005564
3318.0539999157
680
233
200
application/json
Fetch
https://platform.twitter.com/js/moment~timeline.4391e0bf4053fbaa2a022e3fad2a1e1a.js
http/1.1
3326.96400024
3381.3350005075
8547
25494
200
application/javascript
Script
https://platform.twitter.com/js/timeline.34cf38a85ac899f1d6a0438a1659decc.js
http/1.1
3327.5700006634
3381.9700004533
6979
20656
200
application/javascript
Script
https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_WIKIWIKI_Japan_old&dnt=false&domain=wikiwiki.jp&lang=ja&screen_name=WIKIWIKI_Japan&suppress_response_codes=true&t=1825286&tz=GMT-0800&with_replies=false
h2
3396.8640007079
3505.01000043
9167
109909
200
application/javascript
Script
https://pbs.twimg.com/card_img/1481970749149569024/AltvAgmc?format=png&name=144x144_2
h2
3531.3730007038
3547.4430005997
8921
8222
200
image/png
Image
https://platform.twitter.com/css/timeline.2fcb295ab98c2ce26f4cca0d2b2d0f48.light.ltr.css
http/1.1
3531.960000284
3588.7210005894
12666
53760
200
text/css
Stylesheet
https://platform.twitter.com/css/timeline.2fcb295ab98c2ce26f4cca0d2b2d0f48.light.ltr.css
http/1.1
3533.3230001852
3686.3910006359
12666
53760
200
text/css
Image
https://pbs.twimg.com/profile_images/830311384021766145/8HU4JUSZ_normal.jpg
h2
3594.2200003192
3609.6120001748
2904
2187
200
image/jpeg
Image
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
h2
3595.9320003167
3613.8019999489
7512
45170
200
text/css
Stylesheet
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
h2
3597.0160001889
3691.5020002052
7512
45170
200
text/css
Image
data
3602.076000534
3602.2470006719
0
512
200
image/svg+xml
Image
data
3604.6569999307
3604.7750003636
0
825
200
image/svg+xml
Image
data
3606.7470004782
3606.8580001593
0
572
200
image/svg+xml
Image
data
3608.2180002704
3608.3090007305
0
644
200
image/svg+xml
Image
https://syndication.twitter.com/i/jot
http/1.1
4014.4009999931
4093.5180000961
753
0
302
text/html
https://platform.twitter.com/jot.html
http/1.1
4094.0380003303
4147.7910000831
570
80
200
text/html
Document
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)
1341.148
7.305
1349.187
5.076
1371.469
7.819
1380.037
9.679
1399.4
162.596
1567.866
15.465
2967.922
15.131
2983.306
57.753
3041.072
32.408
3073.949
26.398
3111.544
33.037
3145.253
58.851
3205.203
6.939
3212.152
6.547
3232.311
18.565
3254.524
19.848
3274.904
7.85
3284.234
36.318
3358.528
7.675
3424.554
11.253
3435.819
13.765
3478.863
11.389
3490.313
22.798
3547.209
22.082
3569.304
7.014
3633.364
91.133
3730.254
22.004
3756.041
6.339
3763.456
18.388
3781.93
27.236
3809.974
8.208
3839.384
7.321
3865.753
8.147
3942.367
23.893
4015.627
11.145
4032.294
11.648
4044.105
5.678
4188.654
5.833
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.

Other

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wikiwiki.jp 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://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312345
640
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wikiwiki.jp should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wikiwiki.jp should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/cse/static/element/ff97a008b4153450/default+ja.css
10010
3041
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wikiwiki.jp should consider minifying JS files.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Wikiwiki.jp should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wikiwiki.jp/
190
https://wikiwiki.jp/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wikiwiki.jp 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 0 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://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
167
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids an excessive DOM size — 677 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
677
Maximum DOM Depth
×
22
Maximum Child Elements
2022-01-21 18:39:57 電子海のはなし Wiki* 2022-01-21 18:39:45 ドリームレジェンドアニメファイタークロニクル Wi…
100
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wikiwiki.jp 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 — 0.1 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://platform.twitter.com/widgets.js
242.217
73.676
4.553
https://wikiwiki.jp/
219.164
8.446
1.076
https://www.google-analytics.com/analytics.js
163.912
19.567
0.919
Unattributable
117.769
3.404
0.123
Minimizes main-thread work — 1.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)
Style & Layout
377.777
Script Evaluation
222.483
Other
203.706
Rendering
81.838
Parse HTML & CSS
55.823
Script Parsing & Compilation
41.57
Garbage Collection
5.639
Keep request counts low and transfer sizes small — 49 requests • 4,379 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
49
4483594
Font
4
1799787
Image
23
1759447
Script
10
419760
Stylesheet
5
344903
Document
3
157385
Other
4
2312
Media
0
0
Third-party
25
447133
Minimize third-party usage — Third-party code blocked the main thread for 100 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)
SHOW DETAILS
21240
87.208
SHOW DETAILS
214543
16.232
SHOW DETAILS
173616
0
SHOW DETAILS
37286
0
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
オーバースペックでご提供！ WIKIWIKIは世界で最も速いレンタルWIKIサービスを目指しています。
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
オーバースペックでご提供！ WIKIWIKIは世界で最も速いレンタルWIKIサービスを目指しています。
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
埋め込む Twitterで表示
0.13529411764706
お知らせ WIKIWIKIの最新情報をTwitterで配信しています。 初めての方へ WIKIWIKIの特徴 お試しWIKI サンプルWIKI デザインテ…
0.008892610104194
Tweets by WIKIWIKI_Japan
0.0026034848086858
WIKIの設定 ・ 新規登録
4.0517847852247E-5
WIKI 検索
3.2669666982849E-5
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 — 1 long task 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.google-analytics.com/analytics.js
1010
81
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 wikiwiki.jp on mobile screens.

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.

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.

Audits

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

Other

Properly size images — Potential savings of 530 KiB
Images can slow down the page's load time. Wikiwiki.jp should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
677175
498512
https://wikiwiki.jp/pa/img/logo.png
61781
32920
https://wikiwiki.jp/pa/img/wikiwiki_game_logo.png
12967
11067
Reduce unused CSS — Potential savings of 291 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wikiwiki.jp 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://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312345
297759
Reduce unused JavaScript — Potential savings of 294 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://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
148101
104600
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
105911
102218
https://www.google.com/cse/static/element/ff97a008b4153450/cse_element__ja.js?usqp=CAM%3D
103345
51817
https://cse.google.com/adsense/search/async-ads.js
51855
42176
Efficiently encode images — Potential savings of 454 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
677175
261678
https://wikiwiki.jp/pa/img/main-visual.jpg
752277
203615
Enable text compression — Potential savings of 394 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312100
254584
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
147842
105517
https://wikiwiki.jp/
50495
43705

Metrics

Speed Index — 2.5 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.5 s
The timing of the largest text or image that is painted.

Other

Serve images in next-gen formats — Potential savings of 1,174 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://wikiwiki.jp/pa/img/main-visual.jpg
752277
516115.5
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
677175
493799.15
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16-pc.png
167101
114517.15
https://wikiwiki.jp/pa/img/logo.png
61781
45643.45
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-hot-wiki.png
20538
16066.6
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-recent-wiki.png
20382
15825.9
Reduce initial server response time — Root document took 970 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://wikiwiki.jp/
969.638
Avoid enormous network payloads — Total size was 4,379 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://wikiwiki.jp/pa/img/main-visual.jpg
752501
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
677399
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
556303
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
551507
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
550139
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312345
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16-pc.png
167324
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
148101
https://wikiwiki.jp/pa/assets/_6c9a1b73/webfonts/fa-solid-900.woff2
141838
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
105957
Serve static assets with an efficient cache policy — 28 resources found
Wikiwiki.jp 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://wikiwiki.jp/pa/img/main-visual.jpg
0
752501
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
0
677399
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
0
556303
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
0
551507
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
0
550139
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
0
312345
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16-pc.png
0
167324
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
0
148101
https://wikiwiki.jp/pa/assets/_6c9a1b73/webfonts/fa-solid-900.woff2
0
141838
https://wikiwiki.jp/pa/img/logo.png
0
62002
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-hot-wiki.png
0
20759
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-recent-wiki.png
0
20603
https://wikiwiki.jp/pa/img/wikiwiki_game_logo.png
0
13188
https://cse.google.com/cse.js?cx=bcf91dfa96f3c4721
0
4140
https://wikiwiki.jp/pa/img/icon-setting-white.png
0
2938
https://wikiwiki.jp/pa/assets/_4bdd8094/img/header-back.png
0
2027
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-btn-primary.png
0
1448
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-btn-secondary.png
0
1328
https://wikiwiki.jp/pa/img/icon-menu-white.png
0
912
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-contact.png
0
870
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-for-beginner.png
0
870
https://wikiwiki.jp/pa/assets/_4bdd8094/img/h2.png
0
638
https://wikiwiki.jp/pa/assets/_4bdd8094/img/purpose.png
0
293
https://platform.twitter.com/widgets.js
1800000
29709
https://www.google.com/cse/static/style/look/v4/minimalist.css
3000000
2370
https://www.google-analytics.com/analytics.js
7200000
20631
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
604788000
7512
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
604788000
7512
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://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
948.6479992047
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
632.02799949795
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
171.55500035733
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
https://wikiwiki.jp/pa/img/logo.png
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wikiwiki.jp. 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.
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 `[alt]` 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"]`
Wikiwiki.jp 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
WIKIの設定
新規登録
WIKIWIKIの特徴
2022-01-21 18:39:57
2022-01-21 18:39:45
2022-01-21 18:39:41
2022-01-21 18:39:41
2022-01-21 18:39:37
2022-01-21 18:39:32
2022-01-21 18:39:15
2022-01-21 18:39:12
2022-01-21 18:39:08
2022-01-21 18:39:08
2022-01-21 18:38:58
2022-01-21 18:38:56
2022-01-21 18:38:56
2022-01-21 18:38:28
2022-01-21 18:38:25
2022-01-21 18:38:24
2022-01-21 18:38:23
2022-01-21 18:37:46
2022-01-21 18:37:45
2022-01-21 18:37:27
2022-01-21 18:37:22
2022-01-21 18:35:51
2022-01-21 18:35:35
2022-01-21 18:35:33
2022-01-21 18:35:13
2022-01-21 18:35:02
2022-01-21 18:34:48
2022-01-21 18:34:11
2022-01-21 18:33:54
2022-01-21 18:33:18
2022-01-21 18:31:47
2022-01-21 18:31:41
2022-01-21 18:31:36
2022-01-21 18:31:31
2022-01-21 18:31:25
2022-01-21 18:31:10
2022-01-21 18:31:03
2022-01-21 18:30:23
2022-01-21 18:30:20
2022-01-21 18:30:18
2022-01-21 18:29:52
2022-01-21 18:29:39
2022-01-21 18:29:21
2022-01-21 18:29:18
2022-01-21 18:28:35
2022-01-21 18:28:34
2022-01-21 18:27:46
2022-01-21 18:27:39
2022-01-21 18:27:11
2022-01-21 18:26:05
2022-01-21 18:25:58
2022-01-21 18:25:55
2022-01-21 18:25:47
2022-01-21 18:25:04
2022-01-21 18:24:37
2022-01-21 18:22:51
2022-01-21 18:19:39
2022-01-21 18:19:29
2022-01-21 18:19:10
2022-01-21 18:18:05
2022-01-21 18:17:49
2022-01-21 18:17:41
2022-01-21 18:16:13
2022-01-21 18:15:02
2022-01-21 18:14:44
2022-01-21 18:14:09
2022-01-21 18:12:56
2022-01-21 18:12:37
2022-01-21 18:12:33
2022-01-21 18:12:03
2022-01-21 18:11:46
2022-01-21 18:10:36
2022-01-21 18:10:30
2022-01-21 18:10:07
2022-01-21 18:07:07
2022-01-21 18:05:42
2022-01-21 18:04:07
2022-01-21 18:00:18
2022-01-21 17:59:20
2022-01-21 17:57:20
2022-01-21 17:57:20
2022-01-21 17:56:40
2022-01-21 17:52:53
2022-01-21 17:52:49
2022-01-21 17:52:49
2022-01-21 17:52:07
2022-01-21 17:50:50
2022-01-21 17:49:47
2022-01-21 17:49:36
2022-01-21 17:48:45
2022-01-21 17:46:26
2022-01-21 17:46:10
2022-01-21 17:45:38
2022-01-21 17:45:15
2022-01-21 17:44:30
2022-01-21 17:42:54
2022-01-21 17:42:28
2022-01-21 17:40:25
2022-01-21 17:39:30
2022-01-21 17:36:23
もっと見る
新規登録
利用規約
利用規約
プライバシーポリシー
広告について
運営会社
Copyright(C) Since 2005 WIKIWIKI. All Rights Reserved.

Navigation

Heading elements are not 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.
Failing Elements
WIKI 検索

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.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wikiwiki.jp 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
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

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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.2.1
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.
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://wikiwiki.jp/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 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
SHOW DETAILS
3
Medium
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wikiwiki.jp. 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 wikiwiki.jp on mobile screens.
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.

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.

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.

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.
22

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 wikiwiki.jp. This includes details about web app manifests.

PWA Optimized

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 wikiwiki.jp on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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 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) 66
Performance 27
Accessibility 96
Best Practices 85
SEO 91
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://wikiwiki.jp/
Updated: 21st January, 2022

1.17 seconds
First Contentful Paint (FCP)
90%
5%
5%

0.02 seconds
First Input Delay (FID)
94%
6%
0%

Simulate loading on mobile
27

Performance

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

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Wikiwiki.jp should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Wikiwiki.jp should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/cse/static/element/ff97a008b4153450/default+ja.css
10010
3041
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Wikiwiki.jp should consider minifying JS files.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Wikiwiki.jp should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://wikiwiki.jp/
630
https://wikiwiki.jp/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Wikiwiki.jp 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 0 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://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
167
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids an excessive DOM size — 678 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
678
Maximum DOM Depth
×
22
Maximum Child Elements
2022-01-21 18:39:57 電子海のはなし Wiki* 2022-01-21 18:39:45 ドリームレジェンドアニメファイタークロニクル Wi…
100
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Wikiwiki.jp 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.3 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://platform.twitter.com/widgets.js
1813.156
564.152
18.08
https://wikiwiki.jp/
967.356
57.488
3.668
https://www.google-analytics.com/analytics.js
659.968
63.744
3.368
Unattributable
584.952
31.772
0.9
https://www.google.com/cse/static/element/ff97a008b4153450/cse_element__ja.js?usqp=CAI%3D
245.772
189.624
18.52
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
149.408
27.764
64.036
https://www.googletagmanager.com/gtag/js?id=UA-19502774-1
105.472
57.876
6.152
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
84.572
65.852
8.732
https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_WIKIWIKI_Japan_old&dnt=false&domain=wikiwiki.jp&lang=ja&screen_name=WIKIWIKI_Japan&suppress_response_codes=true&t=1825286&tz=GMT-0800&with_replies=false
72.08
11.572
6.488
https://platform.twitter.com/js/moment~timeline.4391e0bf4053fbaa2a022e3fad2a1e1a.js
60.388
56.02
1.724
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
50.316
0
0
Keep request counts low and transfer sizes small — 46 requests • 4,333 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
46
4437490
Font
4
1799787
Image
19
1710875
Script
10
419838
Stylesheet
6
347334
Document
3
157385
Other
4
2271
Media
0
0
Third-party
26
450551
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
オーバースペックでご提供！ WIKIWIKIは世界で最も速いレンタルWIKIサービスを目指しています。
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
オーバースペックでご提供！ WIKIWIKIは世界で最も速いレンタルWIKIサービスを目指しています。
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
みんなが評価しているWIKI Escape from Tarkov Wiki* D2XSpoilerJ Wiki* モンスターハンター大辞典 Wiki* 原神…
0.41279699233575
WIKI 検索
0.17005710394772
埋め込む Twitterで表示
0.13529411764706
WIKIWIKIの特徴
0.052389991069231
WIKIWIKIの特徴 WIKI 検索 みんなが評価しているWIKI Escape from Tarkov Wiki* D2XSpoilerJ Wik…
0.005277481727269
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 — 18 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.google-analytics.com/analytics.js
4246
328
https://platform.twitter.com/widgets.js
6210
311
https://platform.twitter.com/widgets.js
3228
136
https://platform.twitter.com/widgets.js
3413
121
https://platform.twitter.com/widgets.js
2869
118
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
18810
117
https://www.google.com/cse/static/element/ff97a008b4153450/cse_element__ja.js?usqp=CAI%3D
4920
114
https://wikiwiki.jp/
1427
89
https://platform.twitter.com/widgets.js
2790
79
https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_WIKIWIKI_Japan_old&dnt=false&domain=wikiwiki.jp&lang=ja&screen_name=WIKIWIKI_Japan&suppress_response_codes=true&t=1825286&tz=GMT-0800&with_replies=false
7140
72
Unattributable
1808
72
https://platform.twitter.com/widgets.js
3156
72
Unattributable
1654
67
Unattributable
1548
60
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
5070
59
https://platform.twitter.com/js/moment~timeline.4391e0bf4053fbaa2a022e3fad2a1e1a.js
5400
58
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
7710
50
Unattributable
1758
50
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
ウェブ
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 wikiwiki.jp on mobile screens.

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://wikiwiki.jp/
http/1.1
0
302.57900001016
255
0
301
text/html
https://wikiwiki.jp/
h2
302.87300003693
1198.4990000492
50858
50495
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-19502774-1
h2
1212.3399999691
1226.0679999599
37286
92933
200
application/javascript
Script
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
h2
1212.5569999916
1675.0369999791
312345
312100
200
text/css
Stylesheet
https://wikiwiki.jp/pa/img/logo.png
h2
1218.1799999671
2392.211999977
62002
61781
200
image/png
Image
https://wikiwiki.jp/pa/img/icon-setting-white.png
h2
1218.2980000507
1819.1540000262
2938
2719
200
image/png
Image
https://wikiwiki.jp/pa/img/icon-menu-white.png
h2
1218.4330000309
2390.5769999838
912
694
200
image/png
Image
https://wikiwiki.jp/pa/img/main-visual.jpg
h2
1218.5360000003
2687.8809999907
752501
752277
200
image/jpeg
Image
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
h2
1218.6210000655
2550.3759999992
677399
677175
200
image/jpeg
Image
https://wikiwiki.jp/pa/img/wikiwiki_game_logo.png
h2
1218.7660000054
2253.8540000096
13188
12967
200
image/png
Image
https://platform.twitter.com/widgets.js
http/1.1
1218.8600000227
1230.7060000021
29709
98744
200
application/javascript
Script
https://cse.google.com/cse.js?cx=bcf91dfa96f3c4721
h2
1217.3780000303
1279.9730000552
4142
10347
200
text/javascript
Script
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
h2
1218.0050000316
2392.7469999762
148101
147842
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1269.3669999717
1273.3830000507
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1846545307&t=pageview&_s=1&dl=https%3A%2F%2Fwikiwiki.jp%2F&ul=en-us&de=UTF-8&dt=%E7%84%A1%E6%96%99%20%E3%83%AC%E3%83%B3%E3%82%BF%E3%83%AB%20Wiki%20%E3%82%B5%E3%83%BC%E3%83%93%E3%82%B9%20WIKIWIKI&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=102181982&gjid=1639255315&cid=1642009120.1642758275&tid=UA-19502774-1&_gid=1109080409.1642758275&_r=1&gtm=2ou1j0&z=1913942370
h2
1441.7050000047
1444.7510000318
609
1
200
text/plain
XHR
https://www.google.com/cse/static/element/ff97a008b4153450/cse_element__ja.js?usqp=CAI%3D
h2
1691.1390000023
1697.535000043
103345
309124
200
text/javascript
Script
https://www.google.com/cse/static/element/ff97a008b4153450/default+ja.css
h2
1691.8529999675
1696.8470000429
10010
41765
200
text/css
Stylesheet
https://www.google.com/cse/static/style/look/v4/minimalist.css
h2
1692.2809999669
1695.4410000471
2370
5084
200
text/css
Stylesheet
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
h2
1700.6880000699
2542.3350000056
556303
556068
200
application/font-woff
Font
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-btn-primary.png
h2
1701.212999993
2390.8140000422
1448
1229
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16.png
h2
1704.2859999929
2267.3130000476
121178
120955
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/header-back.png
h2
1704.648999963
2390.2040000539
2027
1808
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/h2.png
h2
1707.4300000677
2253.0670000706
638
420
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-recent-wiki.png
h2
1707.5630000327
2266.5640000487
20603
20382
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-hot-wiki.png
h2
1708.2060000394
2253.5360000329
20759
20538
200
image/png
Image
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
h2
1714.5480000181
2684.6870000008
550139
549904
200
application/font-woff
Font
https://wikiwiki.jp/pa/assets/_6c9a1b73/webfonts/fa-solid-900.woff2
h2
1714.95100006
2682.0640000515
141838
141600
200
application/octet-stream
Font
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
h2
1720.1549999882
2022.59399998
551507
551272
200
application/font-woff
Font
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
http/1.1
2428.4550000448
2474.0829999791
105957
327158
200
text/html
Document
https://www.google.com/cse/static/element/ff97a008b4153450/mobile+ja.css
h2
2431.0270000715
2435.8159999829
2432
4919
200
text/css
Stylesheet
https://cse.google.com/adsense/search/async-ads.js
h2
2433.0759999575
2446.346999961
51868
139269
200
text/javascript
Script
https://www.google.com/cse/static/css/v2/clear.png
h2
2452.2359999828
2455.4220000282
1896
1018
200
image/png
Image
https://www.googleapis.com/generate_204
h2
2464.5960000344
2467.8080000449
224
0
204
text/plain
Image
https://clients1.google.com/generate_204
h2
2464.7399999667
2532.3349999962
224
0
204
text/plain
Image
https://syndication.twitter.com/settings?session_id=08a4c0e71d53f737e79f743f76f93eb41430fc56
h2
2546.6299999971
2577.2339999676
680
233
200
application/json
Fetch
https://platform.twitter.com/js/moment~timeline.4391e0bf4053fbaa2a022e3fad2a1e1a.js
http/1.1
2608.2610000158
2620.7560000475
8547
25494
200
application/javascript
Script
https://platform.twitter.com/js/timeline.34cf38a85ac899f1d6a0438a1659decc.js
http/1.1
2608.4269999992
2621.1289999774
6979
20656
200
application/javascript
Script
https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_WIKIWIKI_Japan_old&dnt=false&domain=wikiwiki.jp&lang=ja&screen_name=WIKIWIKI_Japan&suppress_response_codes=true&t=1825286&tz=GMT-0800&with_replies=false
h2
2639.3890000181
2644.9649999849
9230
109909
200
application/javascript
Script
https://pbs.twimg.com/card_img/1481970749149569024/AltvAgmc?format=png&name=144x144_2
h2
2679.8079999862
2685.8570000622
8907
8222
200
image/png
Image
https://platform.twitter.com/css/timeline.2fcb295ab98c2ce26f4cca0d2b2d0f48.light.ltr.css
http/1.1
2679.9919999903
2694.3960000062
12666
53760
200
text/css
Stylesheet
https://platform.twitter.com/css/timeline.2fcb295ab98c2ce26f4cca0d2b2d0f48.light.ltr.css
http/1.1
2679.9139999785
2718.8379999716
12666
53760
200
text/css
Image
https://pbs.twimg.com/profile_images/830311384021766145/8HU4JUSZ_bigger.jpg
h2
2735.9639999922
2742.7320000716
3854
3151
200
image/jpeg
Image
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
h2
2739.2509999918
2755.3609999595
7511
45170
200
text/css
Stylesheet
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
h2
2739.8850000463
2896.7880000127
7511
45170
200
text/css
Image
data
2756.4390000189
2756.5800000448
0
512
200
image/svg+xml
Image
data
2759.010000038
2759.119000053
0
825
200
image/svg+xml
Image
data
2761.3650000421
2761.4649999887
0
572
200
image/svg+xml
Image
data
2763.387999963
2763.4770000586
0
644
200
image/svg+xml
Image
https://syndication.twitter.com/i/jot
http/1.1
3367.0050000073
3403.1139999861
727
0
302
text/html
https://platform.twitter.com/jot.html
http/1.1
3405.2369999699
3415.4349999735
570
80
200
text/html
Document
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)
1244.459
9.744
1277.384
7.842
1285.418
19.812
1305.261
7.323
1321.454
164.116
1719.862
12.579
1735.992
59.103
1813.427
22.211
1835.886
28.562
2045.939
16.061
2068.327
14.971
2083.434
13.246
2450.691
58.559
2509.382
6.642
2523.868
10.142
2534.18
6.431
2544.214
6.696
2561.896
29.524
2595.365
16.639
2612.675
18.36
2639.092
8.245
2668.589
14.451
2683.053
15.754
2703.259
18.02
2721.289
5.088
2727.323
12.496
2740.828
17.371
2762.9
7.903
2771.09
6.617
2781.371
155.28
2943.436
19.845
2963.794
18.012
2984.434
36.112
3023.205
9.802
3033.05
6.686
3066.198
67.773
3133.997
14.169
3302.88
7.84
3314.144
20.469
3334.786
60.538
3395.593
9.129
3461.076
11.792
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

Total Blocking Time — 390 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

Eliminate render-blocking resources — Potential savings of 780 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Wikiwiki.jp 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://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312345
3150

Metrics

First Contentful Paint — 4.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 16.3 s
The time taken for the page to become fully interactive.
Speed Index — 7.5 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 22.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.645
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

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

Other

Properly size images — Potential savings of 464 KiB
Images can slow down the page's load time. Wikiwiki.jp should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wikiwiki.jp/pa/img/main-visual.jpg
752277
437367
https://wikiwiki.jp/pa/img/logo.png
61781
37932
Reduce unused CSS — Potential savings of 295 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Wikiwiki.jp 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://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312345
301741
Reduce unused JavaScript — Potential savings of 293 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://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
148101
104600
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
105911
102218
https://www.google.com/cse/static/element/ff97a008b4153450/cse_element__ja.js?usqp=CAI%3D
103345
51377
https://cse.google.com/adsense/search/async-ads.js
51868
42178
Efficiently encode images — Potential savings of 454 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
677175
261678
https://wikiwiki.jp/pa/img/main-visual.jpg
752277
203615
Serve images in next-gen formats — Potential savings of 1,140 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://wikiwiki.jp/pa/img/main-visual.jpg
752277
516115.5
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
677175
493799.15
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16.png
120955
80326.25
https://wikiwiki.jp/pa/img/logo.png
61781
45643.45
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-hot-wiki.png
20538
16066.6
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-recent-wiki.png
20382
15825.9
Enable text compression — Potential savings of 394 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312100
254584
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
147842
105517
https://wikiwiki.jp/
50495
43704
Reduce initial server response time — Root document took 900 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://wikiwiki.jp/
896.619
Avoid enormous network payloads — Total size was 4,333 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://wikiwiki.jp/pa/img/main-visual.jpg
752501
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
677399
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
556303
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
551507
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
550139
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
312345
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
148101
https://wikiwiki.jp/pa/assets/_6c9a1b73/webfonts/fa-solid-900.woff2
141838
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16.png
121178
https://platform.twitter.com/widgets/widget_iframe.8f764d5bd2778f88121d31d7d8d8e1e3.html?origin=https%3A%2F%2Fwikiwiki.jp
105957
Serve static assets with an efficient cache policy — 24 resources found
Wikiwiki.jp 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://wikiwiki.jp/pa/img/main-visual.jpg
0
752501
https://wikiwiki.jp/pa/img/main-visual-pc.jpg
0
677399
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
0
556303
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
0
551507
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
0
550139
https://wikiwiki.jp/pa/assets/all-a2d56a2adf6256e34fc742e56214160b.min.css
0
312345
https://wikiwiki.jp/pa/assets/all-dcc971759e00c51fca2c916973777c13.min.js
0
148101
https://wikiwiki.jp/pa/assets/_6c9a1b73/webfonts/fa-solid-900.woff2
0
141838
https://wikiwiki.jp/pa/assets/_4bdd8094/img/anniversary16.png
0
121178
https://wikiwiki.jp/pa/img/logo.png
0
62002
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-hot-wiki.png
0
20759
https://wikiwiki.jp/pa/assets/_4bdd8094/img/icon-recent-wiki.png
0
20603
https://wikiwiki.jp/pa/img/wikiwiki_game_logo.png
0
13188
https://cse.google.com/cse.js?cx=bcf91dfa96f3c4721
0
4142
https://wikiwiki.jp/pa/img/icon-setting-white.png
0
2938
https://wikiwiki.jp/pa/assets/_4bdd8094/img/header-back.png
0
2027
https://wikiwiki.jp/pa/assets/_4bdd8094/img/arrow-btn-primary.png
0
1448
https://wikiwiki.jp/pa/img/icon-menu-white.png
0
912
https://wikiwiki.jp/pa/assets/_4bdd8094/img/h2.png
0
638
https://platform.twitter.com/widgets.js
1800000
29709
https://www.google.com/cse/static/style/look/v4/minimalist.css
3000000
2370
https://www.google-analytics.com/analytics.js
7200000
20631
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
604788000
7511
https://ton.twimg.com/tfw/css/syndication_bundle_v1_73385286cca9d2256f6bf3993470820d4827b058.css
604788000
7511
Minimize main-thread work — 4.9 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)
Style & Layout
1815.144
Script Evaluation
1188.98
Other
922.38399999999
Rendering
687.128
Parse HTML & CSS
179.624
Script Parsing & Compilation
146.808
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://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Bold.woff
841.64699993562
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Regular.woff
970.13899998274
https://wikiwiki.jp/pa/assets/_4bdd8094/font/NotoSansJP-Medium.woff
302.43899999186
Reduce the impact of third-party code — Third-party code blocked the main thread for 1,390 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)
SHOW DETAILS
215514
755.288
SHOW DETAILS
21240
548.536
SHOW DETAILS
176063
84.5
SHOW DETAILS
37286
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://wikiwiki.jp/pa/img/main-visual.jpg
https://wikiwiki.jp/pa/img/logo.png
https://wikiwiki.jp/pa/img/icon-setting-white.png
https://wikiwiki.jp/pa/img/icon-menu-white.png
First Contentful Paint (3G) — 9810 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of wikiwiki.jp. 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.
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 `[alt]` 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"]`
Wikiwiki.jp 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
WIKIWIKIの特徴
2022-01-21 18:39:57
2022-01-21 18:39:45
2022-01-21 18:39:41
2022-01-21 18:39:41
2022-01-21 18:39:37
2022-01-21 18:39:32
2022-01-21 18:39:15
2022-01-21 18:39:12
2022-01-21 18:39:08
2022-01-21 18:39:08
2022-01-21 18:38:58
2022-01-21 18:38:56
2022-01-21 18:38:56
2022-01-21 18:38:28
2022-01-21 18:38:25
2022-01-21 18:38:24
2022-01-21 18:38:23
2022-01-21 18:37:46
2022-01-21 18:37:45
2022-01-21 18:37:27
2022-01-21 18:37:22
2022-01-21 18:35:51
2022-01-21 18:35:35
2022-01-21 18:35:33
2022-01-21 18:35:13
2022-01-21 18:35:02
2022-01-21 18:34:48
2022-01-21 18:34:11
2022-01-21 18:33:54
2022-01-21 18:33:18
2022-01-21 18:31:47
2022-01-21 18:31:41
2022-01-21 18:31:36
2022-01-21 18:31:31
2022-01-21 18:31:25
2022-01-21 18:31:10
2022-01-21 18:31:03
2022-01-21 18:30:23
2022-01-21 18:30:20
2022-01-21 18:30:18
2022-01-21 18:29:52
2022-01-21 18:29:39
2022-01-21 18:29:21
2022-01-21 18:29:18
2022-01-21 18:28:35
2022-01-21 18:28:34
2022-01-21 18:27:46
2022-01-21 18:27:39
2022-01-21 18:27:11
2022-01-21 18:26:05
2022-01-21 18:25:58
2022-01-21 18:25:55
2022-01-21 18:25:47
2022-01-21 18:25:04
2022-01-21 18:24:37
2022-01-21 18:22:51
2022-01-21 18:19:39
2022-01-21 18:19:29
2022-01-21 18:19:10
2022-01-21 18:18:05
2022-01-21 18:17:49
2022-01-21 18:17:41
2022-01-21 18:16:13
2022-01-21 18:15:02
2022-01-21 18:14:44
2022-01-21 18:14:09
2022-01-21 18:12:56
2022-01-21 18:12:37
2022-01-21 18:12:33
2022-01-21 18:12:03
2022-01-21 18:11:46
2022-01-21 18:10:36
2022-01-21 18:10:30
2022-01-21 18:10:07
2022-01-21 18:07:07
2022-01-21 18:05:42
2022-01-21 18:04:07
2022-01-21 18:00:18
2022-01-21 17:59:20
2022-01-21 17:57:20
2022-01-21 17:57:20
2022-01-21 17:56:40
2022-01-21 17:52:53
2022-01-21 17:52:49
2022-01-21 17:52:49
2022-01-21 17:52:07
2022-01-21 17:50:50
2022-01-21 17:49:47
2022-01-21 17:49:36
2022-01-21 17:48:45
2022-01-21 17:46:26
2022-01-21 17:46:10
2022-01-21 17:45:38
2022-01-21 17:45:15
2022-01-21 17:44:30
2022-01-21 17:42:54
2022-01-21 17:42:28
2022-01-21 17:40:25
2022-01-21 17:39:30
2022-01-21 17:36:23
もっと見る
利用規約
プライバシーポリシー
広告について
運営会社
Copyright(C) Since 2005 WIKIWIKI. All Rights Reserved.

Navigation

Heading elements are not 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.
Failing Elements
WIKI 検索

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.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that wikiwiki.jp 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
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

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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.2.1
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.
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://wikiwiki.jp/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 3 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
SHOW DETAILS
3
Medium
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for wikiwiki.jp. 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 wikiwiki.jp on mobile screens.
Document uses legible font sizes — 89.56% 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
SHOW DETAILS
.c-wiki-list__item-date
4.85%
9px
SHOW DETAILS
.c-copyright
0.28%
10px
SHOW DETAILS
5.31%
< 12px
SHOW DETAILS
89.56%
≥ 12px

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 — 98% 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
運営会社
40x15
プライバシーポリシー

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.

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.
30

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 wikiwiki.jp. This includes details about web app manifests.

PWA Optimized

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 wikiwiki.jp on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

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.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
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 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: 3.112.121.254
Continent: Asia
Country: Japan
Japan Flag
Region: Tokyo
City: Tokyo
Longitude: 139.7514
Latitude: 35.685
Currencies: JPY
Languages: Japanese

Web Hosting Provider

Name IP Address
Amazon Data Services Japan
Registration

Domain Registrant

Private Registration: Yes
Name: Whois Privacy Protection Service by onamae.com
Organization:
Country:
City:
State:
Post Code:
Email: proxy@whoisprotectservice.com
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.wikiwiki.jp
Issued By: Amazon
Valid From: 11th August, 2021
Valid To: 9th September, 2022
Subject: CN = *.wikiwiki.jp
Hash: b93d2883
Issuer: CN = Amazon
OU = Server CA 1B
O = Amazon
S = US
Version: 2
Serial Number: 6489331822371941219650845917297282474
Serial Number (Hex): 04E1CCC2CF917A4BC9134F395FB08DAA
Valid From: 11th August, 2024
Valid To: 9th September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:59:A4:66:06:52:A0:7B:95:92:3C:A3:94:07:27:96:74:5B:F9:3D:D0
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.sca1b.amazontrust.com/sca1b.crl
Certificate Policies: Policy: 2.23.140.1.2.1
Authority Information Access: OCSP - URI:http://ocsp.sca1b.amazontrust.com
CA Issuers - URI:http://crt.sca1b.amazontrust.com/sca1b.crt
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Aug 11 10:39:10.427 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:CD:33:8F:82:F5:2A:D0:D3:1F:14:E0:
A6:F9:EC:A2:FF:DF:EB:39:3E:A8:E9:25:F7:6B:20:A4:
64:D7:37:F6:28:02:20:2A:CC:4D:E3:D9:14:2E:4D:B4:
51:C2:A3:E6:6D:D2:ED:04:83:43:74:63:3D:3A:1A:46:
C1:56:D4:17:62:C5:49
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Aug 11 10:39:10.446 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:8F:18:91:5A:D0:AE:24:B1:A4:AD:62:
BF:72:76:66:79:A8:AC:01:8B:10:45:A7:FD:1C:DC:2E:
24:FF:16:54:06:02:20:20:09:83:B4:29:94:99:FB:21:
48:2E:C1:70:35:96:76:FB:84:5E:93:8B:BC:14:0F:A5:
BB:59:13:4B:E5:C8:A5
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Aug 11 10:39:10.498 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:E4:D7:C1:44:D9:84:F0:98:EA:B6:11:
A9:B7:05:BE:7D:3D:34:C8:B2:DD:AA:C8:4F:29:76:0A:
01:0D:97:26:89:02:20:0B:77:01:0C:8C:0D:2E:AD:AC:
9B:24:C1:AF:CB:F3:E7:50:0C:D4:E3:AD:24:42:53:99:
3A:0E:6C:EC:48:D1:2B
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:wikiwiki.jp
DNS:*.wikiwiki.jp
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 21st January, 2022
Content-Type: text/html; charset=UTF-8
Server: nginx/1.18.0 (Ubuntu)
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: *

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: dan.ns.cloudflare.com
sara.ns.cloudflare.com
Owner Name: Whois Privacy Protection Service by onamae.com
Owner Street: Shibuya-ku
Owner Email: proxy@whoisprotectservice.com
Full Whois: [ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]

Domain Information: [ドメイン情報]
[Domain Name] WIKIWIKI.JP

[登録者名] 株式会社ウキウキ
[Registrant] WIKIWIKI,Inc

[Name Server] dan.ns.cloudflare.com
[Name Server] sara.ns.cloudflare.com
[Signing Key]

[登録年月日] 2014/04/16
[有効期限] 2022/04/30
[状態] Active
[最終更新] 2021/05/01 01:05:09 (JST)

Contact Information: [公開連絡窓口]
[名前] Whois情報公開代行サービス by お名前.com
[Name] Whois Privacy Protection Service by onamae.com
[Email] proxy@whoisprotectservice.com
[Web Page]
[郵便番号] 150-8512
[住所] 東京都渋谷区
桜丘町 26-1
セルリアンタワー 11階
[Postal Address] Shibuya-ku
26-1 Sakuragaoka-cho
Cerulean Tower 11F
[電話番号] +81.354562560
[FAX番号]

View Raw Whois

Nameservers

Name IP Address
dan.ns.cloudflare.com 172.64.33.108
sara.ns.cloudflare.com 108.162.192.144
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
wl.in.th
0/5
xrea.com
$241,334 USD 4/5
yahoo.co.jp
$485,970,828 USD 5/5
yaplog.jp
$12,201 USD 2/5
youtube-douga-kei.paslog.jp
0/5
All sites similar to wikiwiki.jp

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
wikiwiki.ch
0/5
wikiwiki.com
0/5
wikiwiki.in
$13,839 USD 3/5

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

Recently Updated

buyadad.com
watchfreez.net
dfidol.com
m2-spb.ru
m2-spb.com
0123movies.com
xvidos.com
av4us.net
bluehouseeventcenter.com
massagerepublic.com

Recently Viewed

ubereu.com
souledoutblog.com
patroitradio.com
seaise.com
spain-videos.com
mtyci.org
servialbolivia.com
kytelco.com
baypointelawn.com
finding-loans.com