5.6 sec in total
531 ms
4.4 sec
747 ms
Welcome to getdor.com homepage info - get ready to check Get Dor best content for United States right away, or after learning these important things about getdor.com
Drive your retail operations with foot traffic analytics from Dor, a complete people counting solution for retail and facility management.
Visit getdor.comWe analyzed Getdor.com page load time and found that the first response time was 531 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
getdor.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.1 s
12/100
25%
Value10.9 s
6/100
10%
Value11,310 ms
0/100
30%
Value0.004
100/100
15%
Value30.1 s
0/100
10%
531 ms
187 ms
38 ms
106 ms
125 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 24% of them (28 requests) were addressed to the original Getdor.com, 9% (11 requests) were made to Static.formstack.com and 8% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Gstatic.com.
Page size can be reduced by 452.7 kB (28%)
1.6 MB
1.1 MB
In fact, the total size of Getdor.com main page is 1.6 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. 85% 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 978.3 kB which makes up the majority of the site volume.
Potential reduce by 300.2 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 56.8 kB, which is 16% 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 300.2 kB or 84% of the original size.
Potential reduce by 88.2 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. Get Dor images are well optimized though.
Potential reduce by 8.9 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 8.9 kB or 13% of the original size.
Potential reduce by 55.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. Getdor.com needs all CSS files to be minified and compressed as it can save up to 55.4 kB or 29% of the original size.
Number of requests can be reduced by 61 (62%)
98
37
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Get Dor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.getdor.com
531 ms
fonts.css
187 ms
main.min.5b7e3e79.css
38 ms
getdor_com_copy
106 ms
resource_library
125 ms
vendor.27df83e5.js
84 ms
main.min.0bf7fbb1.js
59 ms
363516
93 ms
css2
59 ms
A9138357977EFCEF8.css
115 ms
gtm.js
269 ms
tag.js
526 ms
right-background.jpg
216 ms
hero-icon-play.png
235 ms
hero-image.png
349 ms
icon1.png
236 ms
icon2.png
351 ms
icon3.png
234 ms
dor_logo.a015466e.svg
157 ms
hero-sensor.463d000f.svg
160 ms
hero-icons.46e95f2a.png
292 ms
client-apricot-lane.889ff12d.png
212 ms
client-duluth-trading.b689d4ed.png
234 ms
client-onward-reserve.22a5e81c.webp
213 ms
client-woolrich.7fab7ff6.webp
233 ms
client-clothes-mentor.8bf390c1.png
346 ms
client-buck-mason.8f0f19fe.png
337 ms
quote.9429e2f9.svg
349 ms
author-top-border.1c21571d.svg
339 ms
hardware-1.0280eef9.jpg
511 ms
hardware-2.9d981596.jpg
510 ms
check.d81df472.svg
510 ms
software-1.54829c41.jpg
527 ms
software-2.8bce8fec.jpg
509 ms
api-json-optimized.6d8aa0be.svg
980 ms
support-1.9b8045dd.jpg
989 ms
support-2.9d1e86ff.jpg
989 ms
empower-pattern.e22f8fb4.svg
796 ms
blog.7eeefeed.svg
802 ms
close.42ae92f7.png
802 ms
reset_3d1cc6d59f.css
266 ms
jquery-ui_eb08fdf84b.css
316 ms
default-v4_febab48678.css
273 ms
uil-static.css
312 ms
dialogs_00a7ec5f05.css
265 ms
jquery.min_1d14cd3798.js
298 ms
jquery-ui.min_42a497cb9f.js
413 ms
scripts_5fd2a2242c.js
412 ms
analytics_7d49daa365.js
428 ms
libphonenumber-min_6f64debfdd.js
444 ms
modernizr_60a2d5aeb5.js
461 ms
api.js
412 ms
Sw+O99vVHLdNg+tTouPfr89bTs2p43cfQU6NAM5
4 ms
Oyw6W0ZthmzV7AqGD2UVCtiQj9DZmaOf9LD47329Uct02D61Oi49+vz1tOzanjdx9BTo0Azk=
5 ms
PW07NqeN3H0FOjQDOQ==
5 ms
Oyw6W0ZthmzV7AqGD2UVCtiQj9DZmaOf9LD47329Uct02D61Oi49+vz1tOzanjdx9BTo0Azk=
4 ms
Oyw6W0ZthmzV7AqGD2UVCtiQj9DZmaOf9LD47329Uct02D61Oi49+vz1tOzanjdx9BTo0Azk=
4 ms
Sw+O99vVHLdNg+tTouPfr89bTs2p43cfQU6NAM5
4 ms
pxiByp8kv8JHgFVrLEj6V1s.ttf
455 ms
pxiEyp8kv8JHgFVrFJA.ttf
1306 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
1477 ms
optimize.js
1106 ms
analytics.js
1185 ms
conversion_async.js
995 ms
bat.js
987 ms
hotjar-1578990.js
1260 ms
1694028.js
1060 ms
fbevents.js
981 ms
t.js
1255 ms
insight.min.js
1081 ms
37314f82-3760-429c-b0f4-db03ebb9800f.js
979 ms
89f78fa8356c46ce8f70d1dad1740caa.js.ubembed.com
1253 ms
uwt.js
1081 ms
munchkin.js
1079 ms
heap-1760445225.js
1250 ms
js
648 ms
policy
1415 ms
webfont.js
1337 ms
recaptcha__en.js
1488 ms
2000807300153696
405 ms
730 ms
5664198.js
205 ms
munchkin.js
314 ms
collect
425 ms
pageInfo
506 ms
5664198
797 ms
modules.cbd9768ba80ba0be5b17.js
708 ms
bundle.js
535 ms
h
613 ms
adsct
666 ms
adsct
667 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
627 ms
visitWebPage
523 ms
css
239 ms
collect
470 ms
260 ms
anchor
300 ms
anchor
403 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
62 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
95 ms
clarity.js
70 ms
ga-audiences
26 ms
visit-data
451 ms
styles__ltr.css
40 ms
recaptcha__en.js
43 ms
webworker.js
148 ms
logo_48.png
130 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
18 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
18 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
17 ms
recaptcha__en.js
38 ms
23 ms
dc7a31fe8d3f4db381ee73b1c0e538874fadd1b40dfb4509b56ea6d40f4a6e88
219 ms
shim.latest.js
60 ms
frame.0a1e66d9.js
41 ms
vendor.be9e5129.js
42 ms
c.gif
66 ms
getdor.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 IDs are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
getdor.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
getdor.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Getdor.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 Getdor.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.
getdor.com
Open Graph data is detected on the main page of Get Dor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: