Mobile 375 × 812

Desktop 1440 × 900

Score: 72 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Good foundation, but a few gaps could be exploited.
Major barriers for users with disabilities — up to 15% of your audience.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
18 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
7 image-in-link without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/4f4b1ebd-75cf-4090-8fdd-f8cf5d664bad)<a href="https://beavercheck.com/results/4f4b1ebd-75cf-4090-8fdd-f8cf5d664bad"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fustc.edu.cn" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fustc.edu.cnThis badge auto-updates with your latest scan result.
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.
11 barrier(s) likely increasing bounce by ~30%.
Page loads in 3.5s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 952ms over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
No HSTS header
+1% bounceReturning 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% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
2 form field(s) without a label
+4% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
Viewport disables user zoom
+2% bounceVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
Fix: Remove user-scalable=no; drop maximum-scale if it's below 2
No Open Graph tags
+2% bounceLinks 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% bounceNo 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% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
18 link(s) with generic text ("click here", "read more")
+1% bounceScreen-reader users navigating by link list see no context — and search engines can't infer relevance
Fix: Rewrite with descriptive phrases that identify the destination
No skip-to-content link
+1% bounceKeyboard 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
63 broken link(s) on the page
+5% bounceClicks 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.
¥1,925 investment → ¥6,671/month returns + CNY 50,000,000 risk avoided
¥1,925
6h · 5 findings
¥6,671 /mo
~¥80,047 / year
CNY 50,000,000
if kept compliant
¥350 — 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.
5.5 developer hours at ¥350/hr
Based on China rates (¥350/hr)
Start here for the best return on investment
¥4,166,672 / month at risk
~¥50,000,062 / year if left unfixed
¥50,000,000
+1 more
¥5.18 /mo
9061.2 MB/mo × 0.571 CNY/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
1.80 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.45 s
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.
5.33 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.
3.45 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| ustc.edu.cn/news/fonts/fontello.woff | 870 ms |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/zgtszt.png | 550.0 KiB | 524.7 KiB |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/zjzt.png | 543.9 KiB | 518.7 KiB |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/bxgdzt.png | 517.6 KiB | 492.3 KiB |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/kczt.png | 511.7 KiB | 486.4 KiB |
body > header > ::before body > header > ::before | ustc.edu.cn/news/css/globe.jpg | 157.7 KiB | 134.6 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l3.png | 29.2 KiB | 27.1 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l1.png | 29.0 KiB | 26.9 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/jiuyezhidao.png | 25.9 KiB | 23.8 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l2.png | 25.6 KiB | 23.5 KiB |
section.notice > ul > li > div.cnm | ustc.edu.cn/news/css/sh_1.jpg | 11.1 KiB | 11.1 KiB |
RSS div.container > section.inright > section.notice > a.rss | ustc.edu.cn/news/css/wif.jpg | 8.1 KiB | 8.1 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| ustc.edu.cn/news/js/jquery.js | 83.9 KiB | 41.4 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| ustc.edu.cn/news/js/jquery.js | 83.9 KiB | 35.4 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| ustc.edu.cn/images/zgtszt.png | 551.0 KiB |
| ustc.edu.cn/images/zjzt.png | 545.0 KiB |
| ustc.edu.cn/images/bxgdzt.png | 518.6 KiB |
| ustc.edu.cn/images/kczt.png | 512.8 KiB |
| ustc.edu.cn/news/images/logo.svg | 196.9 KiB |
| ustc.edu.cn/news/css/globe.jpg | 158.3 KiB |
| ustc.edu.cn/__local/D/57/DA/94AAEAEF3830793410880F98321_D453E135_1E27F.jpg | 121.2 KiB |
| ustc.edu.cn/news/js/jquery.js | 84.2 KiB |
| ustc.edu.cn/news/images/l3.png | 29.5 KiB |
| ustc.edu.cn/news/images/l1.png | 29.3 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l1.png |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l2.png |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/jiuyezhidao.png |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l3.png |
address > p > a > img address > p > a > img | ustc.edu.cn/news/images/blue.png |
div.container > address > p > img div.container > address > p > img | ustc.edu.cn/news/images/4054C9236D1DF77880F32A8AC59_C97E8483_1016.jpg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
皖公网安备34011102001530号 div.container > address > p > span |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
学校召开学生工作队伍座谈会 ul > li.picn > div.txt > h4.on |
These are opportunities to improve keyboard navigation in your application.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.boxshadow html.boxshadow |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.container > address > p > img div.container > address > p > img |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul > li.picn > div.pic > a ul > li.picn > div.pic > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > address > p > a div.container > address > p > a |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.container > address > p > img div.container > address > p > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
header > nav.main-menu > div.container > a.toggle header > nav.main-menu > div.container > a.toggle |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
To appear in search results, crawlers need access to your app.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
640 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
832 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.
2.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.
834 ms
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| ustc.edu.cn/news/fonts/fontello.woff | 530 ms |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/zgtszt.png | 550.0 KiB | 547.6 KiB |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/zjzt.png | 543.9 KiB | 541.5 KiB |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/bxgdzt.png | 517.6 KiB | 515.2 KiB |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/kczt.png | 511.7 KiB | 509.3 KiB |
body > header > ::before body > header > ::before | ustc.edu.cn/news/css/globe.jpg | 157.7 KiB | 134.6 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l3.png | 29.2 KiB | 27.1 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l1.png | 29.0 KiB | 26.9 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/jiuyezhidao.png | 25.9 KiB | 23.8 KiB |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l2.png | 25.6 KiB | 23.5 KiB |
section.notice > ul > li > div.cnm | ustc.edu.cn/news/css/sh_1.jpg | 11.1 KiB | 11.1 KiB |
RSS div.container > section.inright > section.notice > a.rss | ustc.edu.cn/news/css/wif.jpg | 8.1 KiB | 8.1 KiB |
在校师生 header > div.container > div.hot-link > a | ustc.edu.cn/news/css/condaohang.jpg | 6.8 KiB | 6.8 KiB |
ul > li > a > img ul > li > a > img | ustc.edu.cn/images/19/08/05/1bv2xhbf6r/img03.jpg | 9.7 KiB | 6.5 KiB |
ul > li > a > img ul > li > a > img | ustc.edu.cn/images/19/08/05/1bv2xhbf6r/img05.jpg | 9.7 KiB | 6.5 KiB |
ul > li > a > img ul > li > a > img | ustc.edu.cn/images/19/08/05/1bv2xhbf6r/img02.jpg | 8.7 KiB | 5.5 KiB |
ul > li > a > img ul > li > a > img | ustc.edu.cn/images/19/08/05/1bv2xhbf6r/img01.jpg | 8.2 KiB | 5.0 KiB |
ul > li > a > img ul > li > a > img | ustc.edu.cn/images/19/08/05/1bv2xhbf6r/img04.jpg | 7.4 KiB | 4.2 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| ustc.edu.cn/news/js/jquery.js | 83.9 KiB | 41.4 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| ustc.edu.cn/news/js/jquery.js | 83.9 KiB | 35.4 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| ustc.edu.cn/images/zgtszt.png | 551.1 KiB |
| ustc.edu.cn/images/zjzt.png | 545.1 KiB |
| ustc.edu.cn/images/bxgdzt.png | 518.6 KiB |
| ustc.edu.cn/images/kczt.png | 512.8 KiB |
| ustc.edu.cn/news/images/logo.svg | 196.9 KiB |
| ustc.edu.cn/news/css/globe.jpg | 158.3 KiB |
| ustc.edu.cn/__local/D/57/DA/94AAEAEF3830793410880F98321_D453E135_1E27F.jpg | 121.2 KiB |
| ustc.edu.cn/news/js/jquery.js | 84.2 KiB |
| ustc.edu.cn/news/images/l3.png | 29.5 KiB |
| ustc.edu.cn/news/images/l1.png | 29.3 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l1.png |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l2.png |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/jiuyezhidao.png |
ul.inlink > li > a > img ul.inlink > li > a > img | ustc.edu.cn/news/images/l3.png |
address > p > a > img address > p > a > img | ustc.edu.cn/news/images/blue.png |
div.container > address > p > img div.container > address > p > img | ustc.edu.cn/news/images/4054C9236D1DF77880F32A8AC59_C97E8483_1016.jpg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
皖公网安备34011102001530号 div.container > address > p > span |
These are opportunities to improve the legibility of your content.
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
学校召开学生工作队伍座谈会 ul > li.picn > div.txt > h4.on |
These are opportunities to improve keyboard navigation in your application.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.boxshadow html.boxshadow |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
div.container > address > p > img div.container > address > p > img |
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
tbody > tr.listContentBright > td > input tbody > tr.listContentBright > td > input |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
tbody > tr.listContentBright > td > input#webber_sitenewslucenesearce250968 tbody > tr.listContentBright > td > input#webber_sitenewslucenesearce250968 |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.img-list > ul > li > a div.img-list > ul > li > a |
div.img-list > ul > li > a div.img-list > ul > li > a |
div.img-list > ul > li > a div.img-list > ul > li > a |
div.img-list > ul > li > a div.img-list > ul > li > a |
div.img-list > ul > li > a div.img-list > ul > li > a |
div.img-list > ul > li > a div.img-list > ul > li > a |
div.img-list > ul > li > a div.img-list > ul > li > a |
ul > li.picn > div.pic > a ul > li.picn > div.pic > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
section.notice > div.ztzlpic > div.sss-zttj > a section.notice > div.ztzlpic > div.sss-zttj > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > ul.inlink > li > a div.container > ul.inlink > li > a |
div.container > address > p > a div.container > address > p > a |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/zgtszt.png | 208 x 70 (2.97) | 2008 x 827 (2.43) |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/kczt.png | 208 x 70 (2.97) | 2008 x 827 (2.43) |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/zjzt.png | 208 x 70 (2.97) | 2008 x 827 (2.43) |
div.ztzlpic > div.sss-zttj > a > img div.ztzlpic > div.sss-zttj > a > img | ustc.edu.cn/images/bxgdzt.png | 208 x 70 (2.97) | 2008 x 827 (2.43) |
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
ul > li > a > img ul > li > a > img |
div.container > address > p > img div.container > address > p > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
header > nav.main-menu > div.container > a.toggle header > nav.main-menu > div.container > a.toggle |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
div.container > address > p.color-switcher > a.color div.container > address > p.color-switcher > a.color |
To appear in search results, crawlers need access to your app.
Send Feedback