8.1 sec in total
348 ms
6.9 sec
798 ms
Welcome to swear.co.il homepage info - get ready to check S Wear best content right away, or after learning these important things about swear.co.il
רשת חנויות מובילה בהלבשה לנשים ולגברים. חולצות, מכנסיים, טייצים, חזיות ספורט ועוד. אס וור היבואנית הרשמית של Hanes הלבשה תחתונה איכותית
Visit swear.co.ilWe analyzed Swear.co.il page load time and found that the first response time was 348 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
swear.co.il performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value6.3 s
11/100
25%
Value13.8 s
1/100
10%
Value3,740 ms
1/100
30%
Value0.016
100/100
15%
Value24.1 s
0/100
10%
348 ms
1067 ms
50 ms
60 ms
44 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Swear.co.il, 90% (108 requests) were made to S-wear.co.il and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source S-wear.co.il.
Page size can be reduced by 967.4 kB (10%)
9.8 MB
8.9 MB
In fact, the total size of Swear.co.il main page is 9.8 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. 70% of websites need less resources to load. Images take 9.0 MB which makes up the majority of the site volume.
Potential reduce by 387.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 387.5 kB or 89% of the original size.
Potential reduce by 541.0 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. S Wear images are well optimized though.
Potential reduce by 38.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 38.7 kB or 20% of the original size.
Potential reduce by 198 B
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. Swear.co.il has all CSS files already compressed.
Number of requests can be reduced by 49 (44%)
111
62
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of S Wear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
swear.co.il
348 ms
www.s-wear.co.il
1067 ms
calendar.min.css
50 ms
styles-m.min.css
60 ms
flexslider.min.css
44 ms
custom.min.css
105 ms
searchsuiteautocomplete.min.css
51 ms
location-styles.min.css
106 ms
styles.min.css
108 ms
style.min.css
107 ms
grid-mageplaza.min.css
138 ms
font-awesome.min.css
114 ms
magnific-popup.min.css
117 ms
styles-l.min.css
119 ms
owl.carousel.min.css
49 ms
css2
101 ms
require.min.js
131 ms
requirejs-min-resolver.min.js
231 ms
mixins.min.js
227 ms
requirejs-config.min.js
226 ms
markerClusterer.min.js
230 ms
autocomplete.min.js
227 ms
js
106 ms
gtm.js
100 ms
logo.svg
227 ms
TBS_6980-2.jpg
229 ms
IMG_3785new-2.png
652 ms
IMG_9999_47-3.jpg
890 ms
IMG_9991-2.jpg
826 ms
72059_Hanes_DTC_Essence_S04A_272-22.jpg
579 ms
file_4.jpg
844 ms
heart1.svg
236 ms
profile1.svg
280 ms
search.svg
313 ms
cart.svg
324 ms
file_282.webp
356 ms
0128031_522_5_-2.webp
376 ms
f1.svg
397 ms
f2.svg
427 ms
f3.svg
499 ms
307-307_copy.webp
530 ms
0175202_522_7_.webp
563 ms
0104400_740_6_.webp
586 ms
f4.png
972 ms
img_7419-2.webp
608 ms
0114161_309_4_-2.webp
631 ms
f5.svg
654 ms
file_284.jpg
1582 ms
file_285.jpg
1594 ms
_2_81.jpg
1745 ms
_2_82.jpg
1815 ms
0175002_553_7__2.jpg
1279 ms
0153114_301_6_-1.jpg
1391 ms
0175037_309_4_.jpg
1672 ms
font
233 ms
img_3755new_8_1.jpg
1785 ms
0128033_050_23_.jpg
1961 ms
0106016_050_5_.jpg
1989 ms
0106891_050_5_.jpg
2056 ms
events.js
298 ms
thunder.js
231 ms
0128173_740_8_.jpg
2115 ms
img_1030new.png
2431 ms
widget.1.2.min.js
158 ms
accessibility.js
160 ms
fbevents.js
128 ms
jquery.min.js
1623 ms
owlCarousel.min.js
2058 ms
mage.min.js
1755 ms
session.min.js
1733 ms
customer-data.min.js
1713 ms
main.MWFhNzU2YTY5MQ.js
112 ms
url.min.js
1710 ms
underscore.min.js
1707 ms
cookies.min.js
1681 ms
weltpixel_ga4_persistentLayer.min.js
2083 ms
weltpixel_ga4_gtm.min.js
2075 ms
0106142_050_2_.jpg
1991 ms
0114013_147_3_.jpg
2006 ms
0175998_522_2_.jpg
2120 ms
0175139_477_4_-2_4.jpg
2292 ms
0106441_231_6__2.jpg
2302 ms
0228231_477_4_.jpg
2265 ms
0153153_486_7_.jpg
2256 ms
0156115_231_7_-2.jpg
2274 ms
0153122_147_5_.jpg
2438 ms
0162011_231_1_.jpg
2441 ms
0262114_309_men_6_.jpg
2417 ms
__2_14.jpg
2643 ms
__2_15.jpg
2566 ms
file_268.jpg
2389 ms
file_269.jpg
2465 ms
file_260.jpg
2432 ms
file_261.jpg
1968 ms
__2_10.jpg
2671 ms
__2_11.jpg
2428 ms
file_258.jpg
2529 ms
file_259.jpg
2497 ms
facebook.svg
2054 ms
insta.svg
1972 ms
main.min.js
1976 ms
tiktok.svg
1998 ms
Session.min.js
2017 ms
ko.min.js
2423 ms
section-config.min.js
2022 ms
storage.min.js
2030 ms
jquery-storageapi.min.js
2461 ms
load
2625 ms
jquery.cookie.min.js
2204 ms
payment-new-s.png
2060 ms
please-wait.gif
1902 ms
logo.png
1898 ms
Up.svg
1887 ms
scripts.min.js
412 ms
class.min.js
386 ms
Data.min.js
372 ms
validation.min.js
439 ms
startsWith.min.js
23 ms
index
659 ms
print.min.css
27 ms
swear.co.il 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
swear.co.il 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
Missing source maps for large first-party JavaScript
swear.co.il 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
IW
HE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Swear.co.il can be misinterpreted by Google and other search engines. Our service has detected that Hebrew is used on the page, and it does not match the claimed language. Our system also found out that Swear.co.il 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.
swear.co.il
Open Graph description is not detected on the main page of S Wear. 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: