7.6 sec in total
3.1 sec
4.3 sec
205 ms
Click here to check amazing FRAAL content. Otherwise, check out these important facts you probably never knew about fraal.com
Fraal Import & Export N.V. - Your 1st choice in Wholesale Distributor! Very competitive pricing and speedy delivery time that is hard to beat! Fraal
Visit fraal.comWe analyzed Fraal.com page load time and found that the first response time was 3.1 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fraal.com performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value12.8 s
0/100
25%
Value26.9 s
0/100
10%
Value25,680 ms
0/100
30%
Value0
100/100
15%
Value38.7 s
0/100
10%
3074 ms
207 ms
129 ms
142 ms
184 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 60% of them (53 requests) were addressed to the original Fraal.com, 16% (14 requests) were made to Maps.google.com and 11% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Fraal.com.
Page size can be reduced by 1.1 MB (49%)
2.2 MB
1.1 MB
In fact, the total size of Fraal.com main page is 2.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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 36.5 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 36.5 kB or 79% of the original size.
Potential reduce by 52.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. FRAAL images are well optimized though.
Potential reduce by 798.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 798.8 kB or 68% of the original size.
Potential reduce by 201.0 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. Fraal.com needs all CSS files to be minified and compressed as it can save up to 201.0 kB or 83% of the original size.
Number of requests can be reduced by 53 (63%)
84
31
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FRAAL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
fraal.com
3074 ms
typography2.php
207 ms
reset.css
129 ms
auto.css
142 ms
bootstrap.min.css
184 ms
superfish.css
170 ms
template.css
171 ms
font-awesome.css
212 ms
style.css
221 ms
social.css
265 ms
template.css
249 ms
main.css
287 ms
creative_buttons.css
284 ms
sexycss-ui.css
297 ms
js
43 ms
mootools-core.js
320 ms
jquery.min.js
348 ms
jquery-noconflict.js
344 ms
jquery-migrate.min.js
345 ms
core.js
362 ms
mootools-more.js
452 ms
bootstrap.min.js
405 ms
jquery.min.js
168 ms
modernizr-2.6.2.min.js
501 ms
init.js
432 ms
hoverIntent.js
439 ms
superfish.js
449 ms
scripts.js
519 ms
jquery.mobmenu.js
520 ms
sexylib.js
555 ms
sexylib-ui.js
566 ms
mousewheel.js
524 ms
creativeimageslider.js
533 ms
style.css
571 ms
plugin_googlemap3.css.php
609 ms
adapt.js
588 ms
noconflict.js
618 ms
jsapi
42 ms
64 ms
googleearth.js
672 ms
googlemapsv3.js
679 ms
wowslider.js
543 ms
blur.js
515 ms
squares.png
179 ms
input-bg.png
191 ms
default.I.js
11 ms
facebook.png
108 ms
ScanFraalLogoSmall.jpg
150 ms
es.gif
108 ms
en.gif
87 ms
dark.png
105 ms
Remia_Slider_Pic.jpg
301 ms
PAN_Slider_Pic.jpg
257 ms
Diamond_Slider_Pic.jpg
287 ms
Armor_All_Slider_Pic.jpg
346 ms
PK_groene_pesto.jpg
308 ms
line.png
243 ms
common.js
7 ms
map.js
22 ms
util.js
21 ms
marker.js
20 ms
StaticMapService.GetMapImage
167 ms
onion.js
27 ms
openhand_8_8.cur
43 ms
ViewportInfoService.GetViewportInfo
57 ms
stats.js
16 ms
controls.js
12 ms
transparent.png
58 ms
css
52 ms
infowindow.js
37 ms
spotlight-poi.png
34 ms
google4.png
33 ms
mapcnt6.png
35 ms
sv5.png
35 ms
vt
51 ms
vt
28 ms
vt
56 ms
vt
46 ms
vt
50 ms
tmapctrl.png
18 ms
cb_scout5.png
40 ms
tmapctrl4.png
13 ms
imgs8.png
21 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
58 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
76 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
90 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
109 ms
AuthenticationService.Authenticate
50 ms
slider4_controls.png
83 ms
fraal.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fraal.com 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
Page has valid source maps
fraal.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Fraal.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 Fraal.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.
fraal.com
Open Graph description is not detected on the main page of FRAAL. 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: