Tools & Wizards About Us

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

php1.cn

第一PHP社区 - PHP1.CN 国内最大的PHP中文社区

Page Load Speed

24.8 sec in total

First Response

667 ms

Resources Loaded

23.1 sec

Page Rendered

953 ms

About Website

Welcome to php1.cn homepage info - get ready to check PHP1 best content for China right away, or after learning these important things about php1.cn

PHP1.CN中文网是国内最大PHP专业技术网站，也提供了PHP中文博客、问答、论坛、教程等频道。向PHP开发人员提供：最新PHP资讯、原创内容、开发资料,技术手册,开源代码和PHP视频教程等相关内容。

Visit php1.cn

Key Findings

We analyzed Php1.cn page load time and found that the first response time was 667 ms and then it took 24.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 48 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

php1.cn performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value3,280 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

php1.cn

667 ms

www.php1.cn

1280 ms

detail_mobile_header.css

414 ms

common.css

632 ms

index.css

633 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 16% of them (15 requests) were addressed to the original Php1.cn, 13% (12 requests) were made to Pic.php1.cn and 12% (11 requests) were made to Img8.php1.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img8.php1.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.0 kB (39%)

Content Size

671.9 kB

After Optimization

411.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Php1.cn main page is 671.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 259.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 220.0 kB

  • Original 259.4 kB
  • After minification 187.0 kB
  • After compression 39.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 72.4 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 220.0 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 8.6 kB

  • Original 144.7 kB
  • After minification 136.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. PHP1 images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 25.2 kB

  • Original 247.8 kB
  • After minification 247.8 kB
  • After compression 222.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-32%

Potential reduce by 6.3 kB

  • Original 20.0 kB
  • After minification 20.0 kB
  • After compression 13.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Php1.cn needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (66%)

Requests Now

41

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PHP1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

php1.cn accessibility score

59

Accessibility Issues

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.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

php1.cn best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

php1.cn SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Php1.cn can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Php1.cn main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of PHP1. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: