Chenjiagou.net Site Title

陈家沟国际太极院 - 陈家沟太极院

Chenjiagou.net Meta Description

陈家沟国际太极院,位于于中国太极拳起源圣地-陈家沟，是陈炳院长在祖居地基础上兴建的现代化学院，北依陈长兴故居，东临陈照丕陵园，西近杨露禅学拳处，村南一号乡村公路和陈家沟太极大街交汇于学院门前，交通方便，被称为陈家沟的“南大门”。

Chenjiagou.net Test Results

Chenjiagou.net Mobile Performance: 54/100
Quick overview:
Time to Interactive
14.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
200 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minify JavaScript
Potential savings of 18 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Reduce unused CSS
Potential savings of 64 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Properly size images
Potential savings of 2,958 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
14,290 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minimize main-thread work
4.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Use video formats for animated content
Potential savings of 69 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
Defer offscreen images
Potential savings of 714 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve images in next-gen formats
Potential savings of 2,598 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Enable text compression
Potential savings of 176 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 89 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.
Eliminate render-blocking resources
Potential savings of 1,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Efficiently encode images
Potential savings of 666 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Avoid enormous network payloads
Total size was 4,471 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Serve static assets with an efficient cache policy
46 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Chenjiagou.net Mobile SEO: 83/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
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

Chenjiagou.net Mobile Best Practices: 59/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Trust and Safety
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not use HTTPS
51 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Chenjiagou.net Mobile Accessibility: 40/100
Quick overview:
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Names and labels
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.
Image elements do not have `[alt]` attributes
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.
Links do not have a discernible name
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
`<input type="image">` elements do not have `[alt]` text
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Tables do not use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `colspan]` attribute may improve the experience for screen reader users. [Learn more about captions.
`<td>` elements in a large `<table>` do not have table headers.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
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.
Similar sites
Similar tests
www.chenjiagou.com
www.chenjiagou.net
www.chenjiagou.org
www.chenjiagou.info
www.chenjiagou.biz
www.chenjiagou.us
www.chenjiagou.mobi
www.henjiagou.net
www.chenjiagou.net
www.xhenjiagou.net
www.cxhenjiagou.net
www.xchenjiagou.net
www.dhenjiagou.net
www.cdhenjiagou.net
www.dchenjiagou.net
www.fhenjiagou.net
www.cfhenjiagou.net
www.fchenjiagou.net
www.vhenjiagou.net
www.cvhenjiagou.net
www.vchenjiagou.net
www.cenjiagou.net
www.cbenjiagou.net
www.chbenjiagou.net
www.cbhenjiagou.net
www.cgenjiagou.net
www.chgenjiagou.net
www.cghenjiagou.net
www.cyenjiagou.net
www.chyenjiagou.net
www.cyhenjiagou.net
www.cuenjiagou.net
www.chuenjiagou.net
www.cuhenjiagou.net
www.cjenjiagou.net
www.chjenjiagou.net
www.cjhenjiagou.net
www.cnenjiagou.net
www.chnenjiagou.net
www.cnhenjiagou.net
www.chnjiagou.net
www.chwnjiagou.net
www.chewnjiagou.net
www.chwenjiagou.net
www.chsnjiagou.net
www.chesnjiagou.net
www.chsenjiagou.net
www.chdnjiagou.net
www.chednjiagou.net
www.chdenjiagou.net
www.chrnjiagou.net
www.chernjiagou.net
www.chrenjiagou.net
www.chejiagou.net
www.chebjiagou.net
www.chenbjiagou.net
www.chebnjiagou.net
www.chehjiagou.net
www.chenhjiagou.net
www.chehnjiagou.net
www.chejjiagou.net
www.chenjjiagou.net
www.chejnjiagou.net
www.chemjiagou.net
www.chenmjiagou.net
www.chemnjiagou.net
www.cheniagou.net
www.chenniagou.net
www.chenjniagou.net
www.chennjiagou.net
www.chenhiagou.net
www.chenjhiagou.net
www.chenuiagou.net
www.chenjuiagou.net
www.chenujiagou.net
www.cheniiagou.net
www.chenjiiagou.net
www.chenijiagou.net
www.chenkiagou.net
www.chenjkiagou.net
www.chenkjiagou.net
www.chenmiagou.net
www.chenjmiagou.net
www.chenjagou.net
www.chenjuagou.net
www.chenjiuagou.net
www.chenjjagou.net
www.chenjijagou.net
www.chenjkagou.net
www.chenjikagou.net
www.chenjoagou.net
www.chenjioagou.net
www.chenjoiagou.net
www.chenjigou.net
www.chenjiqgou.net
www.chenjiaqgou.net
www.chenjiqagou.net
www.chenjiwgou.net
www.chenjiawgou.net
www.chenjiwagou.net
www.chenjisgou.net
www.chenjiasgou.net
www.chenjisagou.net
www.chenjizgou.net
www.chenjiazgou.net
www.chenjizagou.net
www.chenjiaou.net
www.chenjiafou.net
www.chenjiagfou.net
www.chenjiafgou.net
www.chenjiavou.net
www.chenjiagvou.net
www.chenjiavgou.net
www.chenjiatou.net
www.chenjiagtou.net
www.chenjiatgou.net
www.chenjiabou.net
www.chenjiagbou.net
www.chenjiabgou.net
www.chenjiayou.net
www.chenjiagyou.net
www.chenjiaygou.net
www.chenjiahou.net
www.chenjiaghou.net
www.chenjiahgou.net
www.chenjiagu.net
www.chenjiagiu.net
www.chenjiagoiu.net
www.chenjiagiou.net
www.chenjiagku.net
www.chenjiagoku.net
www.chenjiagkou.net
www.chenjiaglu.net
www.chenjiagolu.net
www.chenjiaglou.net
www.chenjiagpu.net
www.chenjiagopu.net
www.chenjiagpou.net
www.chenjiago.net
www.chenjiagoy.net
www.chenjiagouy.net
www.chenjiagoyu.net
www.chenjiagoh.net
www.chenjiagouh.net
www.chenjiagohu.net
www.chenjiagoj.net
www.chenjiagouj.net
www.chenjiagoju.net
www.chenjiagoi.net
www.chenjiagoui.net
Last Tested: