Skip to content
Audit Complete

Results for https://renren.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 22:46 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Nginx · 860 peers
You 75
·
Avg 73
At average
0 50 100
Better than 63% of Nginx sites See full Nginx benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
5

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › 404 Error Page
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Frenren.com)](https://beavercheck.com/results/d5d77114-f34d-4ba9-ab76-267a0060478a)
<a href="https://beavercheck.com/results/d5d77114-f34d-4ba9-ab76-267a0060478a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Frenren.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Frenren.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

7 warning

7 barrier(s) likely increasing bounce by ~16%.

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

¥1,575 investment → ¥1.77/month returns + CNY 50,000,000 risk avoided

Payback period: > 2 years First-year ROI: -99%

Investment

¥1,575

4h · 5 findings

Monthly returns

¥1.77 /mo

~¥21 / year

  • Bandwidth savings ¥1.77

Regulatory risk avoided

CNY 50,000,000

if kept compliant

  • PIPL CNY 50,000,000

¥525 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

¥1,575

4.5 developer hours at ¥350/hr

Based on China rates (¥350/hr)

Quick wins
¥525 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
¥ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

¥4,166,668 / month at risk

~¥50,000,021 / year if left unfixed

Compliance Risk

¥50,000,000

PIPL
  • No privacy policy link detected
    PIPL: CNY 100,000 – CNY 50,000,000
  • Privacy Policy not detected
    PIPL: CNY 100,000 – CNY 50,000,000

Bandwidth Waste

¥1.77 /mo

3091.3 MB/mo × 0.571 CNY/GB

  • Optimize transfer: save ~309 KB per page load
    Saves ¥1.77/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

781 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

781 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.007

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.79 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

781 ms

Detailed Report

Audit breakdown by category with detailed findings.

100

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
renren.com/img/background.png0.0 ms838.1 KiB
renren.com/img/notice2.png0.0 ms158.1 KiB
renren.com/img/header.png0.0 ms6.1 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
body > div.img body > div.img
renren.com/img/background.png837.0 KiB499.5 KiB
人人网 div.h5 > div.container > div.content > img
renren.com/img/header.png6.0 KiB5.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
人人网 div.h5 > div.container > div.content > img
renren.com/img/header.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Time to Interactive 0.8 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 1,006 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.2 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 210 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 210 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Touch targets have sufficient size and spacing.
Document has a main landmark.
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="en">Syntax not understood
4<head>Syntax not understood
5 <meta charset="UTF-8">Syntax not understood
6 <meta name="viewport" content="width=device-width, initial-scale=1.0">Syntax not understood
7 <title>人人网</title>Syntax not understood
8 <style>Syntax not understood
9 html,body {Syntax not understood
10 height: 100%;Unknown directive
11 width: 100%;Unknown directive
12 margin: 0;Unknown directive
13 padding: 0;Unknown directive
14 }Syntax not understood
15 body {Syntax not understood
16 position: relative;Unknown directive
17 }Syntax not understood
18 .img{Syntax not understood
19 width: 100%;Unknown directive
20 height: 100%;Unknown directive
21 background: url('./img/background.png') no-repeat;Unknown directive
22 overflow: hidden;Unknown directive
23 position: absolute;Unknown directive
24 z-index: 1;Unknown directive
25 top: 0;Unknown directive
26 left: 0;Unknown directive
27 }Syntax not understood
28 .box{Syntax not understood
29 width: 100%;Unknown directive
30 height: 100%;Unknown directive
31 position: relative;Unknown directive
32 z-index: 100;Unknown directive
33 }Syntax not understood
34 .pc{Syntax not understood
35 width: 100%;Unknown directive
36 height: 100%;Unknown directive
37 display: flex;Unknown directive
38 justify-content: center;Unknown directive
39 align-items: center;Unknown directive
40 flex-flow: column;Unknown directive
41 }Syntax not understood
42 .h5{Syntax not understood
43 display: none;Unknown directive
44 }Syntax not understood
45 .pc-img{Syntax not understood
46 width: 100%;Unknown directive
47 height: calc(100% - 100px);Unknown directive
48 overflow: hidden;Unknown directive
49 }Syntax not understood
50 .pc-img img{Syntax not understood
51 max-width: 100%;Unknown directive
52 }Syntax not understood
53 .text {Syntax not understood
54 font-size: 12px;Unknown directive
55 display: flex;Unknown directive
56 align-items: center;Unknown directive
57 justify-content: center;Unknown directive
58 flex-flow: column;Unknown directive
59 height: 100px;Unknown directive
60 color: hsl(0deg 0% 100% / 50%);Unknown directive
61 }Syntax not understood
62 .text a{Syntax not understood
63 color: hsl(0deg 0% 100% / 50%);Unknown directive
64 }Syntax not understood
65 .a1 {Syntax not understood
66 display: flex;Unknown directive
67 margin-top: 2px;Unknown directive
68 }Syntax not understood
69 .a2 {Syntax not understood
70 margin-right: 20px;Unknown directive
71 }Syntax not understood
72 .a3 {Syntax not understood
73 margin-right: 10px;Unknown directive
74 }Syntax not understood
75 .a4 {Syntax not understood
76 justify-content: space-between;Unknown directive
77 min-width: 400px;Unknown directive
78 }Syntax not understood
80 @media screen and (max-width: 500px) {Unknown directive
81 .img{Syntax not understood
82 overflow: hidden;Unknown directive
83 position: absolute;Unknown directive
84 z-index: 1;Unknown directive
85 top: 0;Unknown directive
86 left: 0;Unknown directive
87 }Syntax not understood
88 .pc{Syntax not understood
89 display: none;Unknown directive
90 }Syntax not understood
91 .h5{Syntax not understood
92 display: block;Unknown directive
93 position: relative;Unknown directive
94 height: 100%;Unknown directive
95 width: 100%;Unknown directive
96 display: flex;Unknown directive
97 justify-content: center;Unknown directive
98 align-items: center;Unknown directive
99 flex-flow: column;Unknown directive
100 }Syntax not understood
102 .container{Syntax not understood
103 position: absolute;Unknown directive
104 bottom: 109px;Unknown directive
105 width: calc(90%);Unknown directive
106 margin: 0 auto;Unknown directive
107 height: calc(100% - 120px);Unknown directive
108 display: flex;Unknown directive
109 justify-content: center;Unknown directive
110 align-items: center;Unknown directive
111 }Syntax not understood
112 .container .content{Syntax not understood
113 background: #fff;Unknown directive
114 border-radius: 8px;Unknown directive
115 padding: 10px 20px;Unknown directive
116 display: flex;Unknown directive
117 justify-content: center;Unknown directive
118 flex-flow: column;Unknown directive
119 }Syntax not understood
120 .container .content img{Syntax not understood
121 max-width: 80px;Unknown directive
122 }Syntax not understood
123 .container .content p{Syntax not understood
124 font-size: 14px;Unknown directive
125 margin: 0;Unknown directive
126 margin-top: 13px;Unknown directive
127 }Syntax not understood
128 .icp{Syntax not understood
129 width: calc(90%);Unknown directive
130 margin: 0 auto;Unknown directive
131 font-size: 12px;Unknown directive
132 color: hsl(0deg 0% 100% / 50%);Unknown directive
133 position: absolute;Unknown directive
134 bottom: 20px;Unknown directive
135 padding: 10px 0;Unknown directive
136 }Syntax not understood
137 .icp p{Syntax not understood
138 margin: 0;Unknown directive
139 }Syntax not understood
140 .icp a{Syntax not understood
141 color: hsl(0deg 0% 100% / 50%);Unknown directive
142 }Syntax not understood
143 .h5-a1{Syntax not understood
144 display: flex;Unknown directive
145 justify-content: center;Unknown directive
146 margin-top: 3px;Unknown directive
147 }Syntax not understood
148 .h5-a1 div{Syntax not understood
149 width: 50%;Unknown directive
150 }Syntax not understood
151 .h5-a2{Syntax not understood
152 margin-top: 3px;Unknown directive
153 display: flex;Unknown directive
154 }Syntax not understood
155 .h5-a3{Syntax not understood
156 justify-content: space-between;Unknown directive
157 }Syntax not understood
158 .h5-a4{Syntax not understood
159 display: flex;Unknown directive
160 margin-top: 3px;Unknown directive
161 }Syntax not understood
162 }Syntax not understood
163 </style>Syntax not understood
164</head>Syntax not understood
166<body>Syntax not understood
167<div class="img"></div>Syntax not understood
168<div class="box">Syntax not understood
169 <div class="pc">Syntax not understood
170 <div class="pc-img">Syntax not understood
171 <img src="./img/notice2.png" alt="">Syntax not understood
172 </div>Syntax not understood
173 <div class="text">Syntax not understood
174 <div class="a1">Syntax not understood
175 <div class="a2">公司全称:成都人人互娱科技有限公司 </div>Syntax not understood
176 </div>Syntax not understood
177 <div class="a1 a4">Syntax not understood
178 <div>违法信息不良举报电话:010-87538607</div>Syntax not understood
179 <div>邮箱:jubao@infinities.com.cn</div>Syntax not understood
180 </div>Syntax not understood
181 <div class="a1">Syntax not understood
182 <a class="a3" href="https://beian.miit.gov.cn/" target="_blank" data-v-ae6a3fd4="">蜀ICP备2021009929号-11</a>Unknown directive
183 </div>Syntax not understood
184 <div>人人网©2025</div>Syntax not understood
185 </div>Syntax not understood
186 </div>Syntax not understood
187 <div class="h5">Syntax not understood
188 <div class="container">Syntax not understood
189 <div class="content">Syntax not understood
190 <img src="./img/header.png" alt="人人网"/>Syntax not understood
191 <p style="font-weight: bold;font-size: 16px;margin-top: 20px;">人人网服务升级公告</p>Unknown directive
192 <p>亲爱的人人网用户们,</p>Syntax not understood
193 <p>感谢您一直以来的陪伴与支持!我们想告诉您,人人网正在进行一次“换车”升级--就像您的燃油车开了多年,也想试试新能源车一样。</p>Syntax not understood
194 <p>在这期间,您在人人网上的所有数据都得到了严格的保护,确保您的个人信息和隐私安全不受任何威胁。您的数据安全,对我们来说至关重要。</p>Syntax not understood
195 <p>请耐心等待我们的“新车”上路,届时您将享受到更加稳定安全、丰富的社交体验,让我们共同期待人人网的全新启程!</p>Syntax not understood
196 <p>此致!</p>Syntax not understood
197 <p style="margin-bottom: 0;font-weight: bold;">人人网团队</p>Unknown directive
198 <p style="margin: 0;font-weight: bold;">2024年12月2日</p>Unknown directive
199 </div>Syntax not understood
200 </div>Syntax not understood
201 <div class="icp">Syntax not understood
202 <div class="h5-a1">公司全称:成都人人互娱科技有限公司</div>Syntax not understood
203 <div class="h5-a1">违法信息不良举报电话:010-87538607</div>Syntax not understood
204 <div class="h5-a1">邮箱:jubao@infinities.com.cn</div>Syntax not understood
205 <div class="h5-a1">Syntax not understood
206 <div><a href="https://beian.miit.gov.cn/" target="_blank" data-v-ae6a3fd4="">蜀ICP备2021009929号-11</a></div>Unknown directive
207 </div>Syntax not understood
208 <div class="h5-a1">人人网©2025</div>Syntax not understood
209 </div>Syntax not understood
210 </div>Syntax not understood
215</div>Syntax not understood
217</body>Syntax not understood
219</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

251 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

406 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.31 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

406 ms

Detailed Report

Audit breakdown by category with detailed findings.

99

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
renren.com/img/background.png0.0 ms838.1 KiB
renren.com/img/notice2.png0.0 ms158.1 KiB
renren.com/img/header.png0.0 ms6.1 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
body > div.img body > div.img
renren.com/img/background.png837.0 KiB499.5 KiB
div.box > div.pc > div.pc-img > img div.box > div.pc > div.pc-img > img
renren.com/img/notice2.png157.8 KiB79.8 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-1-IMG
nodeLabel: div.box > div.pc > div.pc-img > img
path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,0,IMG
selector: div.box > div.pc > div.pc-img > img
snippet: <img src="./img/notice2.png" alt="">

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.box > div.pc > div.pc-img > img div.box > div.pc > div.pc-img > img
renren.com/img/notice2.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Time to Interactive 0.4 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 1,006 KiB
Minimizes main-thread work 0.0 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 200 ms
Server Backend Latencies 50 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 250 ms
INP breakdown
User Timing marks and measures
JavaScript execution time
Avoid long main-thread tasks
Avoid non-composited animations
Avoid large layout shifts
100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Touch targets have sufficient size and spacing.
Document has a main landmark.
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="en">Syntax not understood
4<head>Syntax not understood
5 <meta charset="UTF-8">Syntax not understood
6 <meta name="viewport" content="width=device-width, initial-scale=1.0">Syntax not understood
7 <title>人人网</title>Syntax not understood
8 <style>Syntax not understood
9 html,body {Syntax not understood
10 height: 100%;Unknown directive
11 width: 100%;Unknown directive
12 margin: 0;Unknown directive
13 padding: 0;Unknown directive
14 }Syntax not understood
15 body {Syntax not understood
16 position: relative;Unknown directive
17 }Syntax not understood
18 .img{Syntax not understood
19 width: 100%;Unknown directive
20 height: 100%;Unknown directive
21 background: url('./img/background.png') no-repeat;Unknown directive
22 overflow: hidden;Unknown directive
23 position: absolute;Unknown directive
24 z-index: 1;Unknown directive
25 top: 0;Unknown directive
26 left: 0;Unknown directive
27 }Syntax not understood
28 .box{Syntax not understood
29 width: 100%;Unknown directive
30 height: 100%;Unknown directive
31 position: relative;Unknown directive
32 z-index: 100;Unknown directive
33 }Syntax not understood
34 .pc{Syntax not understood
35 width: 100%;Unknown directive
36 height: 100%;Unknown directive
37 display: flex;Unknown directive
38 justify-content: center;Unknown directive
39 align-items: center;Unknown directive
40 flex-flow: column;Unknown directive
41 }Syntax not understood
42 .h5{Syntax not understood
43 display: none;Unknown directive
44 }Syntax not understood
45 .pc-img{Syntax not understood
46 width: 100%;Unknown directive
47 height: calc(100% - 100px);Unknown directive
48 overflow: hidden;Unknown directive
49 }Syntax not understood
50 .pc-img img{Syntax not understood
51 max-width: 100%;Unknown directive
52 }Syntax not understood
53 .text {Syntax not understood
54 font-size: 12px;Unknown directive
55 display: flex;Unknown directive
56 align-items: center;Unknown directive
57 justify-content: center;Unknown directive
58 flex-flow: column;Unknown directive
59 height: 100px;Unknown directive
60 color: hsl(0deg 0% 100% / 50%);Unknown directive
61 }Syntax not understood
62 .text a{Syntax not understood
63 color: hsl(0deg 0% 100% / 50%);Unknown directive
64 }Syntax not understood
65 .a1 {Syntax not understood
66 display: flex;Unknown directive
67 margin-top: 2px;Unknown directive
68 }Syntax not understood
69 .a2 {Syntax not understood
70 margin-right: 20px;Unknown directive
71 }Syntax not understood
72 .a3 {Syntax not understood
73 margin-right: 10px;Unknown directive
74 }Syntax not understood
75 .a4 {Syntax not understood
76 justify-content: space-between;Unknown directive
77 min-width: 400px;Unknown directive
78 }Syntax not understood
80 @media screen and (max-width: 500px) {Unknown directive
81 .img{Syntax not understood
82 overflow: hidden;Unknown directive
83 position: absolute;Unknown directive
84 z-index: 1;Unknown directive
85 top: 0;Unknown directive
86 left: 0;Unknown directive
87 }Syntax not understood
88 .pc{Syntax not understood
89 display: none;Unknown directive
90 }Syntax not understood
91 .h5{Syntax not understood
92 display: block;Unknown directive
93 position: relative;Unknown directive
94 height: 100%;Unknown directive
95 width: 100%;Unknown directive
96 display: flex;Unknown directive
97 justify-content: center;Unknown directive
98 align-items: center;Unknown directive
99 flex-flow: column;Unknown directive
100 }Syntax not understood
102 .container{Syntax not understood
103 position: absolute;Unknown directive
104 bottom: 109px;Unknown directive
105 width: calc(90%);Unknown directive
106 margin: 0 auto;Unknown directive
107 height: calc(100% - 120px);Unknown directive
108 display: flex;Unknown directive
109 justify-content: center;Unknown directive
110 align-items: center;Unknown directive
111 }Syntax not understood
112 .container .content{Syntax not understood
113 background: #fff;Unknown directive
114 border-radius: 8px;Unknown directive
115 padding: 10px 20px;Unknown directive
116 display: flex;Unknown directive
117 justify-content: center;Unknown directive
118 flex-flow: column;Unknown directive
119 }Syntax not understood
120 .container .content img{Syntax not understood
121 max-width: 80px;Unknown directive
122 }Syntax not understood
123 .container .content p{Syntax not understood
124 font-size: 14px;Unknown directive
125 margin: 0;Unknown directive
126 margin-top: 13px;Unknown directive
127 }Syntax not understood
128 .icp{Syntax not understood
129 width: calc(90%);Unknown directive
130 margin: 0 auto;Unknown directive
131 font-size: 12px;Unknown directive
132 color: hsl(0deg 0% 100% / 50%);Unknown directive
133 position: absolute;Unknown directive
134 bottom: 20px;Unknown directive
135 padding: 10px 0;Unknown directive
136 }Syntax not understood
137 .icp p{Syntax not understood
138 margin: 0;Unknown directive
139 }Syntax not understood
140 .icp a{Syntax not understood
141 color: hsl(0deg 0% 100% / 50%);Unknown directive
142 }Syntax not understood
143 .h5-a1{Syntax not understood
144 display: flex;Unknown directive
145 justify-content: center;Unknown directive
146 margin-top: 3px;Unknown directive
147 }Syntax not understood
148 .h5-a1 div{Syntax not understood
149 width: 50%;Unknown directive
150 }Syntax not understood
151 .h5-a2{Syntax not understood
152 margin-top: 3px;Unknown directive
153 display: flex;Unknown directive
154 }Syntax not understood
155 .h5-a3{Syntax not understood
156 justify-content: space-between;Unknown directive
157 }Syntax not understood
158 .h5-a4{Syntax not understood
159 display: flex;Unknown directive
160 margin-top: 3px;Unknown directive
161 }Syntax not understood
162 }Syntax not understood
163 </style>Syntax not understood
164</head>Syntax not understood
166<body>Syntax not understood
167<div class="img"></div>Syntax not understood
168<div class="box">Syntax not understood
169 <div class="pc">Syntax not understood
170 <div class="pc-img">Syntax not understood
171 <img src="./img/notice2.png" alt="">Syntax not understood
172 </div>Syntax not understood
173 <div class="text">Syntax not understood
174 <div class="a1">Syntax not understood
175 <div class="a2">公司全称:成都人人互娱科技有限公司 </div>Syntax not understood
176 </div>Syntax not understood
177 <div class="a1 a4">Syntax not understood
178 <div>违法信息不良举报电话:010-87538607</div>Syntax not understood
179 <div>邮箱:jubao@infinities.com.cn</div>Syntax not understood
180 </div>Syntax not understood
181 <div class="a1">Syntax not understood
182 <a class="a3" href="https://beian.miit.gov.cn/" target="_blank" data-v-ae6a3fd4="">蜀ICP备2021009929号-11</a>Unknown directive
183 </div>Syntax not understood
184 <div>人人网©2025</div>Syntax not understood
185 </div>Syntax not understood
186 </div>Syntax not understood
187 <div class="h5">Syntax not understood
188 <div class="container">Syntax not understood
189 <div class="content">Syntax not understood
190 <img src="./img/header.png" alt="人人网"/>Syntax not understood
191 <p style="font-weight: bold;font-size: 16px;margin-top: 20px;">人人网服务升级公告</p>Unknown directive
192 <p>亲爱的人人网用户们,</p>Syntax not understood
193 <p>感谢您一直以来的陪伴与支持!我们想告诉您,人人网正在进行一次“换车”升级--就像您的燃油车开了多年,也想试试新能源车一样。</p>Syntax not understood
194 <p>在这期间,您在人人网上的所有数据都得到了严格的保护,确保您的个人信息和隐私安全不受任何威胁。您的数据安全,对我们来说至关重要。</p>Syntax not understood
195 <p>请耐心等待我们的“新车”上路,届时您将享受到更加稳定安全、丰富的社交体验,让我们共同期待人人网的全新启程!</p>Syntax not understood
196 <p>此致!</p>Syntax not understood
197 <p style="margin-bottom: 0;font-weight: bold;">人人网团队</p>Unknown directive
198 <p style="margin: 0;font-weight: bold;">2024年12月2日</p>Unknown directive
199 </div>Syntax not understood
200 </div>Syntax not understood
201 <div class="icp">Syntax not understood
202 <div class="h5-a1">公司全称:成都人人互娱科技有限公司</div>Syntax not understood
203 <div class="h5-a1">违法信息不良举报电话:010-87538607</div>Syntax not understood
204 <div class="h5-a1">邮箱:jubao@infinities.com.cn</div>Syntax not understood
205 <div class="h5-a1">Syntax not understood
206 <div><a href="https://beian.miit.gov.cn/" target="_blank" data-v-ae6a3fd4="">蜀ICP备2021009929号-11</a></div>Unknown directive
207 </div>Syntax not understood
208 <div class="h5-a1">人人网©2025</div>Syntax not understood
209 </div>Syntax not understood
210 </div>Syntax not understood
215</div>Syntax not understood
217</body>Syntax not understood
219</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback