5.5 sec in total
625 ms
4.2 sec
708 ms
Welcome to 365id.com homepage info - get ready to check 365 ID best content right away, or after learning these important things about 365id.com
We offer the market’s safest and most affordable Global ID Verification solutions. Helping you reduce ID fraud, improve your KYC and more.
Visit 365id.comWe analyzed 365id.com page load time and found that the first response time was 625 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
365id.com performance score
name
value
score
weighting
Value13.2 s
0/100
10%
Value14.5 s
0/100
25%
Value22.1 s
0/100
10%
Value2,130 ms
6/100
30%
Value0.011
100/100
15%
Value32.3 s
0/100
10%
625 ms
28 ms
214 ms
518 ms
427 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 54% of them (67 requests) were addressed to the original 365id.com, 24% (30 requests) were made to Fonts.gstatic.com and 5% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain 365id.com.
Page size can be reduced by 1.7 MB (53%)
3.2 MB
1.5 MB
In fact, the total size of 365id.com main page is 3.2 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. 70% of websites need less resources to load. CSS take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 146.4 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 146.4 kB or 83% of the original size.
Potential reduce by 5 B
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. 365 ID images are well optimized though.
Potential reduce by 552.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 552.8 kB or 57% of the original size.
Potential reduce by 1.0 MB
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. 365id.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 89% of the original size.
Number of requests can be reduced by 70 (79%)
89
19
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 365 ID. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
625 ms
uc.js
28 ms
conditional_logic.css
214 ms
grid.min.css
518 ms
helper-parts.min.css
427 ms
main.min.css
849 ms
style.min.css
323 ms
theme.min.css
321 ms
header-footer.min.css
324 ms
frontend-lite.min.css
738 ms
post-5.css
433 ms
elementor-icons.min.css
645 ms
swiper.min.css
538 ms
frontend-lite.min.css
546 ms
all.min.css
728 ms
v4-shims.min.css
651 ms
global.css
971 ms
post-845.css
968 ms
post-1433.css
762 ms
post-2118.css
834 ms
post-933.css
845 ms
repeatericons.css
874 ms
elementor_repeater.css
943 ms
intlTelInput.min.css
952 ms
elementor-tel.css
957 ms
css
34 ms
jquery.min.js
1090 ms
jquery-migrate.min.js
1050 ms
conditional_logic.js
1061 ms
v4-shims.min.js
1072 ms
elementor_repeater.js
1080 ms
intlTelInput-jquery.js
1188 ms
elementor_tel.js
1162 ms
v.js
64 ms
widget-nav-menu.min.css
1075 ms
widget-icon-box.min.css
1091 ms
widget-carousel.min.css
1210 ms
widget-icon-list.min.css
1172 ms
gtm4wp-youtube.js
1175 ms
player.js
40 ms
cc3f1a8bb2.js
72 ms
gtm4wp-vimeo.js
1184 ms
core.min.js
1112 ms
main.min.js
1142 ms
hello-frontend.min.js
1061 ms
jquery.sticky.min.js
1115 ms
jquery.smartmenus.min.js
1012 ms
imagesloaded.min.js
1004 ms
webpack.runtime.min.js
919 ms
frontend-modules.min.js
964 ms
waypoints.min.js
1025 ms
frontend.min.js
1011 ms
hooks.min.js
919 ms
i18n.min.js
842 ms
elementor.js
833 ms
webpack-pro.runtime.min.js
869 ms
frontend.min.js
821 ms
elements-handlers.min.js
810 ms
gtm.js
189 ms
gtm.js
265 ms
gtm.js
341 ms
gtm.js
307 ms
gtm.js
307 ms
gtm.js
307 ms
13595u952cff44976744348fb5c6dcb1071df9-frame
153 ms
365id_newlogo_2021_payoff.png
437 ms
365id_newlogo_2021_white.png
453 ms
app_hero_16-9.jpg
704 ms
scanner_app_sdk_collection-copy.png
1142 ms
new_web_segment_overview_1x1.jpg
733 ms
new_web_integration_overview_1x1.jpg
853 ms
bg_scan_etc.png
542 ms
noleggiare_round_transparent-300x300.png
566 ms
avance_round_transparent-300x300.png
655 ms
europcar_round_transparent-300x300.png
679 ms
sistec-300x300.png
771 ms
profil-hotels.png
792 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDJZ9xdv.woff
23 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDNZ9xdv.woff
30 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNZ9xdv.woff
90 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNZ9xdv.woff
90 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTBjNZ9xdv.woff
90 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRZ9xdv.woff
51 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRZ9xdv.woff
89 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDRZ9xdv.woff
89 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTnTRZ9xdv.woff
108 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
109 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
109 ms
KFOmCnqEu92Fr1Mu4mxM.woff
109 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
109 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
109 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
114 ms
eicons.woff
1093 ms
usersync
415 ms
iframe_api
177 ms
KFOjCnqEu92Fr1Mu51TjASc6CsI.woff
24 ms
KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff
24 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
23 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff
24 ms
KFOjCnqEu92Fr1Mu51TzBic6CsI.woff
22 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff
60 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HCBsidrD0k.woff
60 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HABsydrD0k.woff
72 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HDfsydrD0k.woff
73 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HCBsydrD0k.woff
72 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HCzsydrD0k.woff
73 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HBftCdrD0k.woff
94 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HBmtCdrD0k.woff
93 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HABtCdrD0k.woff
95 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HAotCdrD0k.woff
95 ms
fa-brands-400.woff
712 ms
bootstrap.min.css
153 ms
css
76 ms
api.js
151 ms
jquery-3.1.1.min.js
151 ms
www-widgetapi.js
34 ms
recaptcha__en.js
40 ms
13595u952cff44976744348fb5c6dcb1071df9_13595
495 ms
fallback
25 ms
fallback__ltr.css
16 ms
css
18 ms
logo_48.png
4 ms
pixel.gif
388 ms
365id.com 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
365id.com 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
365id.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
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 365id.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 365id.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.
365id.com
Open Graph data is detected on the main page of 365 ID. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: