Php.net PHP: Hypertext Preprocessor
php.net Mobile Performance
30/100
These metrics represent real-world Chrome users experience viewing php.net on mobile devices. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Largest Contentful Paint
First Contentful Paint
First Input Delay
Cumulative Layout Shift
Metrics
Total Blocking Time3/100 1,770 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint5/100 7.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive25/100 10.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index47/100 6.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Contentful Paint84/100 2.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift100/100 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (14)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 1,110 ms
1,110 ms
Eliminate render-blocking resources
Potential savings of 620 ms
621 ms
Reduce initial server response time
Root document took 1,000 ms
402 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,650 ms
Serve static assets with an efficient cache policy
19 resources found
Minimize main-thread work
4.2 s
Avoid an excessive DOM size
1,184 elements
Reduce JavaScript execution time
1.7 s
Avoid large layout shifts
1 element found
Largest Contentful Paint element
1 element found
Avoid long main-thread tasks
10 long tasks found
Keep request counts low and transfer sizes small
25 requests • 895 KiB
Avoid chaining critical requests
16 chains found
Passed Audits (15)
Remove unused CSS
Remove unused JavaScript
Enable text compression
Uses passive listeners to improve scrolling performance
Avoids `document.write()`
Minify JavaScript
Potential savings of 7 KiB
Preconnect to required origins
Preload key requests
Defer offscreen images
Serve images in next-gen formats
Avoids enormous network payloads
Total size was 895 KiB
Efficiently encode images
Use video formats for animated content
Minify CSS
Potential savings of 2 KiB
Properly size images
php.net Mobile SEO
84/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (3)
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.
Tap targets are not sized appropriately
83% appropriately sized tap targets
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
Document does not have a meta description
Passed Audits (11)
Page isn’t blocked from indexing
Page has successful HTTP status code
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a valid `hreflang`
Document uses legible font sizes
100% legible text
Links have descriptive text
Document avoids plugins
Links are crawlable
Document has a valid `rel=canonical`
robots.txt is valid
Document has a `<title>` element
php.net Mobile Best Practices
85/100
These checks highlight opportunities to improve the overall code health of php.net mobile page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (2)
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Does not use HTTPS
1 insecure request found
Passed Audits (12)
Page has the HTML doctype
Allows users to paste into password fields
Avoids requesting the notification permission on page load
Avoids deprecated APIs
Detected JavaScript libraries
Avoids Application Cache
Displays images with correct aspect ratio
Links to cross-origin destinations are safe
Avoids requesting the geolocation permission on page load
No browser errors logged to the console
Serves images with appropriate resolution
Properly defines charset
php.net Mobile Progressive Web App
21/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (10)
Installable
Web app manifest does not meet the installability requirements
Does not use HTTPS
1 insecure request found
Does not register a service worker that controls page and `start_url`
PWA Optimized
Does not provide a valid `apple-touch-icon`
Does not set a theme color for the address bar.
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Fast and reliable
Current page does not respond with a 200 when offline
`start_url` does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive at 10.4 s
Passed Audits (4)
Contains some content when JavaScript is not available
Redirects HTTP traffic to HTTPS
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Content is sized correctly for the viewport
php.net Mobile Accessibility
68/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (3)
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.
Form elements do not have associated labels
Image elements do not have `[alt]` attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
Passed Audits (12)
Background and foreground colors have a sufficient contrast ratio
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[accesskey]` values are unique
`<html>` element has a `[lang]` attribute
The page contains a heading, skip link, or landmark region
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Links have a discernible name
Heading elements appear in a sequentially-descending order
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`[aria-hidden="true"]` is not present on the document `<body>`
`<html>` element has a valid value for its `[lang]` attribute
Document has a `<title>` element
Mobile Usability
98/100
These checks validate how easily a visitor can use php.net on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Should Fix (1)
Size tap targets appropriately
Passed Audits (4)
Avoid plugins
Configure the viewport
Size content to viewport
Use legible font sizes
Mobile Speed
80/100
These checks analyze the performance of php.net on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Minify JavaScript
Optimize images
Minify CSS
Enable compression
Passed Audits (4)
Avoid landing page redirects
Reduce server response time
Minify HTML
Prioritize visible content
www.php.com
www.php.net
www.php.org
www.php.info
www.php.biz
www.php.us
www.php.mobi
www.hp.net
www.php.net
www.ohp.net
www.pohp.net
www.ophp.net
www.lhp.net
www.plhp.net
www.lphp.net
www.pp.net
www.pbp.net
www.phbp.net
www.pbhp.net
www.pgp.net
www.phgp.net
www.pghp.net
www.pyp.net
www.phyp.net
www.pyhp.net
www.pup.net
www.phup.net
www.puhp.net
www.pjp.net
www.phjp.net
www.pjhp.net
www.pnp.net
www.phnp.net
www.pnhp.net
www.ph.net
www.pho.net
www.phpo.net
www.phop.net
www.phl.net
www.phpl.net
www.phlp.net
www.php.net
www.php.org
www.php.info
www.php.biz
www.php.us
www.php.mobi
www.hp.net
www.php.net
www.ohp.net
www.pohp.net
www.ophp.net
www.lhp.net
www.plhp.net
www.lphp.net
www.pp.net
www.pbp.net
www.phbp.net
www.pbhp.net
www.pgp.net
www.phgp.net
www.pghp.net
www.pyp.net
www.phyp.net
www.pyhp.net
www.pup.net
www.phup.net
www.puhp.net
www.pjp.net
www.phjp.net
www.pjhp.net
www.pnp.net
www.phnp.net
www.pnhp.net
www.ph.net
www.pho.net
www.phpo.net
www.phop.net
www.phl.net
www.phpl.net
www.phlp.net