6.8 sec in total
1.3 sec
4.8 sec
718 ms
Welcome to worldmicro.com homepage info - get ready to check World Micro best content right away, or after learning these important things about worldmicro.com
World Micro is a global franchised distributor providing supply chain solutions to solve even the most complex requirements. Visit us online today.
Visit worldmicro.comWe analyzed Worldmicro.com page load time and found that the first response time was 1.3 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
worldmicro.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value4.0 s
48/100
25%
Value7.0 s
33/100
10%
Value1,080 ms
24/100
30%
Value0.085
93/100
15%
Value16.3 s
5/100
10%
1300 ms
166 ms
157 ms
131 ms
134 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 54% of them (68 requests) were addressed to the original Worldmicro.com, 20% (25 requests) were made to Maps.google.com and 10% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Worldmicro.com.
Page size can be reduced by 3.2 MB (39%)
8.1 MB
4.9 MB
In fact, the total size of Worldmicro.com main page is 8.1 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 6.8 MB which makes up the majority of the site volume.
Potential reduce by 109.1 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 16.1 kB, which is 13% 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 109.1 kB or 86% of the original size.
Potential reduce by 2.1 MB
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, World Micro needs image optimization as it can save up to 2.1 MB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 695.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 695.8 kB or 71% of the original size.
Potential reduce by 227.9 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. Worldmicro.com needs all CSS files to be minified and compressed as it can save up to 227.9 kB or 88% of the original size.
Number of requests can be reduced by 54 (48%)
113
59
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World Micro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.worldmicro.com
1300 ms
wp-emoji-release.min.js
166 ms
styles.css
157 ms
front-styles.css
131 ms
font-awesome.min.css
134 ms
animate.css
138 ms
framework.css
145 ms
components.css
208 ms
style.css
202 ms
theme-styles.css
225 ms
flaticon.css
225 ms
css
25 ms
responsive.css
245 ms
layers-icons.css
239 ms
style.css
267 ms
jquery.js
397 ms
jquery-migrate.min.js
326 ms
front-scripts.js
311 ms
theme.js
307 ms
plugins.js
388 ms
external-tracking.min.js
350 ms
jquery-2.2.0.min.js
8 ms
swiper.css
447 ms
slick.css
390 ms
inline.css
446 ms
custom.css
417 ms
jquery.form.min.js
476 ms
scripts.js
477 ms
qppr_frontend_script.min.js
477 ms
layers.framework.js
477 ms
wp-embed.min.js
478 ms
swiper.js
550 ms
slick.min.js
549 ms
front-carousel.js
548 ms
countUp.min.js
548 ms
front-counter.js
550 ms
js
44 ms
maps.js
550 ms
masonry.min.js
585 ms
layers.masonry.js
634 ms
analytics.js
30 ms
MITlogo-e1448657897831.png
664 ms
2010-WM-Logo.fw_.png
667 ms
QSLD.fw_.png
821 ms
FAA2.fw_.png
899 ms
AS9120.png
669 ms
microtec.fw_.png
665 ms
nikkhom.fw_.png
664 ms
centraltech.fw_.png
666 ms
atlmicro.fw_.png
667 ms
nkg.fw_.png
668 ms
Batteries-e1448307502132.jpg
685 ms
Resistors.jpg
744 ms
circuit-protection-2.jpg
685 ms
Handshake_generic-e1448663772969.jpg
685 ms
ki1-e1448663903141.jpg
884 ms
Lightbulbs-e1448663981230.jpg
896 ms
Space-480x480.jpg
820 ms
bottomlogo1.fw_.png
950 ms
bottomlogo2.fw_.png
972 ms
bottomlogo3.fw_.png
1020 ms
bottomlogo4.fw_.png
1009 ms
bottomlogo5.fw_.png
1926 ms
bottomlogoESD.fw_.png
1703 ms
layers-icons.woff
1490 ms
collect
23 ms
fontawesome-webfont.woff
1571 ms
home2.png
2064 ms
Slider-2.jpg
2000 ms
Slider-3.jpg
2152 ms
Slider-4.jpg
1954 ms
Slider-5.jpg
1746 ms
contactusslider.jpg
1901 ms
counterbg.jpg
2059 ms
RzoNiRR1p2Mqyyz2RwqSMw.woff
29 ms
AwBqWF2kjhlybWamaKMPcT8E0i7KZn-EPnyo3HZu7kw.woff
29 ms
yVHpdQrmTj9Kax1tmFSx2j8E0i7KZn-EPnyo3HZu7kw.woff
27 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
29 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
29 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
27 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
29 ms
MYWJ4lYm5dbZ1UBuYox79D8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
common.js
29 ms
util.js
31 ms
geocoder.js
27 ms
map.js
25 ms
onion.js
27 ms
openhand_8_8.cur
19 ms
AuthenticationService.Authenticate
82 ms
GeocodeService.Search
79 ms
ViewportInfoService.GetViewportInfo
76 ms
stats.js
16 ms
controls.js
11 ms
transparent.png
37 ms
css
78 ms
google4.png
73 ms
marker.js
42 ms
mapcnt6.png
66 ms
sv5.png
65 ms
tmapctrl.png
29 ms
cb_scout5.png
28 ms
tmapctrl4.png
27 ms
imgs8.png
28 ms
vt
52 ms
vt
49 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
10 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
11 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
9 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
10 ms
ViewportInfoService.GetViewportInfo
115 ms
spotlight-poi.png
15 ms
vt
12 ms
vt
50 ms
vt
7 ms
vt
13 ms
vt
8 ms
vt
8 ms
vt
13 ms
vt
18 ms
vt
20 ms
vt
21 ms
vt
30 ms
vt
29 ms
vt
31 ms
vt
32 ms
vt
55 ms
worldmicro.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
worldmicro.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
worldmicro.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 Worldmicro.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 Worldmicro.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.
worldmicro.com
Open Graph description is not detected on the main page of World Micro. 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: