171 ms in total
29 ms
141 ms
1 ms
Click here to check amazing Wp Api content for India. Otherwise, check out these important facts you probably never knew about wp-api.org
Official Documentation for WP REST API
Visit wp-api.orgWe analyzed Wp-api.org page load time and found that the first response time was 29 ms and then it took 142 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.
wp-api.org performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value4.0 s
49/100
25%
Value3.9 s
82/100
10%
Value120 ms
97/100
30%
Value0.069
96/100
15%
Value5.2 s
74/100
10%
29 ms
20 ms
31 ms
24 ms
16 ms
Our browser made a total of 6 requests to load all elements on the main page. We found that 33% of them (2 requests) were addressed to the original Wp-api.org, 17% (1 request) were made to Cdn.rawgit.com and 17% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (48 ms) relates to the external source Api.github.com.
Page size can be reduced by 15.2 kB (80%)
19.0 kB
3.8 kB
In fact, the total size of Wp-api.org main page is 19.0 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. CSS take 17.5 kB which makes up the majority of the site volume.
Potential reduce by 867 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 867 B or 57% of the original size.
Potential reduce by 14.3 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. Wp-api.org needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 82% of the original size.
We found no issues to fix!
5
5
The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wp Api. According to our analytics all requests are already optimized.
wp-api.org
29 ms
styles.css
20 ms
script.js
31 ms
css
24 ms
github-btn.html
16 ms
WP-API
48 ms
wp-api.org accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
wp-api.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wp-api.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wp-api.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wp-api.org 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.
wp-api.org
Open Graph description is not detected on the main page of Wp Api. 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: