Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

phpweblog.net

PHP博客 - 专注于PHP技术

Page Load Speed

10.4 sec in total

First Response

4.6 sec

Resources Loaded

5.6 sec

Page Rendered

137 ms

phpweblog.net screenshot

About Website

Click here to check amazing Phpweblog content for China. Otherwise, check out these important facts you probably never knew about phpweblog.net

Visit phpweblog.net

Key Findings

We analyzed Phpweblog.net page load time and found that the first response time was 4.6 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

phpweblog.net performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

phpweblog.net

4612 ms

style.css

1384 ms

show_ads.js

49 ms

logo.gif

955 ms

ShowHidden.js

509 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 57% of them (4 requests) were addressed to the original Phpweblog.net, 29% (2 requests) were made to Pagead2.googlesyndication.com and 14% (1 request) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Phpweblog.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.7 kB (30%)

Content Size

25.4 kB

After Optimization

17.7 kB

In fact, the total size of Phpweblog.net main page is 25.4 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. Only 5% of websites need less resources to load. Javascripts take 17.1 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 5.3 kB

  • Original 8.2 kB
  • After minification 7.7 kB
  • After compression 2.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.3 kB or 65% of the original size.

JavaScript Optimization

-14%

Potential reduce by 2.4 kB

  • Original 17.1 kB
  • After minification 16.6 kB
  • After compression 14.7 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 2.4 kB or 14% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phpweblog. According to our analytics all requests are already optimized.

Accessibility Review

phpweblog.net accessibility score

45

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

phpweblog.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

phpweblog.net SEO score

58

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

Image elements do not have [alt] attributes

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 Phpweblog.net 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 Phpweblog.net 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 Phpweblog. 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: