6.4 sec in total
89 ms
2.7 sec
3.6 sec
Welcome to public.com homepage info - get ready to check Public best content for United States right away, or after learning these important things about public.com
Invest in Stocks, Bonds, Options, Crypto, ETFs, Treasuries, and more with AI-powered fundamental data and custom analysis.
Visit public.comWe analyzed Public.com page load time and found that the first response time was 89 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
public.com performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value8.1 s
2/100
25%
Value4.7 s
69/100
10%
Value690 ms
43/100
30%
Value0
100/100
15%
Value7.0 s
52/100
10%
89 ms
22 ms
6 ms
13 ms
62 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 40% of them (23 requests) were addressed to the original Public.com, 33% (19 requests) were made to Hellopublic.wpengine.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Hellopublic.wpengine.com.
Page size can be reduced by 124.2 kB (3%)
3.8 MB
3.7 MB
In fact, the total size of Public.com main page is 3.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 92.8 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 92.8 kB or 81% of the original size.
Potential reduce by 30.0 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 images are well optimized though.
Potential reduce by 71 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 1.4 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.com has all CSS files already compressed.
Number of requests can be reduced by 20 (38%)
52
32
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
public.com
89 ms
public.com
22 ms
main-b015f46f.css
6 ms
home_3494fe9a.css
13 ms
main-b015f46f.js
62 ms
home-async_3494fe9a.js
161 ms
common-async_3494fe9a.js
64 ms
js
1082 ms
frontend.js
62 ms
home_3494fe9a.js
62 ms
gtm.js
1246 ms
hero-sm.png
1869 ms
as-seen-brands.svg
1624 ms
as-seen-store.svg
1625 ms
invest-in-stocks.png
1635 ms
invest-in-crypto-v2.png
1749 ms
invest-in-etf.png
1633 ms
invest-in-art.png
1994 ms
invest-in-collectibles-768x900.png
2033 ms
gb-arrow.svg
1747 ms
context-01.png
2031 ms
calum.png
1857 ms
percy.png
1857 ms
context-02.png
2177 ms
gb-chart.svg
1859 ms
context-03.png
2033 ms
context-04.png
2039 ms
investor-first-sm-1024x1024.jpeg
2081 ms
app-store-apple.svg
641 ms
app-store-google.svg
643 ms
spritemap.svg
1030 ms
public-logo.svg
728 ms
uwt.js
1434 ms
tv2track.js
1510 ms
data.json
443 ms
Graphik-Regular_7087dd4c.woff
679 ms
Graphik-Medium_0e95b6d1.woff
680 ms
Graphik-Bold_e7070729.woff
680 ms
insights-sm.jpeg
1340 ms
insights-lg.jpeg
1339 ms
Hero_Anim_V06_frame-1024x576.jpg
469 ms
invest-ineverything-lg-1024x1024.jpeg
300 ms
context-poster-lg-1024x1024.jpeg
470 ms
home-async_3494fe9a.css
330 ms
js
219 ms
analytics.js
327 ms
insight.min.js
381 ms
bat.js
369 ms
adsct
431 ms
adsct
419 ms
common-async_3494fe9a.css
380 ms
tv2track.php
211 ms
collect
189 ms
bg-modal-md_d74250ca.webp
165 ms
collect
128 ms
ga-audiences
66 ms
25 ms
public.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
public.com 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
public.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Public.com 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.com 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.com
Open Graph data is detected on the main page of Public. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: