6.6 sec in total
738 ms
5.5 sec
388 ms
Welcome to dots.africa homepage info - get ready to check Dots best content right away, or after learning these important things about dots.africa
Your all-in-one background screening platform for seamless background verifications, paying only per check with no subscription fee required.
Visit dots.africaWe analyzed Dots.africa page load time and found that the first response time was 738 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dots.africa performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value7.8 s
3/100
25%
Value15.3 s
1/100
10%
Value1,010 ms
27/100
30%
Value0.015
100/100
15%
Value15.8 s
6/100
10%
738 ms
1504 ms
28 ms
219 ms
438 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 82% of them (67 requests) were addressed to the original Dots.africa, 16% (13 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Dots.africa.
Page size can be reduced by 166.1 kB (25%)
670.3 kB
504.2 kB
In fact, the total size of Dots.africa main page is 670.3 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. 60% of websites need less resources to load. Images take 297.1 kB which makes up the majority of the site volume.
Potential reduce by 118.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. 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 118.0 kB or 82% 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. Dots images are well optimized though.
Potential reduce by 17.1 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 17.1 kB or 11% of the original size.
Potential reduce by 9.6 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. Dots.africa needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 14% of the original size.
Number of requests can be reduced by 51 (76%)
67
16
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dots. 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 from 33 to 1 for CSS and as a result speed up the page load time.
dots.africa
738 ms
www.dots.africa
1504 ms
css
28 ms
cookieNSCconsent.min.css
219 ms
style.min.css
438 ms
theme.min.css
647 ms
header-footer.min.css
656 ms
e-animation-shrink.min.css
900 ms
custom-frontend.min.css
913 ms
widget-image.min.css
917 ms
custom-pro-widget-nav-menu.min.css
910 ms
widget-heading.min.css
865 ms
widget-text-editor.min.css
873 ms
widget-social-icons.min.css
1083 ms
custom-apple-webkit.min.css
1092 ms
swiper.min.css
1115 ms
e-swiper.min.css
1137 ms
post-83.css
1149 ms
popup.min.css
1135 ms
all.min.css
1516 ms
v4-shims.min.css
1309 ms
widget-gallery.min.css
1330 ms
e-gallery.min.css
1353 ms
transitions.min.css
1355 ms
widget-divider.min.css
1364 ms
widget-loop-builder.min.css
1527 ms
custom-pro-widget-testimonial-carousel.min.css
1549 ms
widget-carousel-module-base.min.css
1570 ms
post-15.css
1572 ms
post-40.css
1582 ms
post-53.css
1735 ms
style.css
1745 ms
jquery.min.js
1982 ms
jquery-migrate.min.js
1787 ms
v4-shims.min.js
1790 ms
jquery.bind-first-0.2.3.min.js
1798 ms
js.cookie-2.1.3.min.js
1952 ms
public.js
1964 ms
widget-post-info.min.css
2058 ms
custom-widget-icon-list.min.css
1847 ms
motion-fx.min.css
1628 ms
cookieNSCconsent.min.js
1531 ms
jquery.smartmenus.min.js
1533 ms
e-gallery.min.js
1338 ms
imagesloaded.min.js
1408 ms
webpack-pro.runtime.min.js
1383 ms
webpack.runtime.min.js
1369 ms
frontend-modules.min.js
1481 ms
hooks.min.js
1491 ms
i18n.min.js
1339 ms
frontend.min.js
1409 ms
core.min.js
1386 ms
frontend.min.js
1578 ms
elements-handlers.min.js
1478 ms
gtm.js
133 ms
dots_logo.png
613 ms
Screenshot-2024-05-07-at-14.28.42.png
1056 ms
ncr.jpg
708 ms
SACRRAMemberLogo_Portrait-p-500.png
920 ms
pbsa_fullname-color_transparent-p-500.png
822 ms
cba-logo-p-500.png
833 ms
Comodo_logo.webp
924 ms
Untitled-1.png
924 ms
american-express.png
1043 ms
visa.png
1053 ms
mastercard.png
1139 ms
mastercardSC.png
1142 ms
sCode.png
1143 ms
verifiedVisa.png
1265 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf
18 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf
26 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf
39 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uw.ttf
46 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf
49 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uw.ttf
48 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
47 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
66 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
67 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
66 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
67 ms
dots.africa 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
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
Heading elements are not in a sequentially-descending order
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
dots.africa 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
Browser errors were logged to the console
Page has valid source maps
dots.africa 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
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 Dots.africa 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 Dots.africa 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.
dots.africa
Open Graph data is detected on the main page of Dots. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: