10.3 sec in total
517 ms
6.1 sec
3.7 sec
Click here to check amazing Only content for Germany. Otherwise, check out these important facts you probably never knew about only.com
Discover womenswear with a mature twist & focus on feminine strength, self-confidence, and style. Shop at ONLY's official store today!
Visit only.comWe analyzed Only.com page load time and found that the first response time was 517 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
only.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value3.7 s
57/100
25%
Value4.8 s
66/100
10%
Value40 ms
100/100
30%
Value0.01
100/100
15%
Value4.8 s
79/100
10%
517 ms
195 ms
379 ms
513 ms
22 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 6% of them (7 requests) were addressed to the original Only.com, 63% (69 requests) were made to Demandware.edgesuite.net and 7% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Demandware.edgesuite.net.
Page size can be reduced by 1.6 MB (38%)
4.1 MB
2.6 MB
In fact, the total size of Only.com main page is 4.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. 75% 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 243.3 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 65.4 kB, which is 24% 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 243.3 kB or 90% of the original size.
Potential reduce by 34.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. Only images are well optimized though.
Potential reduce by 684.2 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 684.2 kB or 69% of the original size.
Potential reduce by 618.3 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. Only.com needs all CSS files to be minified and compressed as it can save up to 618.3 kB or 69% of the original size.
Number of requests can be reduced by 36 (38%)
95
59
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Only. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
only.com
517 ms
Page-SetCountry
195 ms
Page-WelcomeBrand
379 ms
only.com
513 ms
styles.css
22 ms
only2015-inc.css
198 ms
scripts-header.js
21 ms
site.css
20 ms
only.js
197 ms
dwac-14.8.js
19 ms
on-flipcard.js
210 ms
on-flyout-fix.js
209 ms
ON-fonts.css
383 ms
scripts-footer.js
25 ms
dwanalytics.js
4 ms
gretel.min.js
10 ms
only2015.css
293 ms
on-content.css
204 ms
font-awesome.min.css
42 ms
dc.js
59 ms
icon_basket.svg
33 ms
icon_account.svg
28 ms
icon_help.svg
39 ms
Frontpage_slide_1.jpg
556 ms
Frontpage_slide_2.jpg
547 ms
Frontpage_01.jpg
395 ms
Frontpage_03.jpg
547 ms
Frontpage_02.jpg
659 ms
Frontpage_04.jpg
541 ms
15111483_PeachBlush_498506_001_List.jpg
542 ms
15100494_BrownStone_456552_001_List.jpg
598 ms
15116981_LightGreyMelange_001_List.jpg
597 ms
15115847_Tarmac_001_List.jpg
604 ms
15117627_DarkGreyMelange_004_List.jpg
634 ms
15112644_CloudDancer_502452_001_List.jpg
654 ms
15112373_PumiceStone_004_List.jpg
667 ms
15112848_MediumBlueDenim_004_List.jpg
670 ms
15112345_Cognac_004_List.jpg
669 ms
15111032_LightGreyMelange_001_List.jpg
748 ms
15112956_NightSky_004_List.jpg
749 ms
15120090_Tarmac_004_List.jpg
749 ms
15115743_DarkBlueDenim_004_List.jpg
768 ms
15118934_Black_518294_004_List.jpg
788 ms
15113536_CloudDancer_505657_001_List.jpg
787 ms
15110384_NightSky_503687_004_List.jpg
844 ms
15113066_DarkBlueDenim_004_List.jpg
845 ms
15120512_Black_004_List.jpg
844 ms
15116579_Nude_002_List.jpg
860 ms
15116555_Black_514266_001_List.jpg
895 ms
Frontpage_05.jpg
1043 ms
Frontpage_07.jpg
1042 ms
Frontpage_06.jpg
2156 ms
Frontpage_08.jpg
947 ms
Frontpage_09_front.jpg
1038 ms
Frontpage_09_back.jpg
1037 ms
Frontpage_10_front.jpg
1072 ms
Frontpage_10_back.jpg
1085 ms
Frontpage_11_front.jpg
1076 ms
Frontpage_11_back.jpg
1082 ms
inpage_linkid.js
26 ms
gtm.js
155 ms
hbAEjQAAAVUBlzIAAA==
91 ms
hbAEjQAAAVUBlzIAAA==
79 ms
__utm.gif
23 ms
fontawesome-webfont.woff
69 ms
analytics.js
20 ms
Frontpage_12_front.jpg
712 ms
ec.js
26 ms
Frontpage_12_back.jpg
649 ms
tsVeriSignTrusted.jpg
564 ms
64-chrome.png
559 ms
64-firefox.png
559 ms
collect
20 ms
64-safari.png
518 ms
64-ie.png
509 ms
arrow-up.png
1539 ms
arrow-down.png
1554 ms
only.svg
1526 ms
pil-left.png
1508 ms
pil-right.png
1495 ms
carousel_prev_horizontal.png
1492 ms
carousel_next_horizontal.png
1483 ms
bg_logo_footer.png
1119 ms
general-icons-sprite.png
1114 ms
go-to-top-arrow.png
1115 ms
ubertags.js
70 ms
UT-528514774
34 ms
851 ms
fbevents.js
842 ms
53 ms
61 ms
61 ms
76 ms
63 ms
62 ms
61 ms
75 ms
1923.js
57 ms
90 ms
89 ms
87 ms
125 ms
126 ms
86 ms
72 ms
pebble
71 ms
Page-GetCountryRedirectAjax
264 ms
GB_flag.png
41 ms
only.com
299 ms
__Analytics-Tracking
223 ms
only.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
<object> elements do not have alternate text
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
only.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
Browser errors were logged to the console
only.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Only.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 Only.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.
only.com
Open Graph description is not detected on the main page of Only. 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: