3.2 sec in total
108 ms
2.8 sec
289 ms
Click here to check amazing Public Record content for United States. Otherwise, check out these important facts you probably never knew about public-record.com
Record Information Services provides the most current and accurate Illinois public record data and marketing lists, all in a convenient online search database.
Visit public-record.comWe analyzed Public-record.com page load time and found that the first response time was 108 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
public-record.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value13.8 s
0/100
25%
Value4.5 s
72/100
10%
Value2,400 ms
5/100
30%
Value0.014
100/100
15%
Value18.5 s
3/100
10%
108 ms
316 ms
77 ms
76 ms
17 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 32% of them (21 requests) were addressed to the original Public-record.com, 14% (9 requests) were made to Tpc.googlesyndication.com and 9% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Public-record.com.
Page size can be reduced by 422.7 kB (47%)
908.8 kB
486.1 kB
In fact, the total size of Public-record.com main page is 908.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. 55% of websites need less resources to load. Javascripts take 510.0 kB which makes up the majority of the site volume.
Potential reduce by 57.3 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 57.3 kB or 71% of the original size.
Potential reduce by 79.3 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, Public Record needs image optimization as it can save up to 79.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 280.6 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 280.6 kB or 55% of the original size.
Potential reduce by 5.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. Public-record.com needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 80% of the original size.
Number of requests can be reduced by 32 (55%)
58
26
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public Record. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
public-record.com
108 ms
www.public-record.com
316 ms
scripts.js
77 ms
style.css
76 ms
ajtg.js
17 ms
brand
28 ms
addthis_widget.js
15 ms
quant.js
6 ms
bg.jpg
199 ms
top_logo.gif
1106 ms
top_bar.jpg
121 ms
x.gif
129 ms
ads.gif
128 ms
small_checkillinois.gif
127 ms
small_watchillinois.gif
127 ms
small_realestateillinois.gif
184 ms
latestupdates_header.jpg
184 ms
div.jpg
182 ms
ataglance.jpg
181 ms
front.PNG
2306 ms
latestnews_header.jpg
288 ms
recordcount.jpg
288 ms
chicago-crains.jpg
319 ms
chicago-tribune.jpg
367 ms
donotcall.jpg
319 ms
brand
188 ms
widget_v2.132.js
20 ms
vj
9 ms
adsbygoogle.js
4 ms
vj
15 ms
ca-pub-3770681708992242.js
58 ms
zrt_lookup.html
147 ms
show_ads_impl.js
106 ms
google_custom_search_watermark.gif
125 ms
ads
547 ms
analytics.js
28 ms
pixel;r=900708138;a=p-7aRfUIOnJjhaQ;fpan=1;fpa=P0-1276200868-1456765761136;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456765761136;tzo=-180;ref=;url=http%3A%2F%2Fwww.public-record.com%2F;ogl=
25 ms
300lo.json
41 ms
counter.8eb9e83b9fa0d4af1e4f.js
52 ms
osd.js
29 ms
sh.7c7179124ea24ac6ba46caac.html
45 ms
ads
505 ms
collect
49 ms
shares.json
10 ms
collect
51 ms
n99h
20 ms
p0dg
19 ms
ga-audiences
16 ms
css
175 ms
m_js_controller.js
50 ms
abg.js
50 ms
suggestion_autolayout_V2_8.css
45 ms
suggestion_autolayout_V2_8.js
46 ms
layout_engine.js
48 ms
aL63HcygAAVYuCCsAAA==
2 ms
s
14 ms
googlelogo_color_112x36dp.png
85 ms
13933795521410226155
8 ms
6505810720168264227
9 ms
x_button_blue2.png
5 ms
favicon
66 ms
nessie_icon_tiamat_white.png
28 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
58 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
4 ms
activeview
12 ms
public-record.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
public-record.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
public-record.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Public-record.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-record.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-record.com
Open Graph description is not detected on the main page of Public Record. 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: