4.6 sec in total
367 ms
3.6 sec
655 ms
Click here to check amazing Why Not Models content for Russia. Otherwise, check out these important facts you probably never knew about whynotmodels.com
Modeling agency and model management in Milano, fashion week, new faces, models for any event in Europe
Visit whynotmodels.comWe analyzed Whynotmodels.com page load time and found that the first response time was 367 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
whynotmodels.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value9.6 s
0/100
25%
Value5.4 s
56/100
10%
Value350 ms
73/100
30%
Value0.089
92/100
15%
Value4.9 s
78/100
10%
367 ms
914 ms
240 ms
25 ms
505 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 75% of them (49 requests) were addressed to the original Whynotmodels.com, 18% (12 requests) were made to Scontent.cdninstagram.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Whynotmodels.com.
Page size can be reduced by 242.3 kB (9%)
2.6 MB
2.4 MB
In fact, the total size of Whynotmodels.com main page is 2.6 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. 30% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 21.6 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 21.6 kB or 78% of the original size.
Potential reduce by 72.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. Why Not Models images are well optimized though.
Potential reduce by 137.7 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 137.7 kB or 67% of the original size.
Potential reduce by 10.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. Whynotmodels.com needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 77% of the original size.
Number of requests can be reduced by 3 (5%)
63
60
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Not Models. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
whynotmodels.com
367 ms
www.whynotmodels.com
914 ms
cmn.css
240 ms
css
25 ms
jquery-1.11.3.min.js
505 ms
jquery.cycle.all.js
478 ms
12716989_1673790986223128_1644475912_n.jpg
360 ms
12716458_932915110095789_1313097380_n.jpg
422 ms
12747561_793938894074143_1931290990_n.jpg
490 ms
12751370_1735221623377408_1779915781_n.jpg
621 ms
12677467_1777770895787213_204806166_n.jpg
624 ms
12797814_967415956662229_1610511440_n.jpg
624 ms
12716637_334009000056017_1478397798_n.jpg
560 ms
12748309_175205389526463_1895517811_n.jpg
561 ms
10387783_258183814513660_1601841271_n.jpg
558 ms
12328132_450915831777297_388289036_n.jpg
625 ms
12424648_1732679450297388_576223988_n.jpg
691 ms
1516882_855004944610886_1148832658_n.jpg
694 ms
h-3877_aamito-lagum1.jpg
631 ms
h-3877_aamito-lagum2.jpg
953 ms
h-3877_aamito-lagum3.jpg
1231 ms
h-3877_aamito-lagum4.jpg
950 ms
h-3877_aamito-lagum5.jpg
1086 ms
h-3877_aamito-lagum6.jpg
996 ms
4039_G-ARMANI.jpg
884 ms
4038_DS2.jpg
1016 ms
4037_DAMIR.jpg
1083 ms
4036_MISSONI.jpg
1186 ms
logoverde.png
1114 ms
t-4019_0.jpg
1140 ms
t-4018_cover.jpg
1202 ms
t-4003_cover.jpg
1202 ms
t-3998_11.jpg
1237 ms
t-4017_1.jpg
1266 ms
t-4002_1.jpg
1303 ms
t-4001_1.jpg
1318 ms
t-3997_1.jpg
1322 ms
t-3995_1.jpg
1360 ms
t-3990_1.jpg
1359 ms
t-4016_2.jpg
1389 ms
t-4004_8.jpg
1417 ms
t-3996_12.jpg
1435 ms
t-3977_cover.jpg
1439 ms
t-3846_x.jpg
1481 ms
t-3845_cover.jpg
1490 ms
t-3844_1.jpg
1513 ms
3842_ne-cai_lee.jpg
1531 ms
3842_ne-matty_carrington.jpg
1553 ms
3842_js-naki.jpg
1555 ms
3842_js-james_magee.jpg
1604 ms
thumb_3648_479112.jpg
1618 ms
thumb_3642_482229.jpg
1634 ms
thumb_3658_480265.jpg
1645 ms
thumb_3510_456777.jpg
1658 ms
analytics.js
31 ms
collect
19 ms
thumb_3442_440425.jpg
1049 ms
thumb_2888_368763.jpg
845 ms
big-green-logo.png
807 ms
map-marker-icon.png
812 ms
facebookicon.png
772 ms
instagramicon.png
777 ms
twittericon.png
712 ms
assem-logo.png
765 ms
iubenda.js
11 ms
whynotmodels.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
Links do not have a discernible name
whynotmodels.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
whynotmodels.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whynotmodels.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whynotmodels.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.
whynotmodels.com
Open Graph description is not detected on the main page of Why Not Models. 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: