4.1 sec in total
399 ms
3 sec
662 ms
Click here to check amazing Dualtron content for Russia. Otherwise, check out these important facts you probably never knew about dual-tron.com
Impel
Visit dual-tron.comWe analyzed Dual-tron.com page load time and found that the first response time was 399 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
dual-tron.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value11.7 s
0/100
25%
Value10.5 s
7/100
10%
Value50 ms
100/100
30%
Value0.021
100/100
15%
Value11.4 s
19/100
10%
399 ms
418 ms
387 ms
94 ms
192 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 51% of them (40 requests) were addressed to the original Dual-tron.com, 32% (25 requests) were made to Minimotors-us.oss-us-west-1.aliyuncs.com and 16% (13 requests) were made to Minimotors.oss-eu-central-1.aliyuncs.com. The less responsive or slowest element that took the longest time to load (998 ms) relates to the external source Minimotors-us.oss-us-west-1.aliyuncs.com.
Page size can be reduced by 84.3 kB (4%)
2.4 MB
2.3 MB
In fact, the total size of Dual-tron.com main page is 2.4 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 43.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. This page needs HTML code to be minified as it can gain 15.0 kB, which is 29% 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 43.4 kB or 85% of the original size.
Potential reduce by 32.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. Dualtron images are well optimized though.
Potential reduce by 8.7 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. Dual-tron.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 11% of the original size.
Number of requests can be reduced by 25 (34%)
74
49
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dualtron. 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 14 to 1 for CSS and as a result speed up the page load time.
dual-tron.com
399 ms
www.dual-tron.com
418 ms
www.dual-tron.com
387 ms
fonts.css
94 ms
bootstrap.min.css
192 ms
font-awesome.min.css
257 ms
magnific-popup.css
262 ms
slick.css
269 ms
slick-theme.css
270 ms
settings.css
287 ms
style.css
406 ms
iconfont.css
340 ms
self-floor.css
348 ms
animate.css
359 ms
swiper-bundle.min.css
361 ms
floor.js
378 ms
wow.js
425 ms
hScroll.js
434 ms
swiper.min.js
542 ms
baguetteBox.js
456 ms
baguetteBox.css
470 ms
self-adaption.js
499 ms
home.css
510 ms
jquery.js
613 ms
popper.js
556 ms
bootstrap.min.js
564 ms
jquery.magnific-popup.min.js
593 ms
slick.min.js
595 ms
custom.js
646 ms
swiper-bundle.min.js
739 ms
ee790a7c04794b98ad6ef10f7a822595.png
292 ms
826e58805d1a491395dbc990e04341c9.jpg
851 ms
logo.png
108 ms
logo_child.png
136 ms
side_mobile_title.png
130 ms
home_banner1.png
413 ms
home_banner1_mobile.png
375 ms
banner_a_title.png
201 ms
eagle_title.png
214 ms
SPEEDWAY3.png
230 ms
goto.png
280 ms
a7d0f649bdc64584ac674af78d489fc0.png
855 ms
cf6b3563bb07477aa2f168de0b747506.png
361 ms
8854d0d9c66b44a8bde5d0d02d6f82ec.png
487 ms
b42848f2464f45cba68964efa770356b.png
398 ms
4f9432ff087846aa93fdf72a6f260c31.png
395 ms
d4c2d09ab3c549bbb2f2c0004e496ff5.png
489 ms
554385fe646948c4b41eeb5c04e30994.png
495 ms
7205cf7386364846b207d01d2f9077ba.png
499 ms
d000fb6fc0f04ebb8fe81bc43bd1346c.png
616 ms
c51bf6c763a44f75926e29c6559e464e.png
599 ms
fd648b238c31428ab683383b3e4d6efc.png
596 ms
9b17ff70a44a411e8e715f828a03e593.png
595 ms
72cd787860f24b28bac1a440266e17aa.png
297 ms
0eb031e0e0e8496c8e7bbce45decb936.jpg
633 ms
9c7cb7322dc74918bf478abe2e714521.jpg
397 ms
44d2025e344b40eabc4b447bfce972dc.jpg
628 ms
48d8033261b64fa79521f57d9cff9998.jpg
614 ms
6e032e0ace7e46ac912367303930db48.jpg
595 ms
eff7a081920a445d8089d1ebe748267b.png
666 ms
a618a7f699be47d49d773ffac0ed7179.jpg
727 ms
eagle_bg2.png
713 ms
eagle_bg3.png
735 ms
eagle_bg1.png
779 ms
eagle_bg3_bg.png
709 ms
eagle_bg2_bg.png
877 ms
eagle_bg1_bg.png
828 ms
bdd1f5f3c21a4a61a080f54ba1da2647.jpg
853 ms
2c572ae1531d449f849ea393a95a8f0f.jpg
832 ms
0b1a9cc90de941c2aea9b75337935ba7.png
830 ms
c26b8d2ade8144b0b5f344db0806b314.png
866 ms
b75b190f3bb643d4ac391fc2abec2d15.png
952 ms
brand1.png
989 ms
65f1e758a528496a868c6ad0125e7329.png
952 ms
brand3.png
990 ms
d4374664a6a84897a59d04a2317df374.png
998 ms
585ab60d599b48e598addd5ccfb70168.png
988 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
35 ms
fontawesome-webfont.woff
277 ms
dual-tron.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
dual-tron.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
Page has valid source maps
dual-tron.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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 Dual-tron.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 Dual-tron.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.
dual-tron.com
Open Graph description is not detected on the main page of Dualtron. 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: