mywife.cc
Free website and domain report on mywife.cc
Last Updated: 4th February, 2021 Update Now
Overview
Snoop Summary for mywife.cc
This is a free and comprehensive report about mywife.cc. Mywife.cc is hosted in Japan on a server with an IP address of 133.242.235.248, where the local currency is JPY and Japanese is the local language. Our records indicate that mywife.cc is owned/operated by Toyo. Mywife.cc has the potential to be earning an estimated $15 USD per day from advertising revenue. If mywife.cc was to be sold it would possibly be worth $11,093 USD (based on the daily revenue potential of the website over a 24 month period). Mywife.cc is very popular with an estimated 5,327 daily unique visitors. This report was last updated 4th February, 2021.
About mywife.cc
| Site Preview: | |
| Title: | 舞ワイフ セレブクラブ |
| Description: | |
| Keywords and Tags: | adult content, av mywife, mywife 00696, mywife cc, mywife cc torrent, popular, pornography, www mywife cc, 小沢 遥, 成田 由里子, 梨田 沙羅, 白井 真菜, 眞鍋 夏帆, 舞 ワイフ, 蒼い 再会, 谷原 奈津美, 酒井 景子 舞 ワイフ |
| Related Terms: | mywife |
| Fav Icon: | |
| Age: | Over 19 years old |
| Domain Created: | 7th June, 2004 |
| Domain Updated: | 21st June, 2020 |
| Domain Expires: | 7th June, 2021 |
Review
Snoop Score
3/5 (Great!)
Valuation
$11,093 USD
Note: All valuation figures are estimates.
Popularity
High
Note: Popularity is estimated.
Rank, Reach and Authority
| Alexa Rank: | 103,848 |
| Alexa Reach: | |
| SEMrush Rank (US): | 1,820,905 |
| SEMrush Authority Score: | 53 |
| Moz Domain Authority: | 0 |
| Moz Page Authority: | 0 |
Organic vs Paid (Google Ads)
| Organic | Paid | |
|---|---|---|
| Keywords: | 16 | 0 |
| Traffic: | 336 | 0 |
| Cost: | $0 USD | $0 USD |
Traffic
Visitors
| Daily Visitors: | 5,327 |
| Monthly Visitors: | 162,147 |
| Yearly Visitors: | 1,944,473 |
Note: All visitors figures are estimates.
Visitors By Country
Revenue
Revenue
| Daily Revenue: | $15 USD |
| Monthly Revenue: | $462 USD |
| Yearly Revenue: | $5,542 USD |
Note: All revenue figures are estimates.
Revenue By Country
SEO
Backlinks Analysis (SEMrush)
| Backlinks: | 15,289 |
| Referring Domains: | 906 |
| Referring IPs: | 404 |
Mywife.cc has 15,289 backlinks according to SEMrush. 73% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve mywife.cc'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 mywife.cc'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://www.mywife.jp/
Target: https://mywife.cc/teigaku/model/no/1592
2
Source: http://www.mywife.jp/
Target: https://mywife.cc/teigaku/model/no/1604
3
Source: http://www.mywife.jp/
Target: https://mywife.cc/teigaku/model/no/1328
4
Source: http://www.mywife.jp/
Target: https://mywife.cc/teigaku/model/no/1323
5
Source: http://www.mywife.jp/
Target: https://mywife.cc/teigaku/model/no/1584
Top Ranking Keywords (US)
1
Keyword: 舞 ワイフ
Ranked Page: https://mywife.cc/
2
Keyword: mywife cc
Ranked Page: https://mywife.cc/
3
Keyword: www mywife cc
Ranked Page: https://mywife.cc/
4
Keyword: 酒井 景子 舞 ワイフ
Ranked Page: https://mywife.cc/teigaku/model/no/1143
5
Keyword: 酒井 景子 舞 ワイフ
Ranked Page: https://mywife.cc/teigaku/model/no/1184
Domain Analysis
| Value | Length | |
|---|---|---|
| Domain: | mywife.cc | 9 |
| Domain Name: | mywife | 6 |
| Extension (TLD): | cc | 2 |
| Expiry Check: | |
Page Speed Analysis
| Average Load Time: | 1.61 seconds |
| Load Time Comparison: | Faster than 55% of sites |
PageSpeed Insights
Avg. (All Categories)
Performance
Accessibility
Best Practices
SEO
Progressive Web App
0–49 (Fail) 50–89 (Average) 90–100 (Pass) 
URL: https://mywife.cc/
Updated: 4th February, 2021
0.91 seconds
First Contentful Paint (FCP)
0.00 seconds
First Input Delay (FID) Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for mywife.cc. This includes details about optimizing page load times which can result in a better user experience.Metrics
First Contentful Paint — 0.8 s The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 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.001 Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data
Other
First CPU Idle — 0.8 s The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mywife.cc as laggy when the latency is higher than 0.05 seconds.
Network Requests Below is a list of network requests that were made during page load.
| URL | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|
| http://mywife.cc/ | 0 | 536.64199996274 | 292 | 0 | 302 | text/html | |
| https://mywife.cc/ | 537.32500004116 | 1480.3900000406 | 29878 | 28966 | 200 | text/html | Document |
| https://mywife.cc/css/bootstrap.min.css | 1495.3900000546 | 2900.839000009 | 126169 | 125889 | 200 | text/css | Stylesheet |
| https://mywife.cc/css/wife.css | 1495.6010000315 | 1846.3260000572 | 15493 | 15216 | 200 | text/css | Stylesheet |
| https://code.jquery.com/jquery-1.9.1.min.js | 1495.8330000518 | 1516.7640000582 | 33278 | 92629 | 200 | application/javascript | Script |
| https://mywife.cc/js/text_overflow1.js | 1496.1190000176 | 1668.6169999884 | 970 | 689 | 200 | text/javascript | Script |
| https://mywife.cc/img/topm.jpg | 2902.8049999615 | 4091.0370000638 | 434219 | 433938 | 200 | image/jpeg | Image |
| https://mywife.cc/img/mywifelogo.png | 2927.8319999576 | 3637.434000033 | 6882 | 6604 | 200 | image/png | Image |
| https://mywife.cc/img/local.jpg | 2928.0339999823 | 3286.6279999726 | 60940 | 60661 | 200 | image/jpeg | Image |
| https://mywife.cc/img/ranking.jpg | 2928.4429999534 | 4531.1079999665 | 199022 | 198740 | 200 | image/jpeg | Image |
| https://mywife.cc/img/continue.jpg | 2928.9100000169 | 4171.8650000403 | 85153 | 84872 | 200 | image/jpeg | Image |
| https://mywife.cc/img/tousatsu.jpg | 2929.1720000328 | 3792.8949999623 | 29436 | 29156 | 200 | image/jpeg | Image |
| https://mywife.cc/img/photo.jpg | 2929.3670000043 | 4178.0240000226 | 61789 | 61509 | 200 | image/jpeg | Image |
| https://mywife.cc/img/wife_recruit2.jpg | 2929.5350000029 | 3977.4730000645 | 57385 | 57105 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 2929.8829999752 | 4303.9910000516 | 65584 | 65341 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 2930.1350000314 | 4335.672999965 | 69614 | 69370 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 2930.309999967 | 4351.7299999949 | 62657 | 62414 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 2930.565000046 | 4174.5649999939 | 45904 | 45661 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 2930.7770000305 | 4348.4760000138 | 76955 | 76711 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 2931.0090000508 | 4138.1260000635 | 44833 | 44590 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 2931.2800000189 | 4310.7770000352 | 70790 | 70546 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 2931.481000036 | 4341.5390000446 | 65000 | 64757 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 2931.6500000423 | 4299.3759999517 | 65690 | 65447 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 2931.8579999963 | 4173.5890000127 | 55032 | 54789 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 2932.0849999785 | 4358.1080000149 | 72886 | 72642 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 2932.3510000249 | 4182.0290000178 | 52588 | 52345 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 2932.5309999986 | 4493.5990000376 | 95919 | 95675 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 2932.6839999994 | 4352.6340000099 | 64365 | 64122 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 2932.8400000231 | 4343.4520000592 | 70469 | 70225 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 2932.9900000012 | 5172.5080000469 | 56175 | 55932 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 2933.1820000662 | 4338.8389999745 | 70737 | 70493 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 2933.5310000461 | 4321.2160000112 | 64286 | 64043 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 2933.868000051 | 4342.255000025 | 68086 | 67842 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 2934.058999992 | 4705.4299999727 | 56125 | 55882 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 2934.2729999917 | 4332.1589999832 | 63046 | 62803 | 200 | image/jpeg | Image |
| https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js | 1847.844999982 | 1853.0749999918 | 34218 | 95992 | 200 | text/javascript | Script |
| https://mywife.cc/js/bootstrap.min.js | 1860.2060000412 | 2390.1520000072 | 37100 | 36816 | 200 | text/javascript | Script |
| https://mywife.cc/js/menu-wrap.js | 2395.2750000171 | 3141.1849999567 | 321 | 0 | 302 | text/html | |
| https://www.googletagmanager.com/gtag/js?id=UA-142592223-2 | 2934.6049999585 | 2966.0790000344 | 39783 | 99048 | 200 | application/javascript | Script |
| https://mywife.cc/img/toppc.jpg | 2938.65799997 | 4712.3510000529 | 225407 | 225125 | 200 | image/jpeg | Image |
| https://mywife.cc/ | 3143.9470000332 | 4255.8560000034 | 29878 | 28966 | 200 | text/html | Script |
| https://www.google-analytics.com/analytics.js | 4292.2790000448 | 4296.6549999546 | 19452 | 47051 | 200 | text/javascript | Script |
| https://www.google-analytics.com/j/collect?v=1&_v=j87&a=1908918133&t=pageview&_s=1&dl=https%3A%2F%2Fmywife.cc%2F&ul=en-us&de=UTF-8&dt=%E8%88%9E%E3%83%AF%E3%82%A4%E3%83%95%20%E3%82%BB%E3%83%AC%E3%83%96%E3%82%AF%E3%83%A9%E3%83%96&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=1439776142&gjid=1268126942&cid=606546469.1612457682&tid=UA-142592223-2&_gid=1862711285.1612457682&_r=1>m=2ou1r0&z=979108494 | 4333.682000055 | 4337.0379999978 | 618 | 2 | 200 | text/plain | XHR |
| https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j87&tid=UA-142592223-2&cid=606546469.1612457682&jid=1439776142&gjid=1268126942&_gid=1862711285.1612457682&_u=IEBAAUAAAAAAAC~&z=440909064 | 4340.7770000631 | 4344.0839999821 | 691 | 2 | 200 | text/plain | XHR |
| https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j87&tid=UA-142592223-2&cid=606546469.1612457682&jid=1439776142&_u=IEBAAUAAAAAAAC~&z=512974750 | 4347.0150000649 | 4354.5220000669 | 683 | 42 | 200 | image/gif | Image |
Network Round Trip Times — 0 ms High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks Below is a list of the top-level main thread tasks that executed during page load.
| Start Time (Ms) | End Time (Ms) |
|---|---|
| 1512.449 | 7.301 |
| 2930.438 | 8.801 |
| 2939.32 | 22.706 |
| 2962.045 | 180.723 |
| 3143.375 | 22.881 |
| 4285.578 | 14.126 |
| 4299.752 | 7.639 |
| 4308.946 | 11.429 |
| 4331.121 | 31.417 |
Opportunities
Defer offscreen images Time to Interactive can be slowed down by resources on the page. Mywife.cc should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 5 KiB Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mywife.cc should consider minifying CSS files.
| URL | Transfer Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/css/wife.css | 15493 | 4843 |
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mywife.cc 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 2,870 ms Redirects can cause additional delays before the page can begin loading. Mywife.cc should avoid multiple or unnecessary page redirects.
| URL | Time Spent (Ms) |
|---|---|
| http://mywife.cc/ | 2870 |
| https://mywife.cc/ | 0 |
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Mywife.cc should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Diagnostics
Avoids an excessive DOM size — 381 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 | 381 | |
| Maximum DOM Depth | 9 | |
| Maximum Child Elements | 22 |
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. Mywife.cc 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.0 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://mywife.cc/ | 283.1 | 29.371 | 4.672 |
| Unattributable | 50.153 | 1.106 | 0.184 |
Minimizes main-thread work — 0.4 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 | 183.526 |
| Script Evaluation | 93.801 |
| Other | 71.91 |
| Rendering | 35.962 |
| Parse HTML & CSS | 22.217 |
| Script Parsing & Compilation | 10.853 |
All text remains visible during webfont loads Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 45 requests • 2,818 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 | 45 | 2885798 |
| Image | 31 | 2517657 |
| Script | 7 | 194679 |
| Stylesheet | 2 | 141662 |
| Document | 1 | 29878 |
| Other | 4 | 1922 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Third-party | 7 | 128723 |
Minimize third-party usage — Third-party code blocked the main thread for 0 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) |
|---|---|---|
| 39783 | 0 | |
| 34218 | 0 | |
| 33278 | 0 | |
| 20070 | 0 | |
| 691 | 0 | |
| 683 | 0 |
Largest Contentful Paint element — 1 element found The element which was identified as the Largest Contentful Paint.
| Element |
|---|
Avoid large layout shifts — 1 element found Below is a list of all DOM elements that contribute to the CLS of the page.
| Element | CLS Contribution |
|---|---|
| 0.0014826489215772 |
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://mywife.cc/ | 385 | 90 |
Avoid non-composited animations It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.
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
Largest Contentful Paint — 2.2 s The timing of the largest text or image that is painted.
Opportunities
Eliminate render-blocking resources — Potential savings of 340 ms Resources, such as JavaScript and style sheets, can block the first paint of the page. Mywife.cc 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://mywife.cc/css/bootstrap.min.css | 126169 | 350 |
| https://mywife.cc/css/wife.css | 15493 | 190 |
| https://code.jquery.com/jquery-1.9.1.min.js | 33278 | 310 |
| https://mywife.cc/js/text_overflow1.js | 970 | 150 |
Remove unused CSS — Potential savings of 129 KiB Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mywife.cc 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://mywife.cc/css/bootstrap.min.css | 126169 | 119277 |
| https://mywife.cc/css/wife.css | 15493 | 12705 |
Remove unused JavaScript — Potential savings of 95 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://mywife.cc/js/bootstrap.min.js | 37100 | 30436 |
| https://code.jquery.com/jquery-1.9.1.min.js | 33278 | 22983 |
| https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js | 34218 | 21991 |
| https://www.googletagmanager.com/gtag/js?id=UA-142592223-2 | 39783 | 21882 |
Enable text compression — Potential savings of 162 KiB Text-based resources should be served with compression, such as gzip, deflate or brotli.
| URL | Transfer Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/css/bootstrap.min.css | 125889 | 104835 |
| https://mywife.cc/js/bootstrap.min.js | 36816 | 27073 |
| https://mywife.cc/ | 28966 | 22154 |
| https://mywife.cc/css/wife.css | 15216 | 11615 |
Diagnostics
Avoid enormous network payloads — Total size was 2,818 KiB Large network payloads can cost users money and are linked to long load times.
| URL | Transfer Size (Bytes) |
|---|---|
| https://mywife.cc/img/topm.jpg | 434219 |
| https://mywife.cc/img/toppc.jpg | 225407 |
| https://mywife.cc/img/ranking.jpg | 199022 |
| https://mywife.cc/css/bootstrap.min.css | 126169 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95919 |
| https://mywife.cc/img/continue.jpg | 85153 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76955 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72886 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70790 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70737 |
Metrics
Speed Index — 2.8 s The time taken for the page contents to be visibly populated.
Opportunities
Properly size images — Potential savings of 1,296 KiB Images can slow down the page's load time. Mywife.cc should consider serving more appropriate-sized images.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/img/ranking.jpg | 198740 | 156753 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95675 | 80266 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76711 | 64356 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72642 | 60943 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70546 | 59184 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70493 | 59140 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70225 | 58915 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 69370 | 58198 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 67842 | 56916 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 65447 | 54907 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 65341 | 54818 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 64757 | 54328 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 64122 | 53795 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 64043 | 53729 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 62803 | 52688 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 62414 | 52362 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 55932 | 46924 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 55882 | 46882 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 54789 | 45965 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 52345 | 43915 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 45661 | 38307 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 44590 | 37409 |
| https://mywife.cc/img/continue.jpg | 84872 | 13149 |
| https://mywife.cc/img/photo.jpg | 61509 | 9530 |
| https://mywife.cc/img/local.jpg | 60661 | 9398 |
| https://mywife.cc/img/tousatsu.jpg | 29156 | 4517 |
Efficiently encode images — Potential savings of 1,071 KiB Unoptimized images can consume more cellular data than what is necessary.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/img/topm.jpg | 433938 | 301401 |
| https://mywife.cc/img/toppc.jpg | 225125 | 151139 |
| https://mywife.cc/img/ranking.jpg | 198740 | 128482 |
| https://mywife.cc/img/continue.jpg | 84872 | 52891 |
| https://mywife.cc/img/photo.jpg | 61509 | 40490 |
| https://mywife.cc/img/local.jpg | 60661 | 38197 |
| https://mywife.cc/img/wife_recruit2.jpg | 57105 | 36770 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95675 | 26505 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 69370 | 18836 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76711 | 18586 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72642 | 18455 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70546 | 18076 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 64122 | 17708 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 67842 | 17328 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70493 | 17176 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 65341 | 16875 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70225 | 16773 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 64757 | 16252 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 65447 | 15923 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 64043 | 15808 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 62414 | 14786 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 55932 | 14441 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 55882 | 14048 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 54789 | 14044 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 52345 | 13816 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 62803 | 12540 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 45661 | 11491 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 44590 | 11169 |
| https://mywife.cc/img/tousatsu.jpg | 29156 | 6585 |
Serve images in next-gen formats — Potential savings of 1,819 KiB Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/img/topm.jpg | 433938 | 374932 |
| https://mywife.cc/img/toppc.jpg | 225125 | 189867 |
| https://mywife.cc/img/ranking.jpg | 198740 | 163138 |
| https://mywife.cc/img/continue.jpg | 84872 | 65900 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95675 | 57397 |
| https://mywife.cc/img/photo.jpg | 61509 | 51205 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76711 | 48559 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72642 | 47956 |
| https://mywife.cc/img/local.jpg | 60661 | 47353 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 69370 | 46894 |
| https://mywife.cc/img/wife_recruit2.jpg | 57105 | 46265 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70225 | 45741 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70546 | 45246 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 64043 | 45011 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 64122 | 44866 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 67842 | 44452 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 65447 | 44021 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 64757 | 43791 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 65341 | 43457 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70493 | 43365 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 62414 | 41546 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 62803 | 40711 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 55882 | 39296 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 55932 | 38814 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 54789 | 38591 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 52345 | 38457 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 44590 | 33738 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 45661 | 33597 |
| https://mywife.cc/img/tousatsu.jpg | 29156 | 18004 |
Reduce initial server response time — Root document took 940 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://mywife.cc/ | 944.062 |
Diagnostics
Serve static assets with an efficient cache policy — 36 resources found Mywife.cc 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://mywife.cc/img/topm.jpg | 0 | 434219 |
| https://mywife.cc/img/toppc.jpg | 0 | 225407 |
| https://mywife.cc/img/ranking.jpg | 0 | 199022 |
| https://mywife.cc/css/bootstrap.min.css | 0 | 126169 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 0 | 95919 |
| https://mywife.cc/img/continue.jpg | 0 | 85153 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 0 | 76955 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 0 | 72886 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 0 | 70790 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 0 | 70737 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 0 | 70469 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 0 | 69614 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 0 | 68086 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 0 | 65690 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 0 | 65584 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 0 | 65000 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 0 | 64365 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 0 | 64286 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 0 | 63046 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 0 | 62657 |
| https://mywife.cc/img/photo.jpg | 0 | 61789 |
| https://mywife.cc/img/local.jpg | 0 | 60940 |
| https://mywife.cc/img/wife_recruit2.jpg | 0 | 57385 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 0 | 56175 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 0 | 56125 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 0 | 55032 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 0 | 52588 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 0 | 45904 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 0 | 44833 |
| https://mywife.cc/js/bootstrap.min.js | 0 | 37100 |
| https://mywife.cc/ | 0 | 29878 |
| https://mywife.cc/img/tousatsu.jpg | 0 | 29436 |
| https://mywife.cc/css/wife.css | 0 | 15493 |
| https://mywife.cc/img/mywifelogo.png | 0 | 6882 |
| https://mywife.cc/js/text_overflow1.js | 0 | 970 |
| https://www.google-analytics.com/analytics.js | 7200000 | 19452 |
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mywife.cc. This includes details about various page attributes that can be optimized.Navigation
`[accesskey]` values are unique Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0 Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute. It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]` Mywife.cc may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]` Mywife.cc may provide relevant information that dialogue cannot, by using audio descriptions.
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 |
|---|
Names and labels
Image elements do not have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
| Failing Elements |
|---|
Form elements do not have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
| Failing Elements |
|---|
Manual Checks
The page has a logical tab order The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that mywife.cc should incorporate. This includes practices such as protecting pages with HTTPS.Audits
Links to cross-origin destinations are safe Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
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.
Avoids Application Cache Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
| Name | Version |
|---|---|
| Bootstrap | 3.3.5 |
| jQuery | 1.11.3 |
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps Consider deploying source maps for added benefits such as the ability to debug while in production.
| URL | Map URL |
|---|---|
| https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js | https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.map |
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 |
|---|
| http://mywife.cc/ |
Includes front-end JavaScript libraries with known security vulnerabilities — 9 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 |
|---|---|---|
| 5 | Medium | |
| 4 | Medium |
Audits
Browser errors were logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
| URL | Description |
|---|---|
| https://mywife.cc/js/menu-wrap.js | SyntaxError: Unexpected token '<' |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mywife.cc. 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 mywife.cc 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.
Document has a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
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.
Crawling and Indexing
robots.txt is not valid — 457 errors found Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
| Line # | Content | Error |
|---|---|---|
| 1 | <!DOCTYPE html> | Syntax not understood |
| 2 | <html lang="en"> | Syntax not understood |
| 3 | <head> | Syntax not understood |
| 4 | <meta charset="utf-8"> | Syntax not understood |
| 5 | <meta http-equiv="X-UA-Compatible" content="IE=edge"> | Syntax not understood |
| 6 | <meta name="viewport" content="width=device-width,initial-scale=1.0,minimum-scale=1.0"> | Syntax not understood |
| 7 | <meta name="Description" content="人妻動画サイト【舞ワイフ】。刺激を求め応募した素人人妻のプレイ動画を楽しめる、全コンテンツ安全な動画サイト。巨乳・3P・浴衣/着物・温泉・不倫・OL・若妻の他、撮りおろし動画を随時更新。" /> | Syntax not understood |
| 8 | <meta name="Keywords" content="舞ワイフ,人妻,若妻,無料,動画" /> | Syntax not understood |
| 9 | <title>舞ワイフ セレブクラブ</title> | Syntax not understood |
| 10 | <link href="css/bootstrap.min.css" rel="stylesheet"> | Syntax not understood |
| 11 | <link href="css/wife.css" rel="stylesheet"> | Syntax not understood |
| 13 | <script src="//code.jquery.com/jquery-1.9.1.min.js"></script> | Syntax not understood |
| 14 | <script src="/js/text_overflow1.js"></script><!--格納--> | Syntax not understood |
| 19 | <style type="text/css"> | Syntax not understood |
| 20 | body { | Syntax not understood |
| 21 | background-color: #333; | Unknown directive |
| 22 | } | Syntax not understood |
| 23 | </style> | Syntax not understood |
| 25 | </head> | Syntax not understood |
| 27 | <body> | Syntax not understood |
| 28 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 29 | <div class="logo"><img src="img/topm.jpg"></div> | Syntax not understood |
| 31 | <!--<p><img src="http://st.mywife.cc/img/stop.jpg" alt="サーバー調整" width="100%" title="サーバー調整"/></p>--> | Unknown directive |
| 33 | </div> | Syntax not understood |
| 35 | <!--<div class="wifewaku3"></div>--> | Syntax not understood |
| 37 | <div class="container theme-showcase" role="main"> <div class="mywifeloginbotan"> | Syntax not understood |
| 38 | <center> | Syntax not understood |
| 39 | <a href="/login" role="button"> | Syntax not understood |
| 40 | <button type="button" class="btn btn-primary btn-lg">舞ワイフID ログイン</button> | Syntax not understood |
| 41 | </a> <a href="https://grp03.id.rakuten.co.jp/rms/nid/login?service_id=i26&internal.id.mode=auth&y=24&openid.ns=http%3A//specs.openid.net/auth/2.0&x=73&openid.identity=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.return_to=http%3A//mywife.cc/join/rakuten&openid.claimed_id=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup" role="button"> | Unknown directive |
| 42 | <button type="button" class="btn btn-danger btn-lg">楽天ID ログイン</button> | Syntax not understood |
| 43 | </a> | Syntax not understood |
| 44 | </center> | Syntax not understood |
| 45 | </div> | Syntax not understood |
| 46 | <div class="mywifetop"> | Syntax not understood |
| 47 | <!--ボタン--> | Syntax not understood |
| 48 | <center> | Syntax not understood |
| 51 | <a href="/memberin" role="button"> | Syntax not understood |
| 52 | <button type="button" class="btn-default btn-sm"> 会員登録（無料） </button> | Syntax not understood |
| 53 | </a> | Syntax not understood |
| 54 | <div class="setsumei"> | Syntax not understood |
| 55 | <div class="setsumeisen2"><strong>・会員登録（無料）：</strong>舞ワイフをお楽しみいただくには会員登録（無料）が必要です。お持ちでない場合は作成をお願いします</div> | Syntax not understood |
| 56 | <div class="setsumeisen"><strong>・定額サービス購入：</strong>月額2200円（30日間）で動画見放題でお楽しみ頂けます</div> | Syntax not understood |
| 57 | <div class="setsumeisen"><strong>・舞ワイフID ログイン：</strong>舞ワイフから発行しましたIDをお持ちの方専用ログインになります</div> | Syntax not understood |
| 58 | <div class="setsumeisen"><strong>・楽天ペイ：</strong>楽天IDでログインする場合は<a href="https://grp03.id.rakuten.co.jp/rms/nid/login?service_id=i26&internal.id.mode=auth&y=24&openid.ns=http%3A//specs.openid.net/auth/2.0&x=73&openid.identity=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.return_to=http%3A//mywife.cc/join/rakuten&openid.claimed_id=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup">こちら</a></div> | Unknown directive |
| 59 | <div class="setsumeisen"><strong>＜支払い方法＞ </strong>・クレジットカード ・銀行振込 ・コンビニ ・ビットキャッシュ ・楽天Edy ・Yahoo!ウォレット ・楽天ペイ ・ドコモ払い</div> | Syntax not understood |
| 60 | </div> | Syntax not understood |
| 63 | <!--/ボタン--> | Syntax not understood |
| 65 | <!--無料会員--> | Syntax not understood |
| 67 | <!--/無料会員--> | Syntax not understood |
| 68 | </center> | Syntax not understood |
| 69 | </div> | Syntax not understood |
| 70 | </div> | Syntax not understood |
| 72 | <!-- Fixed navbar --> | Syntax not understood |
| 73 | <nav class="navbar navbar-inverse navbar-fixed-top"> | Syntax not understood |
| 74 | <div class="container"> | Syntax not understood |
| 75 | <div class="navbar-header"> | Syntax not understood |
| 76 | <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> | Syntax not understood |
| 77 | <a href="/"><img src="/img/mywifelogo.png"></a> </div> | Syntax not understood |
| 78 | <div id="navbar" class="navbar-collapse collapse"> | Syntax not understood |
| 79 | <ul class="nav navbar-nav"> | Syntax not understood |
| 80 | <li class="active"></li> | Syntax not understood |
| 81 | <li><a href="/memberin"> 会員登録 </a></li> | Syntax not understood |
| 82 | <li><a href="/visitor">初めての方</a></li> | Syntax not understood |
| 83 | <li><a href="/login">ログイン</a></li> | Syntax not understood |
| 84 | <li class="dropdown"> <a href="/login" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">サポート<span class="caret"></span></a> | Syntax not understood |
| 85 | <ul class="dropdown-menu"> | Syntax not understood |
| 86 | <li>【サポート】</li> | Syntax not understood |
| 87 | <li role="separator" class="divider"></li> | Syntax not understood |
| 88 | <li class="dropdown-header"></li> | Syntax not understood |
| 89 | <li><a href="/password">ID・パスワードをお忘れの方</a></li> | Syntax not understood |
| 90 | <li><a href="/contact">総合お問合せ</a></li> | Syntax not understood |
| 91 | </ul> | Syntax not understood |
| 92 | </li> | Syntax not understood |
| 93 | </ul> | Syntax not understood |
| 94 | </div> | Syntax not understood |
| 95 | <!--/.nav-collapse --> | Syntax not understood |
| 96 | </div> | Syntax not understood |
| 97 | </nav> | Syntax not understood |
| 98 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 99 | <!-- Main jumbotron for a primary marketing message or call to action --> | Syntax not understood |
| 100 | <div class="infotop color02"> | Syntax not understood |
| 101 | <h3>INFORMATION</h3> | Syntax not understood |
| 102 | <div class="clear"></div> | Syntax not understood |
| 103 | <div class="infobox"> | Syntax not understood |
| 104 | 2/4 <a href="/teigaku/model/no/1710">新しい奥様 木村ななみさんUP</a><br> | Syntax not understood |
| 105 | 2/4 <a href="/teigaku/model/no/1701">真田心南さん写真UP</a><br> | Syntax not understood |
| 106 | 2/3 <a href="/teigaku/model/no/1704">小野麻美さん写真UP</a><br> | Syntax not understood |
| 107 | 2/2 <a href="/teigaku/model/no/1709">中田凛子さん 蒼い再会UP</a><br> | Syntax not understood |
| 108 | <!-- | Syntax not understood |
| 109 | 12/25 <a href="/teigaku/model/no/1698">ローカル妻 三重県UP</a><br> | Syntax not understood |
| 110 | 4/13 <a href="/teigaku/model/no/1620">吉永塔子さん 温泉後編UP</a><br> | Syntax not understood |
| 111 | 11/1 <a href="/teigaku/model/no/1567">人生劇場 本田あやかさんUP</a><br> --> | Syntax not understood |
| 112 | </div> | Syntax not understood |
| 113 | <p></p> | Syntax not understood |
| 114 | <div class="clear"></div> | Syntax not understood |
| 115 | <p class="oshirase2"><a title="" href="/overdays">・継続特典</a> ※クレジットカード決済のみ<br> | Syntax not understood |
| 116 | </p> | Syntax not understood |
| 117 | <div class="clear"></div> | Syntax not understood |
| 118 | </div> | Syntax not understood |
| 119 | </div> | Syntax not understood |
| 120 | <center> | Syntax not understood |
| 121 | <form name="form1" method="get" action="index"> | Syntax not understood |
| 122 | <input type="hidden" name="page" value="1"> | Syntax not understood |
| 123 | <input type="text" name="s" value="" size="20" maxlength="20"> | Syntax not understood |
| 124 | <input type="submit" value=" 奥様検索 " /> | Syntax not understood |
| 125 | </form> | Syntax not understood |
| 126 | <br> | Syntax not understood |
| 127 | <p class="oshirase2">※奥様検索は苗字と名前の間にスペースを入れてください。苗字のみでも名前のみでも検索可能です。</p> | Syntax not understood |
| 128 | </center> | Syntax not understood |
| 129 | <br> | Syntax not understood |
| 130 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 131 | <div class="container"> | Syntax not understood |
| 133 | <!--=================================--> | Syntax not understood |
| 134 | <div class="infotop color02"> <br> | Syntax not understood |
| 136 | <!--=================================--> | Syntax not understood |
| 138 | <!-- | Syntax not understood |
| 139 | <div class="picupmywifetop"> | Syntax not understood |
| 140 | <div class="picupmywifetop_text"> | Syntax not understood |
| 141 | <p><a href="https://mywife.cc/img/campaign/2019_summer/" target="_blank" > | Unknown directive |
| 142 | <img src="https://mywife.cc/img/2019_summer.jpg" width="100%"></a><br> | Unknown directive |
| 143 | <a href="https://mywife.cc/img/campaign/2019_summer/" title="" target="_blank"> | Unknown directive |
| 144 | <strong>【夏の初月月額料金半額キャンペーン】 </strong></a> <br> | Syntax not understood |
| 145 | 7月25日 12:00～8月25日 23:59まで！<br> | Unknown directive |
| 146 | 今年の夏は素敵な人妻と一緒に過ごしませんか？<br> | Syntax not understood |
| 147 | 初月の月額料金が半額になる夏のキャンペーン開催中！このチャンスに是非！美人妻の赤裸々な秘部をご堪能ください。 | Syntax not understood |
| 148 | </p> | Syntax not understood |
| 149 | <p> </p> | Syntax not understood |
| 150 | </div> | Syntax not understood |
| 151 | </div> | Syntax not understood |
| 152 | --> | Syntax not understood |
| 154 | <!--=================================--> | Syntax not understood |
| 155 | <!-- | Syntax not understood |
| 156 | <div class="picupmywifetop"> | Syntax not understood |
| 157 | <div class="picupmywifetop_text"> | Syntax not understood |
| 158 | <p><a href="http://cp.mywife.cc/" target="_blank" ><img src="/img/wife-picup24.jpg" width="100%"></a><br> | Unknown directive |
| 159 | <a href="http://cp.mywife.cc/" title="" target="_blank"><strong>舞ワイフ感謝祭 【twitter】</strong></a> <br> | Unknown directive |
| 160 | 日頃の感謝の意を込めて「舞ワイフ～MEMORIES～」に抽選で30名様ご招待！<br> | Syntax not understood |
| 161 | 人気のある人妻さんを中心に厳選！無料で動画をお楽しみいただけます！ 応募方法は、舞ワイフ twitterアカウント(<a href="https://twitter.com/mywife_memories" target="_blank">@mywife_memories</a>)をフォローいただいた上、キャンペーンツイートをRTするだけ。受付は2月3日まで。当選者には直接 DM します！ </p> | Unknown directive |
| 162 | <a href="http://cp.mywife.cc/" target="_blank" ><button type="button" class="btn btn-default">続きを読む</button></a> | Unknown directive |
| 163 | <p> </p> | Syntax not understood |
| 164 | </div> | Syntax not understood |
| 165 | </div> | Syntax not understood |
| 166 | --> | Syntax not understood |
| 167 | <!--=================================--> | Syntax not understood |
| 169 | <!--<div class="picupmywifetop"> | Syntax not understood |
| 170 | <div class="picupmywifetop_text"> | Syntax not understood |
| 171 | <p><a href="/teigaku/model/no/1469" ><img src="/img/wife-picup22.jpg" width="100%"></a><br> | Syntax not understood |
| 172 | <a title="" href="/teigaku/model/no/1469"><strong>仲村梨々花さん 【PICKUP】</strong></a> <br> | Syntax not understood |
| 173 | 去年のクリスマスに合コンで出会った人妻と温泉デートです。クリスマスだというのにご主人と一緒に過ごすことが叶わなかった仲村さんは寂しさを紛らわすために友人の誘いで合コンに参加したという。結婚して３年過ぎ、ご主人との関係は日々素っ気なくなっていき、結婚したことを後悔するほど…。</p> | Syntax not understood |
| 174 | <p> </p> | Syntax not understood |
| 175 | </div> | Syntax not understood |
| 176 | </div>--> | Syntax not understood |
| 178 | <!--=================================--> | Syntax not understood |
| 180 | <!-- | Syntax not understood |
| 181 | <div class="picupmywifetop"> | Syntax not understood |
| 182 | <div class="picupmywifetop_text"> | Syntax not understood |
| 183 | <p><a href="/teigaku/model/no/1466" ><img src="/img/wife-picup23.jpg" width="100%"></a><br> | Syntax not understood |
| 184 | <a title="早見美優" href="/teigaku/model/no/1466" rel="bookmark"><strong>早見美優さん</strong></a> <br> | Syntax not understood |
| 185 | 美容師のご主人から家政婦の様な扱いを受け、その寂しさから現実逃避を図った若妻です。艶やかな長い髪とファッションモデルの様に細長い手足のスレンダー美女でありながらご主人に放置され表情も曇り気味…。そんな彼女の気持ちを晴らすべく、優しく抱きしめ男のぬくもりを伝えると美しい花びらを開き別人の…</p> | Syntax not understood |
| 186 | <a href="/teigaku/model/no/1466" ><button type="button" class="btn btn-default">続きを読む</button></a> | Syntax not understood |
| 187 | <p> </p> | Syntax not understood |
| 188 | </div> | Syntax not understood |
| 189 | </div> | Syntax not understood |
| 190 | --> | Syntax not understood |
| 192 | <div class="picupmywifetop"> | Syntax not understood |
| 193 | <div class="picupmywifetop_text"> | Syntax not understood |
| 194 | <p> | Syntax not understood |
| 195 | <a href="/local" ><img src="/img/local.jpg" width="100%"></a> | Syntax not understood |
| 196 | <p> </p> | Syntax not understood |
| 197 | <a href="https://mywife.cc/img/ranking/ranking/" ><img src="/img/ranking.jpg" width="100%"></a> | Unknown directive |
| 198 | </p> | Syntax not understood |
| 199 | </div> | Syntax not understood |
| 200 | </div> | Syntax not understood |
| 202 | <div class="picupmywifetop"> | Syntax not understood |
| 203 | <div class="picupmywifetop_text"> | Syntax not understood |
| 204 | <p> | Syntax not understood |
| 205 | <a href="/overdays" ><img src="/img/continue.jpg" width="100%"></a> | Syntax not understood |
| 206 | <p> </p> | Syntax not understood |
| 207 | <a href="/tousatsu" ><img src="/img/tousatsu.jpg" width="100%"></a> | Syntax not understood |
| 208 | </p> | Syntax not understood |
| 209 | </div> | Syntax not understood |
| 210 | </div> | Syntax not understood |
| 212 | <div class="picupmywifetop"> | Syntax not understood |
| 213 | <div class="picupmywifetop_text"> | Syntax not understood |
| 214 | <p> | Syntax not understood |
| 215 | <a href="https://mywife.cc/img/photo/" ><img src="/img/photo.jpg" width="100%"></a> | Unknown directive |
| 216 | <p> </p> | Syntax not understood |
| 217 | <a href="https://mywife.cc/wife_recruit.html" ><img src="/img/wife_recruit2.jpg" width="100%"></a> | Unknown directive |
| 218 | </p> | Syntax not understood |
| 219 | </div> | Syntax not understood |
| 220 | </div> | Syntax not understood |
| 222 | <!--=================================--> | Syntax not understood |
| 223 | <!-- ログイン後に表示--> | Syntax not understood |
| 224 | <!--=================================--> | Syntax not understood |
| 225 | <div class="clear"></div> | Syntax not understood |
| 226 | </div> | Syntax not understood |
| 227 | <div class="clear"></div> | Syntax not understood |
| 228 | </div> | Syntax not understood |
| 229 | <!--=================================--> | Syntax not understood |
| 230 | </div> | Syntax not understood |
| 231 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 232 | <div class="mywifegallery"> MYWIFE GALLERY </div> | Syntax not understood |
| 233 | <div class="container"> | Syntax not understood |
| 234 | <div class="mywifeichiran"> | Syntax not understood |
| 235 | <!--================================--> | Syntax not understood |
| 237 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 239 | <div class="wifeichiran2018"> <a title="木村 ななみ" href="teigaku/model/no/1710" rel="bookmark"> <img src='//p02.mywife.cc/girl/01710/thumb.jpg' width="99%"></a> | Syntax not understood |
| 240 | <p><a title="木村 ななみ" href="teigaku/model/no/1710" rel="bookmark"><b><br> | Syntax not understood |
| 241 | 木村 ななみ</b></a><b><font color="red"> NEW!</font></b></p> | Syntax not understood |
| 242 | <p>セックスレスに悩む人妻です。セックスレスになったキッカケは…</p> | Syntax not understood |
| 243 | <p><a class="btn btn-default" href="teigaku/model/no/1710" role="button">続きを読む »</a></p> | Syntax not understood |
| 244 | <div class="clear"></div> | Syntax not understood |
| 245 | </div> | Syntax not understood |
| 247 | <!--</div>--> | Syntax not understood |
| 249 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 251 | <div class="wifeichiran2018"> <a title="中田 凛子 蒼い再会" href="teigaku/model/no/1709" rel="bookmark"> <img src='//p02.mywife.cc/girl/01709/thumb.jpg' width="99%"></a> | Syntax not understood |
| 252 | <p><a title="中田 凛子 蒼い再会" href="teigaku/model/no/1709" rel="bookmark"><b><br> | Syntax not understood |
| 253 | 中田 凛子 蒼い再会</b></a><b><font color="red"> NEW!</font></b></p> | Syntax not understood |
| 254 | <p>スレンダー美女の中田さんと再会しました。今夜はより密着度の高い…</p> | Syntax not understood |
| 255 | <p><a class="btn btn-default" href="teigaku/model/no/1709" role="button">続きを読む »</a></p> | Syntax not understood |
| 256 | <div class="clear"></div> | Syntax not understood |
| 257 | </div> | Syntax not understood |
| 259 | <!--</div>--> | Syntax not understood |
| 261 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 263 | <div class="wifeichiran2018"> <a title="小林 美矢" href="teigaku/model/no/1708" rel="bookmark"> <img src='//p02.mywife.cc/girl/01708/thumb.jpg' width="99%"></a> | Syntax not understood |
| 264 | <p><a title="小林 美矢" href="teigaku/model/no/1708" rel="bookmark"><b><br> | Syntax not understood |
| 265 | 小林 美矢</b></a></p> | Syntax not understood |
| 266 | <p>学生時代から巫女として神社に勤め、同世代の女性とは違う道…</p> | Syntax not understood |
| 267 | <p><a class="btn btn-default" href="teigaku/model/no/1708" role="button">続きを読む »</a></p> | Syntax not understood |
| 268 | <div class="clear"></div> | Syntax not understood |
| 269 | </div> | Syntax not understood |
| 271 | <!--</div>--> | Syntax not understood |
| 273 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 275 | <div class="wifeichiran2018"> <a title="小出 美沙 蒼い再会" href="teigaku/model/no/1707" rel="bookmark"> <img src='//p02.mywife.cc/girl/01707/thumb.jpg' width="99%"></a> | Syntax not understood |
| 276 | <p><a title="小出 美沙 蒼い再会" href="teigaku/model/no/1707" rel="bookmark"><b><br> | Syntax not understood |
| 277 | 小出 美沙 蒼い再会</b></a></p> | Syntax not understood |
| 278 | <p>スラリと伸びた長い脚とGカップのバストとグラマーでありながら…</p> | Syntax not understood |
| 279 | <p><a class="btn btn-default" href="teigaku/model/no/1707" role="button">続きを読む »</a></p> | Syntax not understood |
| 280 | <div class="clear"></div> | Syntax not understood |
| 281 | </div> | Syntax not understood |
| 283 | <!--</div>--> | Syntax not understood |
| 285 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 287 | <div class="wifeichiran2018"> <a title="大野 すみれ" href="teigaku/model/no/1706" rel="bookmark"> <img src='//p02.mywife.cc/girl/01706/thumb.jpg' width="99%"></a> | Syntax not understood |
| 288 | <p><a title="大野 すみれ" href="teigaku/model/no/1706" rel="bookmark"><b><br> | Syntax not understood |
| 289 | 大野 すみれ</b></a></p> | Syntax not understood |
| 290 | <p>某有名企業の受付嬢をしていた大野さん。会社の看板として…</p> | Syntax not understood |
| 291 | <p><a class="btn btn-default" href="teigaku/model/no/1706" role="button">続きを読む »</a></p> | Syntax not understood |
| 292 | <div class="clear"></div> | Syntax not understood |
| 293 | </div> | Syntax not understood |
| 295 | <!--</div>--> | Syntax not understood |
| 297 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 299 | <div class="wifeichiran2018"> <a title="神咲 あやか 蒼い再会" href="teigaku/model/no/1705" rel="bookmark"> <img src='//p02.mywife.cc/girl/01705/thumb.jpg' width="99%"></a> | Syntax not understood |
| 300 | <p><a title="神咲 あやか 蒼い再会" href="teigaku/model/no/1705" rel="bookmark"><b><br> | Syntax not understood |
| 301 | 神咲 あやか 蒼い再会</b></a></p> | Syntax not understood |
| 302 | <p>女の悦びと背徳感が入り混じった濃密な時間を体験した神咲さんが…</p> | Syntax not understood |
| 303 | <p><a class="btn btn-default" href="teigaku/model/no/1705" role="button">続きを読む »</a></p> | Syntax not understood |
| 304 | <div class="clear"></div> | Syntax not understood |
| 305 | </div> | Syntax not understood |
| 307 | <!--</div>--> | Syntax not understood |
| 309 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 311 | <div class="wifeichiran2018"> <a title="小野 麻美" href="teigaku/model/no/1704" rel="bookmark"> <img src='//p02.mywife.cc/girl/01704/thumb.jpg' width="99%"></a> | Syntax not understood |
| 312 | <p><a title="小野 麻美" href="teigaku/model/no/1704" rel="bookmark"><b><br> | Syntax not understood |
| 313 | 小野 麻美</b></a></p> | Syntax not understood |
| 314 | <p>今回出会った人妻は、ご主人の浮気に悩み心傷ついてしまった…</p> | Syntax not understood |
| 315 | <p><a class="btn btn-default" href="teigaku/model/no/1704" role="button">続きを読む »</a></p> | Syntax not understood |
| 316 | <div class="clear"></div> | Syntax not understood |
| 317 | </div> | Syntax not understood |
| 319 | <!--</div>--> | Syntax not understood |
| 321 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 323 | <div class="wifeichiran2018"> <a title="相原 すみれ 蒼い再会" href="teigaku/model/no/1703" rel="bookmark"> <img src='//p02.mywife.cc/girl/01703/thumb.jpg' width="99%"></a> | Syntax not understood |
| 324 | <p><a title="相原 すみれ 蒼い再会" href="teigaku/model/no/1703" rel="bookmark"><b><br> | Syntax not understood |
| 325 | 相原 すみれ 蒼い再会</b></a></p> | Syntax not understood |
| 326 | <p>引き締まった裸体と溢れるフェロモンで男の性欲を掻きたてて…</p> | Syntax not understood |
| 327 | <p><a class="btn btn-default" href="teigaku/model/no/1703" role="button">続きを読む »</a></p> | Syntax not understood |
| 328 | <div class="clear"></div> | Syntax not understood |
| 329 | </div> | Syntax not understood |
| 331 | <!--</div>--> | Syntax not understood |
| 333 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 335 | <div class="wifeichiran2018"> <a title="最上 美香" href="teigaku/model/no/1702" rel="bookmark"> <img src='//p02.mywife.cc/girl/01702/thumb.jpg' width="99%"></a> | Syntax not understood |
| 336 | <p><a title="最上 美香" href="teigaku/model/no/1702" rel="bookmark"><b><br> | Syntax not understood |
| 337 | 最上 美香</b></a></p> | Syntax not understood |
| 338 | <p>すれ違ったら思わず振り返って見返したくなってしまう魅力…</p> | Syntax not understood |
| 339 | <p><a class="btn btn-default" href="teigaku/model/no/1702" role="button">続きを読む »</a></p> | Syntax not understood |
| 340 | <div class="clear"></div> | Syntax not understood |
| 341 | </div> | Syntax not understood |
| 343 | <!--</div>--> | Syntax not understood |
| 345 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 347 | <div class="wifeichiran2018"> <a title="真田 心南 蒼い再会" href="teigaku/model/no/1701" rel="bookmark"> <img src='//p02.mywife.cc/girl/01701/thumb.jpg' width="99%"></a> | Syntax not understood |
| 348 | <p><a title="真田 心南 蒼い再会" href="teigaku/model/no/1701" rel="bookmark"><b><br> | Syntax not understood |
| 349 | 真田 心南 蒼い再会</b></a></p> | Syntax not understood |
| 350 | <p>今まで味わったことのない刺激的な時間を体験した真田さん…</p> | Syntax not understood |
| 351 | <p><a class="btn btn-default" href="teigaku/model/no/1701" role="button">続きを読む »</a></p> | Syntax not understood |
| 352 | <div class="clear"></div> | Syntax not understood |
| 353 | </div> | Syntax not understood |
| 355 | <!--</div>--> | Syntax not understood |
| 357 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 359 | <div class="wifeichiran2018"> <a title="百瀬 雅" href="teigaku/model/no/1700" rel="bookmark"> <img src='//p02.mywife.cc/girl/01700/thumb.jpg' width="99%"></a> | Syntax not understood |
| 360 | <p><a title="百瀬 雅" href="teigaku/model/no/1700" rel="bookmark"><b><br> | Syntax not understood |
| 361 | 百瀬 雅</b></a></p> | Syntax not understood |
| 362 | <p>舞ワイフに出演を志望した人妻です。雅さんの出演理由、それは…</p> | Syntax not understood |
| 363 | <p><a class="btn btn-default" href="teigaku/model/no/1700" role="button">続きを読む »</a></p> | Syntax not understood |
| 364 | <div class="clear"></div> | Syntax not understood |
| 365 | </div> | Syntax not understood |
| 367 | <!--</div>--> | Syntax not understood |
| 369 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 371 | <div class="wifeichiran2018"> <a title="金子 仁菜 蒼い再会" href="teigaku/model/no/1699" rel="bookmark"> <img src='//p02.mywife.cc/girl/01699/thumb.jpg' width="99%"></a> | Syntax not understood |
| 372 | <p><a title="金子 仁菜 蒼い再会" href="teigaku/model/no/1699" rel="bookmark"><b><br> | Syntax not understood |
| 373 | 金子 仁菜 蒼い再会</b></a></p> | Syntax not understood |
| 374 | <p>若さが溢れながら、しっかり色気も併せ持った金子さんと再会…</p> | Syntax not understood |
| 375 | <p><a class="btn btn-default" href="teigaku/model/no/1699" role="button">続きを読む »</a></p> | Syntax not understood |
| 376 | <div class="clear"></div> | Syntax not understood |
| 377 | </div> | Syntax not understood |
| 379 | <!--</div>--> | Syntax not understood |
| 381 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 383 | <div class="wifeichiran2018"> <a title="米山 ゆうな" href="teigaku/model/no/1697" rel="bookmark"> <img src='//p02.mywife.cc/girl/01697/thumb.jpg' width="99%"></a> | Syntax not understood |
| 384 | <p><a title="米山 ゆうな" href="teigaku/model/no/1697" rel="bookmark"><b><br> | Syntax not understood |
| 385 | 米山 ゆうな</b></a></p> | Syntax not understood |
| 386 | <p>ご主人の行き過ぎた束縛に悩む人妻と出会いました。結婚前は…</p> | Syntax not understood |
| 387 | <p><a class="btn btn-default" href="teigaku/model/no/1697" role="button">続きを読む »</a></p> | Syntax not understood |
| 388 | <div class="clear"></div> | Syntax not understood |
| 389 | </div> | Syntax not understood |
| 391 | <!--</div>--> | Syntax not understood |
| 393 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 395 | <div class="wifeichiran2018"> <a title="倖田 らん 蒼い再会" href="teigaku/model/no/1696" rel="bookmark"> <img src='//p02.mywife.cc/girl/01696/thumb.jpg' width="99%"></a> | Syntax not understood |
| 396 | <p><a title="倖田 らん 蒼い再会" href="teigaku/model/no/1696" rel="bookmark"><b><br> | Syntax not understood |
| 397 | 倖田 らん 蒼い再会</b></a></p> | Syntax not understood |
| 398 | <p>前回の情事からしばらくして、さらなる刺激を求めて倖田さんが姿を…</p> | Syntax not understood |
| 399 | <p><a class="btn btn-default" href="teigaku/model/no/1696" role="button">続きを読む »</a></p> | Syntax not understood |
| 400 | <div class="clear"></div> | Syntax not understood |
| 401 | </div> | Syntax not understood |
| 403 | <!--</div>--> | Syntax not understood |
| 405 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 407 | <div class="wifeichiran2018"> <a title="野々村 美雨" href="teigaku/model/no/1695" rel="bookmark"> <img src='//p02.mywife.cc/girl/01695/thumb.jpg' width="99%"></a> | Syntax not understood |
| 408 | <p><a title="野々村 美雨" href="teigaku/model/no/1695" rel="bookmark"><b><br> | Syntax not understood |
| 409 | 野々村 美雨</b></a></p> | Syntax not understood |
| 410 | <p>今宵出会ったのは、度重なるご主人の浮気に悩む人妻。結婚後…</p> | Syntax not understood |
| 411 | <p><a class="btn btn-default" href="teigaku/model/no/1695" role="button">続きを読む »</a></p> | Syntax not understood |
| 412 | <div class="clear"></div> | Syntax not understood |
| 413 | </div> | Syntax not understood |
| 415 | <!--</div>--> | Syntax not understood |
| 417 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 419 | <div class="wifeichiran2018"> <a title="秋川 美羽 蒼い再会" href="teigaku/model/no/1694" rel="bookmark"> <img src='//p02.mywife.cc/girl/01694/thumb.jpg' width="99%"></a> | Syntax not understood |
| 420 | <p><a title="秋川 美羽 蒼い再会" href="teigaku/model/no/1694" rel="bookmark"><b><br> | Syntax not understood |
| 421 | 秋川 美羽 蒼い再会</b></a></p> | Syntax not understood |
| 422 | <p>Hカップの爆乳ボディで興奮を誘発させてくれた秋川さんと再会…</p> | Syntax not understood |
| 423 | <p><a class="btn btn-default" href="teigaku/model/no/1694" role="button">続きを読む »</a></p> | Syntax not understood |
| 424 | <div class="clear"></div> | Syntax not understood |
| 425 | </div> | Syntax not understood |
| 427 | <!--</div>--> | Syntax not understood |
| 429 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 431 | <div class="wifeichiran2018"> <a title="結城 里英" href="teigaku/model/no/1693" rel="bookmark"> <img src='//p02.mywife.cc/girl/01693/thumb.jpg' width="99%"></a> | Syntax not understood |
| 432 | <p><a title="結城 里英" href="teigaku/model/no/1693" rel="bookmark"><b><br> | Syntax not understood |
| 433 | 結城 里英</b></a></p> | Syntax not understood |
| 434 | <p>清楚でとても可愛らしい奥様と出会いました。ですが、見かけに…</p> | Syntax not understood |
| 435 | <p><a class="btn btn-default" href="teigaku/model/no/1693" role="button">続きを読む »</a></p> | Syntax not understood |
| 436 | <div class="clear"></div> | Syntax not understood |
| 437 | </div> | Syntax not understood |
| 439 | <!--</div>--> | Syntax not understood |
| 441 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 443 | <div class="wifeichiran2018"> <a title="三好 翔 蒼い再会" href="teigaku/model/no/1692" rel="bookmark"> <img src='//p02.mywife.cc/girl/01692/thumb.jpg' width="99%"></a> | Syntax not understood |
| 444 | <p><a title="三好 翔 蒼い再会" href="teigaku/model/no/1692" rel="bookmark"><b><br> | Syntax not understood |
| 445 | 三好 翔 蒼い再会</b></a></p> | Syntax not understood |
| 446 | <p>高嶺の花という表現にぴったりの三好さん。今夜もさらなる快楽…</p> | Syntax not understood |
| 447 | <p><a class="btn btn-default" href="teigaku/model/no/1692" role="button">続きを読む »</a></p> | Syntax not understood |
| 448 | <div class="clear"></div> | Syntax not understood |
| 449 | </div> | Syntax not understood |
| 451 | <!--</div>--> | Syntax not understood |
| 453 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 455 | <div class="wifeichiran2018"> <a title="石原 夏蓮" href="teigaku/model/no/1691" rel="bookmark"> <img src='//p02.mywife.cc/girl/01691/thumb.jpg' width="99%"></a> | Syntax not understood |
| 456 | <p><a title="石原 夏蓮" href="teigaku/model/no/1691" rel="bookmark"><b><br> | Syntax not understood |
| 457 | 石原 夏蓮</b></a></p> | Syntax not understood |
| 458 | <p>「不倫願望を満たしてほしい。」と不倫サイトに書き込みをして…</p> | Syntax not understood |
| 459 | <p><a class="btn btn-default" href="teigaku/model/no/1691" role="button">続きを読む »</a></p> | Syntax not understood |
| 460 | <div class="clear"></div> | Syntax not understood |
| 461 | </div> | Syntax not understood |
| 463 | <!--</div>--> | Syntax not understood |
| 465 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 467 | <div class="wifeichiran2018"> <a title="川畑 エミリー 蒼い再会" href="teigaku/model/no/1690" rel="bookmark"> <img src='//p02.mywife.cc/girl/01690/thumb.jpg' width="99%"></a> | Syntax not understood |
| 468 | <p><a title="川畑 エミリー 蒼い再会" href="teigaku/model/no/1690" rel="bookmark"><b><br> | Syntax not understood |
| 469 | 川畑 エミリー 蒼い再会</b></a></p> | Syntax not understood |
| 470 | <p>濃厚淫乱な性交を魅せつけてくれたエミリーさんと再会しました…</p> | Syntax not understood |
| 471 | <p><a class="btn btn-default" href="teigaku/model/no/1690" role="button">続きを読む »</a></p> | Syntax not understood |
| 472 | <div class="clear"></div> | Syntax not understood |
| 473 | </div> | Syntax not understood |
| 475 | <!--</div>--> | Syntax not understood |
| 477 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 479 | <div class="wifeichiran2018"> <a title="中田 凛子" href="teigaku/model/no/1689" rel="bookmark"> <img src='//p02.mywife.cc/girl/01689/thumb.jpg' width="99%"></a> | Syntax not understood |
| 480 | <p><a title="中田 凛子" href="teigaku/model/no/1689" rel="bookmark"><b><br> | Syntax not understood |
| 481 | 中田 凛子</b></a></p> | Syntax not understood |
| 482 | <p>趣味は一人エッチだという凛子さん。毎日の日課の様にアダルト動画…</p> | Syntax not understood |
| 483 | <p><a class="btn btn-default" href="teigaku/model/no/1689" role="button">続きを読む »</a></p> | Syntax not understood |
| 484 | <div class="clear"></div> | Syntax not understood |
| 485 | </div> | Syntax not understood |
| 487 | <!--</div>--> | Syntax not understood |
| 488 | <div> </div> | Syntax not understood |
| 489 | </div> | Syntax not understood |
| 490 | </div> | Syntax not understood |
| 492 | <!-- ページ2 --> | Syntax not understood |
| 493 | <div class="Pagination"> <div class="pagenation-btm"> | Syntax not understood |
| 495 | <a class="on-this-page" href="index?p=1">1</a> | Syntax not understood |
| 496 | <a href="index?p=2">2</a></li> | Syntax not understood |
| 497 | <a href="index?p=3">3</a></li> | Syntax not understood |
| 498 | <a href="index?p=4">4</a></li> | Syntax not understood |
| 499 | <a href="index?p=27">最後</a> | Syntax not understood |
| 500 | </div> | Syntax not understood |
| 504 | </div> | Syntax not understood |
| 506 | <!-- /ページ2 --> | Syntax not understood |
| 508 | <!-- ページ | Syntax not understood |
| 509 | <p class="wifewaku2"><center> | Syntax not understood |
| 510 | <div class="archive-nav section-inner"> | Syntax not understood |
| 511 | <div class="pagenation-btm"> | Syntax not understood |
| 513 | <a class="on-this-page" href="index?p=1">1</a> | Syntax not understood |
| 514 | <a href="index?p=2">2</a></li> | Syntax not understood |
| 515 | <a href="index?p=3">3</a></li> | Syntax not understood |
| 516 | <a href="index?p=4">4</a></li> | Syntax not understood |
| 517 | <a href="index?p=27">最後</a> | Syntax not understood |
| 518 | </div> | Syntax not understood |
| 523 | <div class="clear"></div> | Syntax not understood |
| 524 | </div> | Syntax not understood |
| 525 | </center> | Syntax not understood |
| 526 | </p> | Syntax not understood |
| 527 | --> | Syntax not understood |
| 528 | <!-- /ページ --> | Syntax not understood |
| 530 | <p class="color01"> | Syntax not understood |
| 531 | <center> | Syntax not understood |
| 532 | <a title="" href="/overdays"></a> | Syntax not understood |
| 533 | </center> | Syntax not understood |
| 534 | </p> | Syntax not understood |
| 535 | </div> | Syntax not understood |
| 536 | <div class="jumbotron color02"> | Syntax not understood |
| 537 | <footer> | Syntax not understood |
| 538 | <center> | Syntax not understood |
| 539 | <a href="/tokutei.html" role="button">特定商取引</a> <a href="/terms/law.html" role="button">風営法に基づく届出</a> <a href="/terms/term.html" role="button">利用規約</a> <a href="/terms/privacy.html" role="button">個人情報保護方針</a><br> | Syntax not understood |
| 540 | 当サイトに掲載されている画像やムービーには著作権、肖像権があります。<br> | Syntax not understood |
| 541 | 無断転載・流用を禁じます。Copyright © since 2004 舞ワイフ All Rights Reserved. | Syntax not understood |
| 542 | </center> | Syntax not understood |
| 544 | </footer> | Syntax not understood |
| 545 | </div> | Syntax not understood |
| 547 | <!-- jQuery (necessary for Bootstrap's JavaScript plugins) --> | Syntax not understood |
| 548 | <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script> | Unknown directive |
| 549 | <!-- Include all compiled plugins (below), or include individual files as needed --> | Syntax not understood |
| 550 | <script src="/js/bootstrap.min.js"></script> | Syntax not understood |
| 551 | <!--メニュー--> | Syntax not understood |
| 552 | <script src="/js/menu-wrap.js"></script> | Syntax not understood |
| 554 | <!--Google--> | Syntax not understood |
| 556 | <!-- Global site tag (gtag.js) - Google Analytics --> | Syntax not understood |
| 557 | <script async src="https://www.googletagmanager.com/gtag/js?id=UA-142592223-2"></script> | Unknown directive |
| 558 | <script> | Syntax not understood |
| 559 | window.dataLayer = window.dataLayer || []; | Syntax not understood |
| 560 | function gtag(){dataLayer.push(arguments);} | Syntax not understood |
| 561 | gtag('js', new Date()); | Syntax not understood |
| 563 | gtag('config', 'UA-142592223-2'); | Syntax not understood |
| 564 | </script> | Syntax not understood |
| 567 | <!--/Google--> | Syntax not understood |
| 569 | </body> | Syntax not understood |
| 570 | </html> | Syntax not understood |
Content Best Practices
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.
Progressive Web App
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mywife.cc. This includes details about web app manifests.Fast and reliable
Page load is fast enough on mobile networks Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
PWA Optimized
Redirects HTTP traffic to HTTPS It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 mywife.cc on mobile screens.
Contains some content when JavaScript is not available Apps should display alternative content for when JavaScript is disabled.
Fast and reliable
Current page does not respond with a 200 when offline In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.
Installable
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 |
|---|
| http://mywife.cc/ |
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.
Web app manifest does not meet the installability requirements User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data
PWA Optimized
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)
Performance
Accessibility
Best Practices
SEO
Progressive Web App
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://mywife.cc/
Updated: 4th February, 2021
1.08 seconds
First Contentful Paint (FCP)
0.02 seconds
First Input Delay (FID) Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for mywife.cc. This includes details about optimizing page load times which can result in a better user experience.Metrics
Total Blocking Time — 90 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
Max Potential First Input Delay — 110 ms Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mywife.cc as laggy when the latency is higher than 0.05 seconds.
Network Requests Below is a list of network requests that were made during page load.
| URL | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|
| http://mywife.cc/ | 0 | 177.62199998833 | 279 | 0 | 302 | text/html | |
| https://mywife.cc/ | 178.24400000973 | 589.76900001289 | 29877 | 28966 | 200 | text/html | Document |
| https://mywife.cc/css/bootstrap.min.css | 607.2470000363 | 1338.8559999876 | 126168 | 125889 | 200 | text/css | Stylesheet |
| https://mywife.cc/css/wife.css | 607.61700000148 | 969.8099999805 | 15493 | 15216 | 200 | text/css | Stylesheet |
| https://code.jquery.com/jquery-1.9.1.min.js | 607.9810000374 | 627.98500002827 | 33278 | 92629 | 200 | application/javascript | Script |
| https://mywife.cc/js/text_overflow1.js | 608.14999998547 | 787.34400001122 | 970 | 689 | 200 | text/javascript | Script |
| https://mywife.cc/img/topm.jpg | 1365.18600001 | 3128.1089999829 | 434220 | 433938 | 200 | image/jpeg | Image |
| https://mywife.cc/img/mywifelogo.png | 1365.4110000352 | 1547.3009999841 | 6881 | 6604 | 200 | image/png | Image |
| https://mywife.cc/img/local.jpg | 1365.5560000334 | 1727.5760000339 | 60940 | 60661 | 200 | image/jpeg | Image |
| https://mywife.cc/img/ranking.jpg | 1365.9159999806 | 2978.4130000044 | 199022 | 198740 | 200 | image/jpeg | Image |
| https://mywife.cc/img/continue.jpg | 1366.0680000321 | 2587.3670000001 | 85153 | 84872 | 200 | image/jpeg | Image |
| https://mywife.cc/img/tousatsu.jpg | 1366.1880000145 | 2249.5259999996 | 29436 | 29156 | 200 | image/jpeg | Image |
| https://mywife.cc/img/photo.jpg | 1366.388000024 | 2607.0060000056 | 61789 | 61509 | 200 | image/jpeg | Image |
| https://mywife.cc/img/wife_recruit2.jpg | 1366.5760000004 | 2604.7179999878 | 57385 | 57105 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 1366.7209999985 | 2599.6579999919 | 65584 | 65341 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 1367.0840000268 | 2605.8700000285 | 69614 | 69370 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 1367.3350000172 | 2636.9709999999 | 62657 | 62414 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 1367.5490000169 | 2416.2789999973 | 45904 | 45661 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 1367.7139999927 | 2610.6470000232 | 76955 | 76711 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 1367.871000024 | 2400.4640000057 | 44833 | 44590 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 1368.04999999 | 2597.1129999962 | 70790 | 70546 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 1368.4009999852 | 2936.3350000349 | 65000 | 64757 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 1368.5999999871 | 2567.9259999888 | 65690 | 65447 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 1368.7989999889 | 2590.148999996 | 55032 | 54789 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 1369.0659999847 | 2621.7460000189 | 72886 | 72642 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 1369.3620000267 | 2426.8370000063 | 52588 | 52345 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 1369.5350000053 | 2810.7740000123 | 95919 | 95675 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 1369.6869999985 | 2582.9469999881 | 64365 | 64122 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 1369.869999995 | 2620.2219999977 | 70469 | 70225 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 1370.035000029 | 2609.0430000331 | 56175 | 55932 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 1370.3170000226 | 2785.4640000151 | 70737 | 70493 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 1370.4790000338 | 2637.6339999842 | 64286 | 64043 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 1370.6709999824 | 2608.1969999941 | 68086 | 67842 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 1370.8300000289 | 2424.897000019 | 56125 | 55882 | 200 | image/jpeg | Image |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 1371.3890000363 | 2617.3169999965 | 63046 | 62803 | 200 | image/jpeg | Image |
| https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js | 971.06499999063 | 976.91900003701 | 34219 | 95992 | 200 | text/javascript | Script |
| https://mywife.cc/js/bootstrap.min.js | 984.48799998732 | 2027.2359999944 | 37101 | 36816 | 200 | text/javascript | Script |
| https://mywife.cc/js/menu-wrap.js | 1340.3330000001 | 1552.2789999959 | 296 | 0 | 302 | text/html | |
| https://www.googletagmanager.com/gtag/js?id=UA-142592223-2 | 1371.6160000185 | 1395.251000009 | 39783 | 99048 | 200 | application/javascript | Script |
| https://mywife.cc/ | 1552.5130000315 | 2650.2559999935 | 29878 | 28966 | 200 | text/html | Script |
| https://www.google-analytics.com/analytics.js | 2695.7159999874 | 2700.3269999987 | 19452 | 47051 | 200 | text/javascript | Script |
| https://www.google-analytics.com/j/collect?v=1&_v=j87&a=1305609458&t=pageview&_s=1&dl=https%3A%2F%2Fmywife.cc%2F&ul=en-us&de=UTF-8&dt=%E8%88%9E%E3%83%AF%E3%82%A4%E3%83%95%20%E3%82%BB%E3%83%AC%E3%83%96%E3%82%AF%E3%83%A9%E3%83%96&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAUABAAAAAC~&jid=132495437&gjid=455510946&cid=1550700407.1612457703&tid=UA-142592223-2&_gid=1755982507.1612457703&_r=1>m=2ou1r0&z=58412547 | 2732.090000005 | 2736.1610000371 | 618 | 2 | 200 | text/plain | XHR |
| https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j87&tid=UA-142592223-2&cid=1550700407.1612457703&jid=132495437&gjid=455510946&_gid=1755982507.1612457703&_u=IEBAAUAAAAAAAC~&z=1621560312 | 2739.0449999948 | 2743.3960000053 | 691 | 2 | 200 | text/plain | XHR |
| https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j87&tid=UA-142592223-2&cid=1550700407.1612457703&jid=132495437&_u=IEBAAUAAAAAAAC~&z=2104121357 | 2746.1670000339 | 2754.7149999882 | 683 | 42 | 200 | image/gif | Image |
Network Round Trip Times — 0 ms High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks Below is a list of the top-level main thread tasks that executed during page load.
| Start Time (Ms) | End Time (Ms) |
|---|---|
| 627.081 | 10.032 |
| 639.924 | 6.271 |
| 1373.705 | 8.746 |
| 1382.57 | 22.418 |
| 1405.001 | 113.368 |
| 1519.012 | 17.845 |
| 2064.458 | 7.356 |
| 2633.563 | 5.04 |
| 2649.943 | 6.492 |
| 2686.892 | 17.752 |
| 2704.697 | 9.639 |
| 2716.546 | 13.024 |
| 2739.724 | 26.919 |
| 3016.511 | 5.305 |
| 3163.733 | 5.75 |
Opportunities
Minify CSS — Potential savings of 5 KiB Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mywife.cc should consider minifying CSS files.
| URL | Transfer Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/css/wife.css | 15493 | 4843 |
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mywife.cc 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.
Initial server response time was short — Root document took 410 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://mywife.cc/ | 412.523 |
Avoid multiple page redirects — Potential savings of 15,090 ms Redirects can cause additional delays before the page can begin loading. Mywife.cc should avoid multiple or unnecessary page redirects.
| URL | Time Spent (Ms) |
|---|---|
| http://mywife.cc/ | 15090 |
| https://mywife.cc/ | 0 |
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Mywife.cc should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Diagnostics
Avoids enormous network payloads — Total size was 2,598 KiB Large network payloads can cost users money and are linked to long load times.
| URL | Transfer Size (Bytes) |
|---|---|
| https://mywife.cc/img/topm.jpg | 434220 |
| https://mywife.cc/img/ranking.jpg | 199022 |
| https://mywife.cc/css/bootstrap.min.css | 126168 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95919 |
| https://mywife.cc/img/continue.jpg | 85153 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76955 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72886 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70790 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70737 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70469 |
Avoids an excessive DOM size — 381 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 | 381 | |
| Maximum DOM Depth | 9 | |
| Maximum Child Elements | 22 |
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. Mywife.cc 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.4 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://mywife.cc/ | 945.896 | 115.136 | 19.448 |
| Unattributable | 209.804 | 5.012 | 0.744 |
| https://www.google-analytics.com/analytics.js | 127.256 | 110.792 | 4.02 |
| https://www.googletagmanager.com/gtag/js?id=UA-142592223-2 | 98.336 | 83.996 | 10.656 |
| https://code.jquery.com/jquery-1.9.1.min.js | 62.868 | 49.348 | 8.176 |
Minimizes main-thread work — 1.5 s Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| Category | Time Spent (Ms) |
|---|---|
| Style & Layout | 475.288 |
| Script Evaluation | 393.044 |
| Other | 313.976 |
| Rendering | 198.432 |
| Parse HTML & CSS | 93.812 |
| Script Parsing & Compilation | 46.54 |
All text remains visible during webfont loads Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 44 requests • 2,598 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 | 44 | 2660353 |
| Image | 30 | 2292250 |
| Script | 7 | 194681 |
| Stylesheet | 2 | 141661 |
| Document | 1 | 29877 |
| Other | 4 | 1884 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Third-party | 7 | 128724 |
Minimize third-party usage — Third-party code blocked the main thread for 50 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) |
|---|---|---|
| 20070 | 48.036 | |
| 39783 | 0 | |
| 34219 | 0 | |
| 33278 | 0 | |
| 691 | 0 | |
| 683 | 0 |
Largest Contentful Paint element — 1 element found The element which was identified as the Largest Contentful Paint.
| Element |
|---|
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 |
|---|---|
| 0.40781879087866 | |
| 0.10403540583639 | |
| 0.043829731162554 | |
| 0.034389481373697 | |
| 0.034389481373697 |
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 — 5 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://mywife.cc/ | 1325 | 227 |
| https://www.google-analytics.com/analytics.js | 12480 | 108 |
| https://code.jquery.com/jquery-1.9.1.min.js | 9150 | 90 |
| https://mywife.cc/ | 3840 | 71 |
| https://www.googletagmanager.com/gtag/js?id=UA-142592223-2 | 11589 | 52 |
Avoid non-composited animations It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.
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 — 3.0 s The time taken for the first image or text on the page to be rendered.
Other
First CPU Idle — 4.0 s The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 3.0 s The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5865 ms The time taken for the first image or text on the page to be rendered while on a 3G network.
Opportunities
Remove unused CSS — Potential savings of 131 KiB Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mywife.cc 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://mywife.cc/css/bootstrap.min.css | 126168 | 121024 |
| https://mywife.cc/css/wife.css | 15493 | 12955 |
Remove unused JavaScript — Potential savings of 95 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://mywife.cc/js/bootstrap.min.js | 37101 | 30437 |
| https://code.jquery.com/jquery-1.9.1.min.js | 33278 | 22983 |
| https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js | 34219 | 21991 |
| https://www.googletagmanager.com/gtag/js?id=UA-142592223-2 | 39783 | 21882 |
Metrics
Speed Index — 8.1 s The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 11.1 s The timing of the largest text or image that is painted.
Time to Interactive — 8.3 s The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.624 Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data
Opportunities
Eliminate render-blocking resources — Potential savings of 1,580 ms Resources, such as JavaScript and style sheets, can block the first paint of the page. Mywife.cc 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://mywife.cc/css/bootstrap.min.css | 126168 | 1680 |
| https://mywife.cc/css/wife.css | 15493 | 780 |
| https://code.jquery.com/jquery-1.9.1.min.js | 33278 | 1230 |
| https://mywife.cc/js/text_overflow1.js | 970 | 480 |
Properly size images — Potential savings of 755 KiB Images can slow down the page's load time. Mywife.cc should consider serving more appropriate-sized images.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95675 | 54730 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76711 | 43882 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72642 | 41554 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70546 | 40355 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70493 | 40325 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70225 | 40172 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 69370 | 39683 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 67842 | 38809 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 65447 | 37439 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 65341 | 37378 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 64757 | 37044 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 64122 | 36681 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 64043 | 36635 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 62803 | 35926 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 62414 | 35704 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 55932 | 31996 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 55882 | 31967 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 54789 | 31342 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 52345 | 29944 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 45661 | 26120 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 44590 | 25507 |
Defer offscreen images — Potential savings of 1,320 KiB Time to Interactive can be slowed down by resources on the page. Mywife.cc should consider lazy-loading offscreen and hidden images.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95675 | 95675 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76711 | 76711 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72642 | 72642 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70546 | 70546 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70493 | 70493 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70225 | 70225 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 69370 | 69370 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 67842 | 67842 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 65447 | 65447 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 65341 | 65341 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 64757 | 64757 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 64122 | 64122 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 64043 | 64043 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 62803 | 62803 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 62414 | 62414 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 55932 | 55932 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 55882 | 55882 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 54789 | 54789 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 52345 | 52345 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 45661 | 45661 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 44590 | 44590 |
Efficiently encode images — Potential savings of 923 KiB Unoptimized images can consume more cellular data than what is necessary.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/img/topm.jpg | 433938 | 301401 |
| https://mywife.cc/img/ranking.jpg | 198740 | 128482 |
| https://mywife.cc/img/continue.jpg | 84872 | 52891 |
| https://mywife.cc/img/photo.jpg | 61509 | 40490 |
| https://mywife.cc/img/local.jpg | 60661 | 38197 |
| https://mywife.cc/img/wife_recruit2.jpg | 57105 | 36770 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95675 | 26505 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 69370 | 18836 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76711 | 18586 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72642 | 18455 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70546 | 18076 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 64122 | 17708 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 67842 | 17328 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70493 | 17176 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 65341 | 16875 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70225 | 16773 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 64757 | 16252 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 65447 | 15923 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 64043 | 15808 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 62414 | 14786 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 55932 | 14441 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 55882 | 14048 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 54789 | 14044 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 52345 | 13816 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 62803 | 12540 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 45661 | 11491 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 44590 | 11169 |
| https://mywife.cc/img/tousatsu.jpg | 29156 | 6585 |
Serve images in next-gen formats — Potential savings of 1,633 KiB Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/img/topm.jpg | 433938 | 374932 |
| https://mywife.cc/img/ranking.jpg | 198740 | 163138 |
| https://mywife.cc/img/continue.jpg | 84872 | 65900 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 95675 | 57397 |
| https://mywife.cc/img/photo.jpg | 61509 | 51205 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 76711 | 48559 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 72642 | 47956 |
| https://mywife.cc/img/local.jpg | 60661 | 47353 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 69370 | 46894 |
| https://mywife.cc/img/wife_recruit2.jpg | 57105 | 46265 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 70225 | 45741 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 70546 | 45246 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 64043 | 45011 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 64122 | 44866 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 67842 | 44452 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 65447 | 44021 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 64757 | 43791 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 65341 | 43457 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 70493 | 43365 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 62414 | 41546 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 62803 | 40711 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 55882 | 39296 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 55932 | 38814 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 54789 | 38591 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 52345 | 38457 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 44590 | 33738 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 45661 | 33597 |
| https://mywife.cc/img/tousatsu.jpg | 29156 | 18004 |
Enable text compression — Potential savings of 162 KiB Text-based resources should be served with compression, such as gzip, deflate or brotli.
| URL | Transfer Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://mywife.cc/css/bootstrap.min.css | 125889 | 104835 |
| https://mywife.cc/js/bootstrap.min.js | 36816 | 27073 |
| https://mywife.cc/ | 28966 | 22154 |
| https://mywife.cc/css/wife.css | 15216 | 11615 |
Diagnostics
Serve static assets with an efficient cache policy — 35 resources found Mywife.cc 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://mywife.cc/img/topm.jpg | 0 | 434220 |
| https://mywife.cc/img/ranking.jpg | 0 | 199022 |
| https://mywife.cc/css/bootstrap.min.css | 0 | 126168 |
| https://p02.mywife.cc/girl/01697/thumb.jpg | 0 | 95919 |
| https://mywife.cc/img/continue.jpg | 0 | 85153 |
| https://p02.mywife.cc/girl/01706/thumb.jpg | 0 | 76955 |
| https://p02.mywife.cc/girl/01700/thumb.jpg | 0 | 72886 |
| https://p02.mywife.cc/girl/01704/thumb.jpg | 0 | 70790 |
| https://p02.mywife.cc/girl/01693/thumb.jpg | 0 | 70737 |
| https://p02.mywife.cc/girl/01695/thumb.jpg | 0 | 70469 |
| https://p02.mywife.cc/girl/01709/thumb.jpg | 0 | 69614 |
| https://p02.mywife.cc/girl/01691/thumb.jpg | 0 | 68086 |
| https://p02.mywife.cc/girl/01702/thumb.jpg | 0 | 65690 |
| https://p02.mywife.cc/girl/01710/thumb.jpg | 0 | 65584 |
| https://p02.mywife.cc/girl/01703/thumb.jpg | 0 | 65000 |
| https://p02.mywife.cc/girl/01696/thumb.jpg | 0 | 64365 |
| https://p02.mywife.cc/girl/01692/thumb.jpg | 0 | 64286 |
| https://p02.mywife.cc/girl/01689/thumb.jpg | 0 | 63046 |
| https://p02.mywife.cc/girl/01708/thumb.jpg | 0 | 62657 |
| https://mywife.cc/img/photo.jpg | 0 | 61789 |
| https://mywife.cc/img/local.jpg | 0 | 60940 |
| https://mywife.cc/img/wife_recruit2.jpg | 0 | 57385 |
| https://p02.mywife.cc/girl/01694/thumb.jpg | 0 | 56175 |
| https://p02.mywife.cc/girl/01690/thumb.jpg | 0 | 56125 |
| https://p02.mywife.cc/girl/01701/thumb.jpg | 0 | 55032 |
| https://p02.mywife.cc/girl/01699/thumb.jpg | 0 | 52588 |
| https://p02.mywife.cc/girl/01707/thumb.jpg | 0 | 45904 |
| https://p02.mywife.cc/girl/01705/thumb.jpg | 0 | 44833 |
| https://mywife.cc/js/bootstrap.min.js | 0 | 37101 |
| https://mywife.cc/ | 0 | 29878 |
| https://mywife.cc/img/tousatsu.jpg | 0 | 29436 |
| https://mywife.cc/css/wife.css | 0 | 15493 |
| https://mywife.cc/img/mywifelogo.png | 0 | 6881 |
| https://mywife.cc/js/text_overflow1.js | 0 | 970 |
| https://www.google-analytics.com/analytics.js | 7200000 | 19452 |
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mywife.cc. This includes details about various page attributes that can be optimized.Navigation
`[accesskey]` values are unique Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0 Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute. It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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"]` Mywife.cc may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]` Mywife.cc may provide relevant information that dialogue cannot, by using audio descriptions.
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 |
|---|
Names and labels
Image elements do not have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
| Failing Elements |
|---|
Form elements do not have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
| Failing Elements |
|---|
Manual Checks
The page has a logical tab order The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that mywife.cc should incorporate. This includes practices such as protecting pages with HTTPS.Audits
Links to cross-origin destinations are safe Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
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.
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.
Avoids Application Cache Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
| Name | Version |
|---|---|
| Bootstrap | 3.3.5 |
| jQuery | 1.11.3 |
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps Consider deploying source maps for added benefits such as the ability to debug while in production.
| URL | Map URL |
|---|---|
| https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js | https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.map |
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 |
|---|
| http://mywife.cc/ |
Includes front-end JavaScript libraries with known security vulnerabilities — 9 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 |
|---|---|---|
| 5 | Medium | |
| 4 | Medium |
Audits
Serves images with low resolution For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
| URL | Displayed size | Actual size | Expected size |
|---|---|---|---|
| https://mywife.cc/img/mywifelogo.png | 100 x 45 | 100 x 45 | 263 x 119 |
Audits
Browser errors were logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
| URL | Description |
|---|---|
| https://mywife.cc/js/menu-wrap.js | SyntaxError: Unexpected token '<' |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mywife.cc. 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 mywife.cc on mobile screens.
Document uses legible font sizes — 94.24% 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 |
|---|---|---|---|
| .jumbotron | 5.76% | 10px | |
| 94.24% | ≥ 12px |
Tap targets are sized appropriately — 100% 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.
Content Best Practices
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
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.
Crawling and Indexing
robots.txt is not valid — 457 errors found Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
| Line # | Content | Error |
|---|---|---|
| 1 | <!DOCTYPE html> | Syntax not understood |
| 2 | <html lang="en"> | Syntax not understood |
| 3 | <head> | Syntax not understood |
| 4 | <meta charset="utf-8"> | Syntax not understood |
| 5 | <meta http-equiv="X-UA-Compatible" content="IE=edge"> | Syntax not understood |
| 6 | <meta name="viewport" content="width=device-width,initial-scale=1.0,minimum-scale=1.0"> | Syntax not understood |
| 7 | <meta name="Description" content="人妻動画サイト【舞ワイフ】。刺激を求め応募した素人人妻のプレイ動画を楽しめる、全コンテンツ安全な動画サイト。巨乳・3P・浴衣/着物・温泉・不倫・OL・若妻の他、撮りおろし動画を随時更新。" /> | Syntax not understood |
| 8 | <meta name="Keywords" content="舞ワイフ,人妻,若妻,無料,動画" /> | Syntax not understood |
| 9 | <title>舞ワイフ セレブクラブ</title> | Syntax not understood |
| 10 | <link href="css/bootstrap.min.css" rel="stylesheet"> | Syntax not understood |
| 11 | <link href="css/wife.css" rel="stylesheet"> | Syntax not understood |
| 13 | <script src="//code.jquery.com/jquery-1.9.1.min.js"></script> | Syntax not understood |
| 14 | <script src="/js/text_overflow1.js"></script><!--格納--> | Syntax not understood |
| 19 | <style type="text/css"> | Syntax not understood |
| 20 | body { | Syntax not understood |
| 21 | background-color: #333; | Unknown directive |
| 22 | } | Syntax not understood |
| 23 | </style> | Syntax not understood |
| 25 | </head> | Syntax not understood |
| 27 | <body> | Syntax not understood |
| 28 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 29 | <div class="logo"><img src="img/topm.jpg"></div> | Syntax not understood |
| 31 | <!--<p><img src="http://st.mywife.cc/img/stop.jpg" alt="サーバー調整" width="100%" title="サーバー調整"/></p>--> | Unknown directive |
| 33 | </div> | Syntax not understood |
| 35 | <!--<div class="wifewaku3"></div>--> | Syntax not understood |
| 37 | <div class="container theme-showcase" role="main"> <div class="mywifeloginbotan"> | Syntax not understood |
| 38 | <center> | Syntax not understood |
| 39 | <a href="/login" role="button"> | Syntax not understood |
| 40 | <button type="button" class="btn btn-primary btn-lg">舞ワイフID ログイン</button> | Syntax not understood |
| 41 | </a> <a href="https://grp03.id.rakuten.co.jp/rms/nid/login?service_id=i26&internal.id.mode=auth&y=24&openid.ns=http%3A//specs.openid.net/auth/2.0&x=73&openid.identity=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.return_to=http%3A//mywife.cc/join/rakuten&openid.claimed_id=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup" role="button"> | Unknown directive |
| 42 | <button type="button" class="btn btn-danger btn-lg">楽天ID ログイン</button> | Syntax not understood |
| 43 | </a> | Syntax not understood |
| 44 | </center> | Syntax not understood |
| 45 | </div> | Syntax not understood |
| 46 | <div class="mywifetop"> | Syntax not understood |
| 47 | <!--ボタン--> | Syntax not understood |
| 48 | <center> | Syntax not understood |
| 51 | <a href="/memberin" role="button"> | Syntax not understood |
| 52 | <button type="button" class="btn-default btn-sm"> 会員登録（無料） </button> | Syntax not understood |
| 53 | </a> | Syntax not understood |
| 54 | <div class="setsumei"> | Syntax not understood |
| 55 | <div class="setsumeisen2"><strong>・会員登録（無料）：</strong>舞ワイフをお楽しみいただくには会員登録（無料）が必要です。お持ちでない場合は作成をお願いします</div> | Syntax not understood |
| 56 | <div class="setsumeisen"><strong>・定額サービス購入：</strong>月額2200円（30日間）で動画見放題でお楽しみ頂けます</div> | Syntax not understood |
| 57 | <div class="setsumeisen"><strong>・舞ワイフID ログイン：</strong>舞ワイフから発行しましたIDをお持ちの方専用ログインになります</div> | Syntax not understood |
| 58 | <div class="setsumeisen"><strong>・楽天ペイ：</strong>楽天IDでログインする場合は<a href="https://grp03.id.rakuten.co.jp/rms/nid/login?service_id=i26&internal.id.mode=auth&y=24&openid.ns=http%3A//specs.openid.net/auth/2.0&x=73&openid.identity=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.return_to=http%3A//mywife.cc/join/rakuten&openid.claimed_id=http%3A//specs.openid.net/auth/2.0/identifier_select&openid.mode=checkid_setup">こちら</a></div> | Unknown directive |
| 59 | <div class="setsumeisen"><strong>＜支払い方法＞ </strong>・クレジットカード ・銀行振込 ・コンビニ ・ビットキャッシュ ・楽天Edy ・Yahoo!ウォレット ・楽天ペイ ・ドコモ払い</div> | Syntax not understood |
| 60 | </div> | Syntax not understood |
| 63 | <!--/ボタン--> | Syntax not understood |
| 65 | <!--無料会員--> | Syntax not understood |
| 67 | <!--/無料会員--> | Syntax not understood |
| 68 | </center> | Syntax not understood |
| 69 | </div> | Syntax not understood |
| 70 | </div> | Syntax not understood |
| 72 | <!-- Fixed navbar --> | Syntax not understood |
| 73 | <nav class="navbar navbar-inverse navbar-fixed-top"> | Syntax not understood |
| 74 | <div class="container"> | Syntax not understood |
| 75 | <div class="navbar-header"> | Syntax not understood |
| 76 | <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> | Syntax not understood |
| 77 | <a href="/"><img src="/img/mywifelogo.png"></a> </div> | Syntax not understood |
| 78 | <div id="navbar" class="navbar-collapse collapse"> | Syntax not understood |
| 79 | <ul class="nav navbar-nav"> | Syntax not understood |
| 80 | <li class="active"></li> | Syntax not understood |
| 81 | <li><a href="/memberin"> 会員登録 </a></li> | Syntax not understood |
| 82 | <li><a href="/visitor">初めての方</a></li> | Syntax not understood |
| 83 | <li><a href="/login">ログイン</a></li> | Syntax not understood |
| 84 | <li class="dropdown"> <a href="/login" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">サポート<span class="caret"></span></a> | Syntax not understood |
| 85 | <ul class="dropdown-menu"> | Syntax not understood |
| 86 | <li>【サポート】</li> | Syntax not understood |
| 87 | <li role="separator" class="divider"></li> | Syntax not understood |
| 88 | <li class="dropdown-header"></li> | Syntax not understood |
| 89 | <li><a href="/password">ID・パスワードをお忘れの方</a></li> | Syntax not understood |
| 90 | <li><a href="/contact">総合お問合せ</a></li> | Syntax not understood |
| 91 | </ul> | Syntax not understood |
| 92 | </li> | Syntax not understood |
| 93 | </ul> | Syntax not understood |
| 94 | </div> | Syntax not understood |
| 95 | <!--/.nav-collapse --> | Syntax not understood |
| 96 | </div> | Syntax not understood |
| 97 | </nav> | Syntax not understood |
| 98 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 99 | <!-- Main jumbotron for a primary marketing message or call to action --> | Syntax not understood |
| 100 | <div class="infotop color02"> | Syntax not understood |
| 101 | <h3>INFORMATION</h3> | Syntax not understood |
| 102 | <div class="clear"></div> | Syntax not understood |
| 103 | <div class="infobox"> | Syntax not understood |
| 104 | 2/4 <a href="/teigaku/model/no/1710">新しい奥様 木村ななみさんUP</a><br> | Syntax not understood |
| 105 | 2/4 <a href="/teigaku/model/no/1701">真田心南さん写真UP</a><br> | Syntax not understood |
| 106 | 2/3 <a href="/teigaku/model/no/1704">小野麻美さん写真UP</a><br> | Syntax not understood |
| 107 | 2/2 <a href="/teigaku/model/no/1709">中田凛子さん 蒼い再会UP</a><br> | Syntax not understood |
| 108 | <!-- | Syntax not understood |
| 109 | 12/25 <a href="/teigaku/model/no/1698">ローカル妻 三重県UP</a><br> | Syntax not understood |
| 110 | 4/13 <a href="/teigaku/model/no/1620">吉永塔子さん 温泉後編UP</a><br> | Syntax not understood |
| 111 | 11/1 <a href="/teigaku/model/no/1567">人生劇場 本田あやかさんUP</a><br> --> | Syntax not understood |
| 112 | </div> | Syntax not understood |
| 113 | <p></p> | Syntax not understood |
| 114 | <div class="clear"></div> | Syntax not understood |
| 115 | <p class="oshirase2"><a title="" href="/overdays">・継続特典</a> ※クレジットカード決済のみ<br> | Syntax not understood |
| 116 | </p> | Syntax not understood |
| 117 | <div class="clear"></div> | Syntax not understood |
| 118 | </div> | Syntax not understood |
| 119 | </div> | Syntax not understood |
| 120 | <center> | Syntax not understood |
| 121 | <form name="form1" method="get" action="index"> | Syntax not understood |
| 122 | <input type="hidden" name="page" value="1"> | Syntax not understood |
| 123 | <input type="text" name="s" value="" size="20" maxlength="20"> | Syntax not understood |
| 124 | <input type="submit" value=" 奥様検索 " /> | Syntax not understood |
| 125 | </form> | Syntax not understood |
| 126 | <br> | Syntax not understood |
| 127 | <p class="oshirase2">※奥様検索は苗字と名前の間にスペースを入れてください。苗字のみでも名前のみでも検索可能です。</p> | Syntax not understood |
| 128 | </center> | Syntax not understood |
| 129 | <br> | Syntax not understood |
| 130 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 131 | <div class="container"> | Syntax not understood |
| 133 | <!--=================================--> | Syntax not understood |
| 134 | <div class="infotop color02"> <br> | Syntax not understood |
| 136 | <!--=================================--> | Syntax not understood |
| 138 | <!-- | Syntax not understood |
| 139 | <div class="picupmywifetop"> | Syntax not understood |
| 140 | <div class="picupmywifetop_text"> | Syntax not understood |
| 141 | <p><a href="https://mywife.cc/img/campaign/2019_summer/" target="_blank" > | Unknown directive |
| 142 | <img src="https://mywife.cc/img/2019_summer.jpg" width="100%"></a><br> | Unknown directive |
| 143 | <a href="https://mywife.cc/img/campaign/2019_summer/" title="" target="_blank"> | Unknown directive |
| 144 | <strong>【夏の初月月額料金半額キャンペーン】 </strong></a> <br> | Syntax not understood |
| 145 | 7月25日 12:00～8月25日 23:59まで！<br> | Unknown directive |
| 146 | 今年の夏は素敵な人妻と一緒に過ごしませんか？<br> | Syntax not understood |
| 147 | 初月の月額料金が半額になる夏のキャンペーン開催中！このチャンスに是非！美人妻の赤裸々な秘部をご堪能ください。 | Syntax not understood |
| 148 | </p> | Syntax not understood |
| 149 | <p> </p> | Syntax not understood |
| 150 | </div> | Syntax not understood |
| 151 | </div> | Syntax not understood |
| 152 | --> | Syntax not understood |
| 154 | <!--=================================--> | Syntax not understood |
| 155 | <!-- | Syntax not understood |
| 156 | <div class="picupmywifetop"> | Syntax not understood |
| 157 | <div class="picupmywifetop_text"> | Syntax not understood |
| 158 | <p><a href="http://cp.mywife.cc/" target="_blank" ><img src="/img/wife-picup24.jpg" width="100%"></a><br> | Unknown directive |
| 159 | <a href="http://cp.mywife.cc/" title="" target="_blank"><strong>舞ワイフ感謝祭 【twitter】</strong></a> <br> | Unknown directive |
| 160 | 日頃の感謝の意を込めて「舞ワイフ～MEMORIES～」に抽選で30名様ご招待！<br> | Syntax not understood |
| 161 | 人気のある人妻さんを中心に厳選！無料で動画をお楽しみいただけます！ 応募方法は、舞ワイフ twitterアカウント(<a href="https://twitter.com/mywife_memories" target="_blank">@mywife_memories</a>)をフォローいただいた上、キャンペーンツイートをRTするだけ。受付は2月3日まで。当選者には直接 DM します！ </p> | Unknown directive |
| 162 | <a href="http://cp.mywife.cc/" target="_blank" ><button type="button" class="btn btn-default">続きを読む</button></a> | Unknown directive |
| 163 | <p> </p> | Syntax not understood |
| 164 | </div> | Syntax not understood |
| 165 | </div> | Syntax not understood |
| 166 | --> | Syntax not understood |
| 167 | <!--=================================--> | Syntax not understood |
| 169 | <!--<div class="picupmywifetop"> | Syntax not understood |
| 170 | <div class="picupmywifetop_text"> | Syntax not understood |
| 171 | <p><a href="/teigaku/model/no/1469" ><img src="/img/wife-picup22.jpg" width="100%"></a><br> | Syntax not understood |
| 172 | <a title="" href="/teigaku/model/no/1469"><strong>仲村梨々花さん 【PICKUP】</strong></a> <br> | Syntax not understood |
| 173 | 去年のクリスマスに合コンで出会った人妻と温泉デートです。クリスマスだというのにご主人と一緒に過ごすことが叶わなかった仲村さんは寂しさを紛らわすために友人の誘いで合コンに参加したという。結婚して３年過ぎ、ご主人との関係は日々素っ気なくなっていき、結婚したことを後悔するほど…。</p> | Syntax not understood |
| 174 | <p> </p> | Syntax not understood |
| 175 | </div> | Syntax not understood |
| 176 | </div>--> | Syntax not understood |
| 178 | <!--=================================--> | Syntax not understood |
| 180 | <!-- | Syntax not understood |
| 181 | <div class="picupmywifetop"> | Syntax not understood |
| 182 | <div class="picupmywifetop_text"> | Syntax not understood |
| 183 | <p><a href="/teigaku/model/no/1466" ><img src="/img/wife-picup23.jpg" width="100%"></a><br> | Syntax not understood |
| 184 | <a title="早見美優" href="/teigaku/model/no/1466" rel="bookmark"><strong>早見美優さん</strong></a> <br> | Syntax not understood |
| 185 | 美容師のご主人から家政婦の様な扱いを受け、その寂しさから現実逃避を図った若妻です。艶やかな長い髪とファッションモデルの様に細長い手足のスレンダー美女でありながらご主人に放置され表情も曇り気味…。そんな彼女の気持ちを晴らすべく、優しく抱きしめ男のぬくもりを伝えると美しい花びらを開き別人の…</p> | Syntax not understood |
| 186 | <a href="/teigaku/model/no/1466" ><button type="button" class="btn btn-default">続きを読む</button></a> | Syntax not understood |
| 187 | <p> </p> | Syntax not understood |
| 188 | </div> | Syntax not understood |
| 189 | </div> | Syntax not understood |
| 190 | --> | Syntax not understood |
| 192 | <div class="picupmywifetop"> | Syntax not understood |
| 193 | <div class="picupmywifetop_text"> | Syntax not understood |
| 194 | <p> | Syntax not understood |
| 195 | <a href="/local" ><img src="/img/local.jpg" width="100%"></a> | Syntax not understood |
| 196 | <p> </p> | Syntax not understood |
| 197 | <a href="https://mywife.cc/img/ranking/ranking/" ><img src="/img/ranking.jpg" width="100%"></a> | Unknown directive |
| 198 | </p> | Syntax not understood |
| 199 | </div> | Syntax not understood |
| 200 | </div> | Syntax not understood |
| 202 | <div class="picupmywifetop"> | Syntax not understood |
| 203 | <div class="picupmywifetop_text"> | Syntax not understood |
| 204 | <p> | Syntax not understood |
| 205 | <a href="/overdays" ><img src="/img/continue.jpg" width="100%"></a> | Syntax not understood |
| 206 | <p> </p> | Syntax not understood |
| 207 | <a href="/tousatsu" ><img src="/img/tousatsu.jpg" width="100%"></a> | Syntax not understood |
| 208 | </p> | Syntax not understood |
| 209 | </div> | Syntax not understood |
| 210 | </div> | Syntax not understood |
| 212 | <div class="picupmywifetop"> | Syntax not understood |
| 213 | <div class="picupmywifetop_text"> | Syntax not understood |
| 214 | <p> | Syntax not understood |
| 215 | <a href="https://mywife.cc/img/photo/" ><img src="/img/photo.jpg" width="100%"></a> | Unknown directive |
| 216 | <p> </p> | Syntax not understood |
| 217 | <a href="https://mywife.cc/wife_recruit.html" ><img src="/img/wife_recruit2.jpg" width="100%"></a> | Unknown directive |
| 218 | </p> | Syntax not understood |
| 219 | </div> | Syntax not understood |
| 220 | </div> | Syntax not understood |
| 222 | <!--=================================--> | Syntax not understood |
| 223 | <!-- ログイン後に表示--> | Syntax not understood |
| 224 | <!--=================================--> | Syntax not understood |
| 225 | <div class="clear"></div> | Syntax not understood |
| 226 | </div> | Syntax not understood |
| 227 | <div class="clear"></div> | Syntax not understood |
| 228 | </div> | Syntax not understood |
| 229 | <!--=================================--> | Syntax not understood |
| 230 | </div> | Syntax not understood |
| 231 | <div class="container theme-showcase" role="main"> | Syntax not understood |
| 232 | <div class="mywifegallery"> MYWIFE GALLERY </div> | Syntax not understood |
| 233 | <div class="container"> | Syntax not understood |
| 234 | <div class="mywifeichiran"> | Syntax not understood |
| 235 | <!--================================--> | Syntax not understood |
| 237 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 239 | <div class="wifeichiran2018"> <a title="木村 ななみ" href="teigaku/model/no/1710" rel="bookmark"> <img src='//p02.mywife.cc/girl/01710/thumb.jpg' width="99%"></a> | Syntax not understood |
| 240 | <p><a title="木村 ななみ" href="teigaku/model/no/1710" rel="bookmark"><b><br> | Syntax not understood |
| 241 | 木村 ななみ</b></a><b><font color="red"> NEW!</font></b></p> | Syntax not understood |
| 242 | <p>セックスレスに悩む人妻です。セックスレスになったキッカケは…</p> | Syntax not understood |
| 243 | <p><a class="btn btn-default" href="teigaku/model/no/1710" role="button">続きを読む »</a></p> | Syntax not understood |
| 244 | <div class="clear"></div> | Syntax not understood |
| 245 | </div> | Syntax not understood |
| 247 | <!--</div>--> | Syntax not understood |
| 249 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 251 | <div class="wifeichiran2018"> <a title="中田 凛子 蒼い再会" href="teigaku/model/no/1709" rel="bookmark"> <img src='//p02.mywife.cc/girl/01709/thumb.jpg' width="99%"></a> | Syntax not understood |
| 252 | <p><a title="中田 凛子 蒼い再会" href="teigaku/model/no/1709" rel="bookmark"><b><br> | Syntax not understood |
| 253 | 中田 凛子 蒼い再会</b></a><b><font color="red"> NEW!</font></b></p> | Syntax not understood |
| 254 | <p>スレンダー美女の中田さんと再会しました。今夜はより密着度の高い…</p> | Syntax not understood |
| 255 | <p><a class="btn btn-default" href="teigaku/model/no/1709" role="button">続きを読む »</a></p> | Syntax not understood |
| 256 | <div class="clear"></div> | Syntax not understood |
| 257 | </div> | Syntax not understood |
| 259 | <!--</div>--> | Syntax not understood |
| 261 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 263 | <div class="wifeichiran2018"> <a title="小林 美矢" href="teigaku/model/no/1708" rel="bookmark"> <img src='//p02.mywife.cc/girl/01708/thumb.jpg' width="99%"></a> | Syntax not understood |
| 264 | <p><a title="小林 美矢" href="teigaku/model/no/1708" rel="bookmark"><b><br> | Syntax not understood |
| 265 | 小林 美矢</b></a></p> | Syntax not understood |
| 266 | <p>学生時代から巫女として神社に勤め、同世代の女性とは違う道…</p> | Syntax not understood |
| 267 | <p><a class="btn btn-default" href="teigaku/model/no/1708" role="button">続きを読む »</a></p> | Syntax not understood |
| 268 | <div class="clear"></div> | Syntax not understood |
| 269 | </div> | Syntax not understood |
| 271 | <!--</div>--> | Syntax not understood |
| 273 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 275 | <div class="wifeichiran2018"> <a title="小出 美沙 蒼い再会" href="teigaku/model/no/1707" rel="bookmark"> <img src='//p02.mywife.cc/girl/01707/thumb.jpg' width="99%"></a> | Syntax not understood |
| 276 | <p><a title="小出 美沙 蒼い再会" href="teigaku/model/no/1707" rel="bookmark"><b><br> | Syntax not understood |
| 277 | 小出 美沙 蒼い再会</b></a></p> | Syntax not understood |
| 278 | <p>スラリと伸びた長い脚とGカップのバストとグラマーでありながら…</p> | Syntax not understood |
| 279 | <p><a class="btn btn-default" href="teigaku/model/no/1707" role="button">続きを読む »</a></p> | Syntax not understood |
| 280 | <div class="clear"></div> | Syntax not understood |
| 281 | </div> | Syntax not understood |
| 283 | <!--</div>--> | Syntax not understood |
| 285 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 287 | <div class="wifeichiran2018"> <a title="大野 すみれ" href="teigaku/model/no/1706" rel="bookmark"> <img src='//p02.mywife.cc/girl/01706/thumb.jpg' width="99%"></a> | Syntax not understood |
| 288 | <p><a title="大野 すみれ" href="teigaku/model/no/1706" rel="bookmark"><b><br> | Syntax not understood |
| 289 | 大野 すみれ</b></a></p> | Syntax not understood |
| 290 | <p>某有名企業の受付嬢をしていた大野さん。会社の看板として…</p> | Syntax not understood |
| 291 | <p><a class="btn btn-default" href="teigaku/model/no/1706" role="button">続きを読む »</a></p> | Syntax not understood |
| 292 | <div class="clear"></div> | Syntax not understood |
| 293 | </div> | Syntax not understood |
| 295 | <!--</div>--> | Syntax not understood |
| 297 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 299 | <div class="wifeichiran2018"> <a title="神咲 あやか 蒼い再会" href="teigaku/model/no/1705" rel="bookmark"> <img src='//p02.mywife.cc/girl/01705/thumb.jpg' width="99%"></a> | Syntax not understood |
| 300 | <p><a title="神咲 あやか 蒼い再会" href="teigaku/model/no/1705" rel="bookmark"><b><br> | Syntax not understood |
| 301 | 神咲 あやか 蒼い再会</b></a></p> | Syntax not understood |
| 302 | <p>女の悦びと背徳感が入り混じった濃密な時間を体験した神咲さんが…</p> | Syntax not understood |
| 303 | <p><a class="btn btn-default" href="teigaku/model/no/1705" role="button">続きを読む »</a></p> | Syntax not understood |
| 304 | <div class="clear"></div> | Syntax not understood |
| 305 | </div> | Syntax not understood |
| 307 | <!--</div>--> | Syntax not understood |
| 309 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 311 | <div class="wifeichiran2018"> <a title="小野 麻美" href="teigaku/model/no/1704" rel="bookmark"> <img src='//p02.mywife.cc/girl/01704/thumb.jpg' width="99%"></a> | Syntax not understood |
| 312 | <p><a title="小野 麻美" href="teigaku/model/no/1704" rel="bookmark"><b><br> | Syntax not understood |
| 313 | 小野 麻美</b></a></p> | Syntax not understood |
| 314 | <p>今回出会った人妻は、ご主人の浮気に悩み心傷ついてしまった…</p> | Syntax not understood |
| 315 | <p><a class="btn btn-default" href="teigaku/model/no/1704" role="button">続きを読む »</a></p> | Syntax not understood |
| 316 | <div class="clear"></div> | Syntax not understood |
| 317 | </div> | Syntax not understood |
| 319 | <!--</div>--> | Syntax not understood |
| 321 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 323 | <div class="wifeichiran2018"> <a title="相原 すみれ 蒼い再会" href="teigaku/model/no/1703" rel="bookmark"> <img src='//p02.mywife.cc/girl/01703/thumb.jpg' width="99%"></a> | Syntax not understood |
| 324 | <p><a title="相原 すみれ 蒼い再会" href="teigaku/model/no/1703" rel="bookmark"><b><br> | Syntax not understood |
| 325 | 相原 すみれ 蒼い再会</b></a></p> | Syntax not understood |
| 326 | <p>引き締まった裸体と溢れるフェロモンで男の性欲を掻きたてて…</p> | Syntax not understood |
| 327 | <p><a class="btn btn-default" href="teigaku/model/no/1703" role="button">続きを読む »</a></p> | Syntax not understood |
| 328 | <div class="clear"></div> | Syntax not understood |
| 329 | </div> | Syntax not understood |
| 331 | <!--</div>--> | Syntax not understood |
| 333 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 335 | <div class="wifeichiran2018"> <a title="最上 美香" href="teigaku/model/no/1702" rel="bookmark"> <img src='//p02.mywife.cc/girl/01702/thumb.jpg' width="99%"></a> | Syntax not understood |
| 336 | <p><a title="最上 美香" href="teigaku/model/no/1702" rel="bookmark"><b><br> | Syntax not understood |
| 337 | 最上 美香</b></a></p> | Syntax not understood |
| 338 | <p>すれ違ったら思わず振り返って見返したくなってしまう魅力…</p> | Syntax not understood |
| 339 | <p><a class="btn btn-default" href="teigaku/model/no/1702" role="button">続きを読む »</a></p> | Syntax not understood |
| 340 | <div class="clear"></div> | Syntax not understood |
| 341 | </div> | Syntax not understood |
| 343 | <!--</div>--> | Syntax not understood |
| 345 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 347 | <div class="wifeichiran2018"> <a title="真田 心南 蒼い再会" href="teigaku/model/no/1701" rel="bookmark"> <img src='//p02.mywife.cc/girl/01701/thumb.jpg' width="99%"></a> | Syntax not understood |
| 348 | <p><a title="真田 心南 蒼い再会" href="teigaku/model/no/1701" rel="bookmark"><b><br> | Syntax not understood |
| 349 | 真田 心南 蒼い再会</b></a></p> | Syntax not understood |
| 350 | <p>今まで味わったことのない刺激的な時間を体験した真田さん…</p> | Syntax not understood |
| 351 | <p><a class="btn btn-default" href="teigaku/model/no/1701" role="button">続きを読む »</a></p> | Syntax not understood |
| 352 | <div class="clear"></div> | Syntax not understood |
| 353 | </div> | Syntax not understood |
| 355 | <!--</div>--> | Syntax not understood |
| 357 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 359 | <div class="wifeichiran2018"> <a title="百瀬 雅" href="teigaku/model/no/1700" rel="bookmark"> <img src='//p02.mywife.cc/girl/01700/thumb.jpg' width="99%"></a> | Syntax not understood |
| 360 | <p><a title="百瀬 雅" href="teigaku/model/no/1700" rel="bookmark"><b><br> | Syntax not understood |
| 361 | 百瀬 雅</b></a></p> | Syntax not understood |
| 362 | <p>舞ワイフに出演を志望した人妻です。雅さんの出演理由、それは…</p> | Syntax not understood |
| 363 | <p><a class="btn btn-default" href="teigaku/model/no/1700" role="button">続きを読む »</a></p> | Syntax not understood |
| 364 | <div class="clear"></div> | Syntax not understood |
| 365 | </div> | Syntax not understood |
| 367 | <!--</div>--> | Syntax not understood |
| 369 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 371 | <div class="wifeichiran2018"> <a title="金子 仁菜 蒼い再会" href="teigaku/model/no/1699" rel="bookmark"> <img src='//p02.mywife.cc/girl/01699/thumb.jpg' width="99%"></a> | Syntax not understood |
| 372 | <p><a title="金子 仁菜 蒼い再会" href="teigaku/model/no/1699" rel="bookmark"><b><br> | Syntax not understood |
| 373 | 金子 仁菜 蒼い再会</b></a></p> | Syntax not understood |
| 374 | <p>若さが溢れながら、しっかり色気も併せ持った金子さんと再会…</p> | Syntax not understood |
| 375 | <p><a class="btn btn-default" href="teigaku/model/no/1699" role="button">続きを読む »</a></p> | Syntax not understood |
| 376 | <div class="clear"></div> | Syntax not understood |
| 377 | </div> | Syntax not understood |
| 379 | <!--</div>--> | Syntax not understood |
| 381 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 383 | <div class="wifeichiran2018"> <a title="米山 ゆうな" href="teigaku/model/no/1697" rel="bookmark"> <img src='//p02.mywife.cc/girl/01697/thumb.jpg' width="99%"></a> | Syntax not understood |
| 384 | <p><a title="米山 ゆうな" href="teigaku/model/no/1697" rel="bookmark"><b><br> | Syntax not understood |
| 385 | 米山 ゆうな</b></a></p> | Syntax not understood |
| 386 | <p>ご主人の行き過ぎた束縛に悩む人妻と出会いました。結婚前は…</p> | Syntax not understood |
| 387 | <p><a class="btn btn-default" href="teigaku/model/no/1697" role="button">続きを読む »</a></p> | Syntax not understood |
| 388 | <div class="clear"></div> | Syntax not understood |
| 389 | </div> | Syntax not understood |
| 391 | <!--</div>--> | Syntax not understood |
| 393 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 395 | <div class="wifeichiran2018"> <a title="倖田 らん 蒼い再会" href="teigaku/model/no/1696" rel="bookmark"> <img src='//p02.mywife.cc/girl/01696/thumb.jpg' width="99%"></a> | Syntax not understood |
| 396 | <p><a title="倖田 らん 蒼い再会" href="teigaku/model/no/1696" rel="bookmark"><b><br> | Syntax not understood |
| 397 | 倖田 らん 蒼い再会</b></a></p> | Syntax not understood |
| 398 | <p>前回の情事からしばらくして、さらなる刺激を求めて倖田さんが姿を…</p> | Syntax not understood |
| 399 | <p><a class="btn btn-default" href="teigaku/model/no/1696" role="button">続きを読む »</a></p> | Syntax not understood |
| 400 | <div class="clear"></div> | Syntax not understood |
| 401 | </div> | Syntax not understood |
| 403 | <!--</div>--> | Syntax not understood |
| 405 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 407 | <div class="wifeichiran2018"> <a title="野々村 美雨" href="teigaku/model/no/1695" rel="bookmark"> <img src='//p02.mywife.cc/girl/01695/thumb.jpg' width="99%"></a> | Syntax not understood |
| 408 | <p><a title="野々村 美雨" href="teigaku/model/no/1695" rel="bookmark"><b><br> | Syntax not understood |
| 409 | 野々村 美雨</b></a></p> | Syntax not understood |
| 410 | <p>今宵出会ったのは、度重なるご主人の浮気に悩む人妻。結婚後…</p> | Syntax not understood |
| 411 | <p><a class="btn btn-default" href="teigaku/model/no/1695" role="button">続きを読む »</a></p> | Syntax not understood |
| 412 | <div class="clear"></div> | Syntax not understood |
| 413 | </div> | Syntax not understood |
| 415 | <!--</div>--> | Syntax not understood |
| 417 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 419 | <div class="wifeichiran2018"> <a title="秋川 美羽 蒼い再会" href="teigaku/model/no/1694" rel="bookmark"> <img src='//p02.mywife.cc/girl/01694/thumb.jpg' width="99%"></a> | Syntax not understood |
| 420 | <p><a title="秋川 美羽 蒼い再会" href="teigaku/model/no/1694" rel="bookmark"><b><br> | Syntax not understood |
| 421 | 秋川 美羽 蒼い再会</b></a></p> | Syntax not understood |
| 422 | <p>Hカップの爆乳ボディで興奮を誘発させてくれた秋川さんと再会…</p> | Syntax not understood |
| 423 | <p><a class="btn btn-default" href="teigaku/model/no/1694" role="button">続きを読む »</a></p> | Syntax not understood |
| 424 | <div class="clear"></div> | Syntax not understood |
| 425 | </div> | Syntax not understood |
| 427 | <!--</div>--> | Syntax not understood |
| 429 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 431 | <div class="wifeichiran2018"> <a title="結城 里英" href="teigaku/model/no/1693" rel="bookmark"> <img src='//p02.mywife.cc/girl/01693/thumb.jpg' width="99%"></a> | Syntax not understood |
| 432 | <p><a title="結城 里英" href="teigaku/model/no/1693" rel="bookmark"><b><br> | Syntax not understood |
| 433 | 結城 里英</b></a></p> | Syntax not understood |
| 434 | <p>清楚でとても可愛らしい奥様と出会いました。ですが、見かけに…</p> | Syntax not understood |
| 435 | <p><a class="btn btn-default" href="teigaku/model/no/1693" role="button">続きを読む »</a></p> | Syntax not understood |
| 436 | <div class="clear"></div> | Syntax not understood |
| 437 | </div> | Syntax not understood |
| 439 | <!--</div>--> | Syntax not understood |
| 441 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 443 | <div class="wifeichiran2018"> <a title="三好 翔 蒼い再会" href="teigaku/model/no/1692" rel="bookmark"> <img src='//p02.mywife.cc/girl/01692/thumb.jpg' width="99%"></a> | Syntax not understood |
| 444 | <p><a title="三好 翔 蒼い再会" href="teigaku/model/no/1692" rel="bookmark"><b><br> | Syntax not understood |
| 445 | 三好 翔 蒼い再会</b></a></p> | Syntax not understood |
| 446 | <p>高嶺の花という表現にぴったりの三好さん。今夜もさらなる快楽…</p> | Syntax not understood |
| 447 | <p><a class="btn btn-default" href="teigaku/model/no/1692" role="button">続きを読む »</a></p> | Syntax not understood |
| 448 | <div class="clear"></div> | Syntax not understood |
| 449 | </div> | Syntax not understood |
| 451 | <!--</div>--> | Syntax not understood |
| 453 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 455 | <div class="wifeichiran2018"> <a title="石原 夏蓮" href="teigaku/model/no/1691" rel="bookmark"> <img src='//p02.mywife.cc/girl/01691/thumb.jpg' width="99%"></a> | Syntax not understood |
| 456 | <p><a title="石原 夏蓮" href="teigaku/model/no/1691" rel="bookmark"><b><br> | Syntax not understood |
| 457 | 石原 夏蓮</b></a></p> | Syntax not understood |
| 458 | <p>「不倫願望を満たしてほしい。」と不倫サイトに書き込みをして…</p> | Syntax not understood |
| 459 | <p><a class="btn btn-default" href="teigaku/model/no/1691" role="button">続きを読む »</a></p> | Syntax not understood |
| 460 | <div class="clear"></div> | Syntax not understood |
| 461 | </div> | Syntax not understood |
| 463 | <!--</div>--> | Syntax not understood |
| 465 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 467 | <div class="wifeichiran2018"> <a title="川畑 エミリー 蒼い再会" href="teigaku/model/no/1690" rel="bookmark"> <img src='//p02.mywife.cc/girl/01690/thumb.jpg' width="99%"></a> | Syntax not understood |
| 468 | <p><a title="川畑 エミリー 蒼い再会" href="teigaku/model/no/1690" rel="bookmark"><b><br> | Syntax not understood |
| 469 | 川畑 エミリー 蒼い再会</b></a></p> | Syntax not understood |
| 470 | <p>濃厚淫乱な性交を魅せつけてくれたエミリーさんと再会しました…</p> | Syntax not understood |
| 471 | <p><a class="btn btn-default" href="teigaku/model/no/1690" role="button">続きを読む »</a></p> | Syntax not understood |
| 472 | <div class="clear"></div> | Syntax not understood |
| 473 | </div> | Syntax not understood |
| 475 | <!--</div>--> | Syntax not understood |
| 477 | <!--<div class="col-md-4 wifecon">--> | Syntax not understood |
| 479 | <div class="wifeichiran2018"> <a title="中田 凛子" href="teigaku/model/no/1689" rel="bookmark"> <img src='//p02.mywife.cc/girl/01689/thumb.jpg' width="99%"></a> | Syntax not understood |
| 480 | <p><a title="中田 凛子" href="teigaku/model/no/1689" rel="bookmark"><b><br> | Syntax not understood |
| 481 | 中田 凛子</b></a></p> | Syntax not understood |
| 482 | <p>趣味は一人エッチだという凛子さん。毎日の日課の様にアダルト動画…</p> | Syntax not understood |
| 483 | <p><a class="btn btn-default" href="teigaku/model/no/1689" role="button">続きを読む »</a></p> | Syntax not understood |
| 484 | <div class="clear"></div> | Syntax not understood |
| 485 | </div> | Syntax not understood |
| 487 | <!--</div>--> | Syntax not understood |
| 488 | <div> </div> | Syntax not understood |
| 489 | </div> | Syntax not understood |
| 490 | </div> | Syntax not understood |
| 492 | <!-- ページ2 --> | Syntax not understood |
| 493 | <div class="Pagination"> <div class="pagenation-btm"> | Syntax not understood |
| 495 | <a class="on-this-page" href="index?p=1">1</a> | Syntax not understood |
| 496 | <a href="index?p=2">2</a></li> | Syntax not understood |
| 497 | <a href="index?p=3">3</a></li> | Syntax not understood |
| 498 | <a href="index?p=4">4</a></li> | Syntax not understood |
| 499 | <a href="index?p=27">最後</a> | Syntax not understood |
| 500 | </div> | Syntax not understood |
| 504 | </div> | Syntax not understood |
| 506 | <!-- /ページ2 --> | Syntax not understood |
| 508 | <!-- ページ | Syntax not understood |
| 509 | <p class="wifewaku2"><center> | Syntax not understood |
| 510 | <div class="archive-nav section-inner"> | Syntax not understood |
| 511 | <div class="pagenation-btm"> | Syntax not understood |
| 513 | <a class="on-this-page" href="index?p=1">1</a> | Syntax not understood |
| 514 | <a href="index?p=2">2</a></li> | Syntax not understood |
| 515 | <a href="index?p=3">3</a></li> | Syntax not understood |
| 516 | <a href="index?p=4">4</a></li> | Syntax not understood |
| 517 | <a href="index?p=27">最後</a> | Syntax not understood |
| 518 | </div> | Syntax not understood |
| 523 | <div class="clear"></div> | Syntax not understood |
| 524 | </div> | Syntax not understood |
| 525 | </center> | Syntax not understood |
| 526 | </p> | Syntax not understood |
| 527 | --> | Syntax not understood |
| 528 | <!-- /ページ --> | Syntax not understood |
| 530 | <p class="color01"> | Syntax not understood |
| 531 | <center> | Syntax not understood |
| 532 | <a title="" href="/overdays"></a> | Syntax not understood |
| 533 | </center> | Syntax not understood |
| 534 | </p> | Syntax not understood |
| 535 | </div> | Syntax not understood |
| 536 | <div class="jumbotron color02"> | Syntax not understood |
| 537 | <footer> | Syntax not understood |
| 538 | <center> | Syntax not understood |
| 539 | <a href="/tokutei.html" role="button">特定商取引</a> <a href="/terms/law.html" role="button">風営法に基づく届出</a> <a href="/terms/term.html" role="button">利用規約</a> <a href="/terms/privacy.html" role="button">個人情報保護方針</a><br> | Syntax not understood |
| 540 | 当サイトに掲載されている画像やムービーには著作権、肖像権があります。<br> | Syntax not understood |
| 541 | 無断転載・流用を禁じます。Copyright © since 2004 舞ワイフ All Rights Reserved. | Syntax not understood |
| 542 | </center> | Syntax not understood |
| 544 | </footer> | Syntax not understood |
| 545 | </div> | Syntax not understood |
| 547 | <!-- jQuery (necessary for Bootstrap's JavaScript plugins) --> | Syntax not understood |
| 548 | <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script> | Unknown directive |
| 549 | <!-- Include all compiled plugins (below), or include individual files as needed --> | Syntax not understood |
| 550 | <script src="/js/bootstrap.min.js"></script> | Syntax not understood |
| 551 | <!--メニュー--> | Syntax not understood |
| 552 | <script src="/js/menu-wrap.js"></script> | Syntax not understood |
| 554 | <!--Google--> | Syntax not understood |
| 556 | <!-- Global site tag (gtag.js) - Google Analytics --> | Syntax not understood |
| 557 | <script async src="https://www.googletagmanager.com/gtag/js?id=UA-142592223-2"></script> | Unknown directive |
| 558 | <script> | Syntax not understood |
| 559 | window.dataLayer = window.dataLayer || []; | Syntax not understood |
| 560 | function gtag(){dataLayer.push(arguments);} | Syntax not understood |
| 561 | gtag('js', new Date()); | Syntax not understood |
| 563 | gtag('config', 'UA-142592223-2'); | Syntax not understood |
| 564 | </script> | Syntax not understood |
| 567 | <!--/Google--> | Syntax not understood |
| 569 | </body> | Syntax not understood |
| 570 | </html> | Syntax not understood |
Content Best Practices
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.
Progressive Web App
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of mywife.cc. This includes details about web app manifests.Fast and reliable
Page load is fast enough on mobile networks Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.
PWA Optimized
Redirects HTTP traffic to HTTPS It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 mywife.cc on mobile screens.
Contains some content when JavaScript is not available Apps should display alternative content for when JavaScript is disabled.
Fast and reliable
Current page does not respond with a 200 when offline In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.
Installable
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 |
|---|
| http://mywife.cc/ |
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.
Web app manifest does not meet the installability requirements User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data
PWA Optimized
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: | 133.242.235.248 |
| Continent: | Asia |
| Country: | Japan  |
| Region: | |
| City: | |
| Longitude: | 139.69 |
| Latitude: | 35.69 |
| Currencies: | JPY |
| Languages: | Japanese |
Web Hosting Provider
| Name | IP Address |
|---|---|
| Japan Network Information Center |
Registration
Domain Registrant
| Private Registration: | No |
| Name: | Toyo Yasunari |
| Organization: | Toyo |
| Country: | JP |
| City: | Shibuya-ku |
| State: | Tokyo |
| Post Code: | 150-0002 |
| Email: | shimizu@s-soul.net |
| Phone: | +81.364185599 |
Note: Registration information is derived from various sources and may be inaccurate.
Domain Registrar
| Name | IP Address |
|---|---|
| GMO INTERNET, INC. | 104.17.28.100 |
Security
Visitor Safety
| Mature Content: | Yes |
| McAfee WebAdvisor Rating: | Safe |
| WOT Rating: | 2.5/5 |
| WOT Trustworthiness: | 50/100 |
| WOT Child Safety: | 37/100 |
Note: Safety information is not guaranteed.
SSL/TLS Certificate
| Issued To: | *.mywife.cc |
| Issued By: | GlobalSign GCC R3 DV TLS CA 2020 |
| Valid From: | 17th December, 2020 |
| Valid To: | 21st August, 2021 |
| Subject: | CN = *.mywife.cc |
| Hash: | f424b1ea |
| Issuer: | CN = GlobalSign GCC R3 DV TLS CA 2020 O = GlobalSign nv-sa S = BE |
| Version: | 2 |
| Serial Number: | 15857269484084496781268894082 |
| Serial Number (Hex): | 333CD36D3774C104F0624182 |
| Valid From: | 17th December, 2024 |
| Valid To: | 21st August, 2024 |
| Signature Algorithm (Short Name): | RSA-SHA256 |
| Signature Algorithm (Long Name): | sha256WithRSAEncryption |
| Authority Key Identifier: | keyid:0D:98:C0:73:7F:AB:BD:BD:D9:47:4B:49:AD:0A:4A:0C:AC:3E:C7:7C |
| Extended Key Usage: | TLS Web Server Authentication, TLS Web Client Authentication |
| CRL Distribution Points: | Full Name: URI:http://crl.globalsign.com/gsgccr3dvtlsca2020.crl |
| Certificate Policies: | Policy: 1.3.6.1.4.1.4146.1.10 CPS: https://www.globalsign.com/repository/ Policy: 2.23.140.1.2.1 |
| Authority Information Access: | CA Issuers - URI:http://secure.globalsign.com/cacert/gsgccr3dvtlsca2020.crt OCSP - URI:http://ocsp.globalsign.com/gsgccr3dvtlsca2020 |
| SCT List: | Signed Certificate Timestamp: Version : v1 (0x0) Log ID : EE:C0:95:EE:8D:72:64:0F:92:E3:C3:B9:1B:C7:12:A3: 69:6A:09:7B:4B:6A:1A:14:38:E6:47:B2:CB:ED:C5:F9 Timestamp : Dec 17 01:43:03.315 2020 GMT Extensions: none Signature : ecdsa-with-SHA256 30:45:02:20:38:4A:1D:C1:40:ED:0A:91:A3:AA:75:40: DA:CC:9C:A5:E7:8D:2A:1B:B2:2B:30:94:5F:2F:22:75: 21:F4:FA:15:02:21:00:F6:2C:F3:7B:86:B1:16:56:58: 24:58:5D:F7:38:33:AC:27:82:A7:7A:85:3F:27:E4:01: E5:60:B1:67:64:33:36 Signed Certificate Timestamp: Version : v1 (0x0) Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E: E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3 Timestamp : Dec 17 01:43:03.273 2020 GMT Extensions: none Signature : ecdsa-with-SHA256 30:44:02:20:5C:CB:35:EF:67:8F:DD:60:A4:3A:F9:3A: C3:13:D7:64:14:DF:CB:A3:B0:46:D7:B2:9D:71:2A:7F: 7E:DB:7A:96:02:20:67:23:44:B1:F9:8A:FA:B2:69:19: 23:84:7E:6E:E5:71:93:CF:AB:EA:7A:E1:F8:0D:6F:A0: 59:2E:6F:55:A1:3A |
| Key Usage: | Digital Signature, Key Encipherment |
| Basic Constraints: | CA:FALSE |
| Subject Alternative Name: | DNS:mywife.cc DNS:*.mywife.cc |
Technical
DNS Lookup
A Records
| Host | IP Address | Class | TTL |
|---|---|---|---|
| mywife.cc. | 133.242.235.248 | IN | 3599 |
NS Records
| Host | Nameserver | Class | TTL |
|---|---|---|---|
| mywife.cc. | 01.dnsv.jp. | IN | 21599 |
| mywife.cc. | 02.dnsv.jp. | IN | 21599 |
| mywife.cc. | 03.dnsv.jp. | IN | 21599 |
| mywife.cc. | 04.dnsv.jp. | IN | 21599 |
MX Records
| Priority | Host | Server | Class | TTL |
|---|---|---|---|---|
| 10 | mywife.cc. | mx.mywife.cc. | IN | 3599 |
SOA Records
| Domain Name | Primary NS | Responsible Email | TTL |
|---|---|---|---|
| mywife.cc. | 01.dnsv.jp. | hostmaster.dnsv.jp. | 21599 |
TXT Records
| Host | Value | Class | TTL |
|---|---|---|---|
| mywife.cc. | google-site-verification=AiNzWjRAdYsw_6zwxOnJA1BsBD_5swhGv8e5AQ4cSVM | IN | 3599 |
| mywife.cc. | v=spf1 | IN | 3599 |
HTTP Response Headers
| HTTP-Code: | HTTP/1.1 200 OK |
| Date: | 4th February, 2021 |
| Server: | Apache |
| Content-Type: | text/html; charset=UTF-8 |
| X-Powered-By: | PHP/5.6.14 |
| Set-Cookie: | * |
Whois Lookup
| Created: | 7th June, 2004 |
| Changed: | 21st June, 2020 |
| Expires: | 7th June, 2021 |
| Registrar: | GMO INTERNET, INC. |
| Status: |
| Nameservers: | 01.dnsv.jp 02.dnsv.jp 03.dnsv.jp 04.dnsv.jp |
| Owner Name: | shinji nagumo |
| Owner Organization: | SOUL Inc. |
| Owner Street: | 6-23-2 Jingumae 25SY Bill 7F |
| Owner Post Code: | 150-0001 |
| Owner City: | Shibuya Ku |
| Owner State: | Tokyo |
| Owner Country: | JP |
| Owner Phone: | 03-6805-0105 |
| Owner Email: | saka@s-soul.net |
| Admin Name: | shinji nagumo |
| Admin Organization: | SOUL Inc. |
| Admin Street: | 6-23-2 Jingumae 25SY Bill 7F |
| Admin Post Code: | 150-0001 |
| Admin City: | Shibuya Ku |
| Admin State: | Tokyo |
| Admin Country: | JP |
| Admin Phone: | 03-6805-0105 |
| Admin Email: | saka@s-soul.net |
| Tech Name: | INTERLINK Gonbei INTERLINK Gonbei |
| Tech Organization: | INTERLINK |
| Tech Street: | 3-1-1 higashi-ikebukuro |
| Tech Post Code: | 170-6035 |
| Tech City: | Toshima |
| Tech State: | Tokyo |
| Tech Country: | JP |
| Tech Phone: | +81.339853711 |
| Tech Email: | support@gonbei.jp |
| Full Whois: | Domain Name: mywife.cc
Registry Domain ID: 86482000_DOMAIN_CC-VRSN Registrar WHOIS Server: whois.discount-domain.com Registrar URL: http://www.onamae.com Updated Date: 2020-06-21T00:37:07Z Creation Date: 2004-07-06T01:28:05Z Registrar Registration Expiration Date: 2021-07-06T01:28:05Z Registrar: GMO INTERNET, INC. Registrar IANA ID: 49 Registrar Abuse Contact Email: abuse@gmo.jp Registrar Abuse Contact Phone: +81.337709199 Domain Status: ACTIVE Registry Registrant ID: Registrant Name: shinji nagumo Registrant Organization: SOUL Inc. Registrant Street: 6-23-2 Jingumae Registrant Street: 25SY Bill 7F Registrant City: Shibuya Ku Registrant State/Province: Tokyo Registrant Postal Code: 150-0001 Registrant Country: JP Registrant Phone: 03-6805-0105 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: saka@s-soul.net Registry Admin ID: Admin Name: shinji nagumo Admin Organization: SOUL Inc. Admin Street: 6-23-2 Jingumae Admin Street: 25SY Bill 7F Admin City: Shibuya Ku Admin State/Province: Tokyo Admin Postal Code: 150-0001 Admin Country: JP Admin Phone: 03-6805-0105 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: saka@s-soul.net Registry Tech ID: Tech Name: INTERLINK Gonbei INTERLINK Gonbei Tech Organization: INTERLINK Tech Street: 3-1-1 higashi-ikebukuro Tech City: Toshima Tech State/Province: Tokyo Tech Postal Code: 170-6035 Tech Country: JP Tech Phone: +81.339853711 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: support@gonbei.jp Name Server: 01.dnsv.jp Name Server: 02.dnsv.jp Name Server: 03.dnsv.jp Name Server: 04.dnsv.jp DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2020-06-21T00:37:07Z <<< For more information on Whois status codes, please visit https://icann.org/epp |
Nameservers
| Name | IP Address |
|---|---|
| 01.dnsv.jp | 157.7.32.53 |
| 02.dnsv.jp | 157.7.33.53 |
| 03.dnsv.jp | 157.7.34.53 |
| 04.dnsv.jp | 157.7.35.53 |
Love W3 Snoop?
Share This 
