Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

phpdoc.org

Home | phpDocumentor

Page Load Speed

573 ms in total

First Response

245 ms

Resources Loaded

254 ms

Page Rendered

74 ms

About Website

Visit phpdoc.org now to see the best up-to-date Phpdoc content for United States and also check out these interesting facts you probably never knew about phpdoc.org

Documentation Generator for PHP

Visit phpdoc.org

Key Findings

We analyzed Phpdoc.org page load time and found that the first response time was 245 ms and then it took 328 ms 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.

Performance Metrics

phpdoc.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

phpdoc.org

245 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Phpdoc.org and no external sources were called. The less responsive or slowest element that took the longest time to load (245 ms) belongs to the original domain Phpdoc.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 675.2 kB (47%)

Content Size

1.4 MB

After Optimization

757.8 kB

In fact, the total size of Phpdoc.org main page is 1.4 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 668.7 kB which makes up the majority of the site volume.

HTML Optimization

-35%

Potential reduce by 54 B

  • Original 156 B
  • After minification 154 B
  • After compression 102 B

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 54 B or 35% of the original size.

Image Optimization

-17%

Potential reduce by 110.5 kB

  • Original 668.7 kB
  • After minification 558.2 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. Obviously, Phpdoc needs image optimization as it can save up to 110.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 263.8 kB

  • Original 405.8 kB
  • After minification 388.8 kB
  • After compression 142.0 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 263.8 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 300.8 kB

  • Original 358.3 kB
  • After minification 329.6 kB
  • After compression 57.5 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. Phpdoc.org needs all CSS files to be minified and compressed as it can save up to 300.8 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

phpdoc.org accessibility score

65

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

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

phpdoc.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

phpdoc.org SEO score

92

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

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

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phpdoc.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Phpdoc.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Phpdoc. 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: