2 sec in total
225 ms
1.7 sec
127 ms
Visit public.resource.org now to see the best up-to-date Public Resource content for India and also check out these interesting facts you probably never knew about public.resource.org
Public.Resource.Org, home of the Seal of Approval.
Visit public.resource.orgWe analyzed Public.resource.org page load time and found that the first response time was 225 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
public.resource.org performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value2.2 s
95/100
25%
Value3.6 s
87/100
10%
Value370 ms
71/100
30%
Value0.013
100/100
15%
Value9.3 s
31/100
10%
225 ms
561 ms
77 ms
151 ms
221 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 78% of them (36 requests) were addressed to the original Public.resource.org, 7% (3 requests) were made to S.ytimg.com and 4% (2 requests) were made to Paypal.com. The less responsive or slowest element that took the longest time to load (650 ms) belongs to the original domain Public.resource.org.
Page size can be reduced by 396.4 kB (45%)
880.8 kB
484.4 kB
In fact, the total size of Public.resource.org main page is 880.8 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. 40% of websites need less resources to load. Images take 384.1 kB which makes up the majority of the site volume.
Potential reduce by 9.0 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 2.6 kB, which is 22% 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 9.0 kB or 77% of the original size.
Potential reduce by 21.4 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. Public Resource images are well optimized though.
Potential reduce by 138.8 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 138.8 kB or 65% of the original size.
Potential reduce by 227.2 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. Public.resource.org needs all CSS files to be minified and compressed as it can save up to 227.2 kB or 83% of the original size.
Number of requests can be reduced by 5 (12%)
42
37
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public Resource. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
public.resource.org
225 ms
public.resource.org
561 ms
setup.css
77 ms
text.css
151 ms
toggle.js
221 ms
switcher.js
227 ms
2tOJdGaMvVw
116 ms
btn_donateCC_LG.gif
67 ms
foil.seal.oregon.png
76 ms
foil.seal.justice.png
224 ms
foil.seal.gao.png
389 ms
foil.seal.itu.png
220 ms
foil.seal.sec.png
149 ms
foil.seal.si.png
434 ms
foil.seal.white2.png
436 ms
frontpage.seal.tilt.png
221 ms
frontpage.seal.upright.png
354 ms
foil.seal.uspto.png
355 ms
foil.seal.uscourts.png
354 ms
foil.seal.copyright.png
379 ms
foil.seal.house.png
387 ms
foil.seal.bsc.ca.gov.png
386 ms
foil.seal.gpo.png
460 ms
foil.seal.doc.alpha.png
460 ms
foil.seal.presidential.png
462 ms
foil.seal.fjc.png
461 ms
foil.seal.obverse.png
646 ms
bg_head_bottom_nav.jpg
504 ms
bg_main_withnav.jpg
533 ms
bg_corner_topleft.gif
533 ms
bg_corner_topright.gif
533 ms
currents.png
534 ms
bottom.gray.png
577 ms
pamphlet_icon.jpg
608 ms
8778041_cover.jpg
607 ms
bears.png
609 ms
bg_foot.jpg
608 ms
support.PD.red.png
650 ms
pixel.gif
57 ms
www-embed-player-vflRGs1ko.css
66 ms
www-embed-player.js
90 ms
base.js
155 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
44 ms
ad_status.js
42 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
89 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
100 ms
public.resource.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
public.resource.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
public.resource.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Public.resource.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Public.resource.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.
public.resource.org
Open Graph description is not detected on the main page of Public Resource. 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: