3.5 sec in total
848 ms
2.5 sec
201 ms
Click here to check amazing UGLY content for Belgium. Otherwise, check out these important facts you probably never knew about ugly.be
Verkoop of koop je huis of appartement aan de juiste prijs dankzij onze ervaring, styling, teksten en foto’s. Contacteer ons vrijblijvend.
Visit ugly.beWe analyzed Ugly.be page load time and found that the first response time was 848 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
ugly.be performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value13.0 s
0/100
25%
Value10.3 s
8/100
10%
Value2,180 ms
6/100
30%
Value0.004
100/100
15%
Value15.1 s
7/100
10%
848 ms
99 ms
183 ms
279 ms
189 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 70% of them (16 requests) were addressed to the original Ugly.be, 9% (2 requests) were made to Google-analytics.com and 9% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ugly.be.
Page size can be reduced by 151.9 kB (20%)
744.1 kB
592.2 kB
In fact, the total size of Ugly.be main page is 744.1 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. 25% of websites need less resources to load. Images take 532.5 kB which makes up the majority of the site volume.
Potential reduce by 13.7 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 13.7 kB or 72% of the original size.
Potential reduce by 7.6 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. UGLY images are well optimized though.
Potential reduce by 98.4 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 98.4 kB or 63% of the original size.
Potential reduce by 32.2 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. Ugly.be needs all CSS files to be minified and compressed as it can save up to 32.2 kB or 87% of the original size.
Number of requests can be reduced by 5 (25%)
20
15
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UGLY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
ugly.be
848 ms
MyFontsWebfontsKit.css
99 ms
style.css
183 ms
jquery-1.10.2.min.js
279 ms
form.js
189 ms
frontend.js
195 ms
jquery.backstretch.min.js
206 ms
28bb61
14 ms
page-grey.png
97 ms
all.js
161 ms
icons.png
91 ms
ugly-logo.png
104 ms
trans.png
92 ms
analytics.js
12 ms
_J6A6049MediumMedium.JPG
625 ms
58f52d1b039ba86add951e4b7c21bc56.jpg
1270 ms
figr1_surface50_kitchen.jpg
600 ms
28BB61_1_0.woff
243 ms
28BB61_0_0.woff
357 ms
collect
12 ms
155 ms
xd_arbiter.php
161 ms
xd_arbiter.php
269 ms
ugly.be 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.
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
ugly.be 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
Missing source maps for large first-party JavaScript
ugly.be 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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ugly.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Ugly.be 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.
ugly.be
Open Graph description is not detected on the main page of UGLY. 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: