87.7 sec in total
222 ms
77.4 sec
10.1 sec
Click here to check amazing Teva content for United States. Otherwise, check out these important facts you probably never knew about teva.com
Pioneered in 1984, Teva® is your guide for adventure from the everyday to the epic. Visit the Teva® Official Site for shoes, active sandals, hikers, boots, and more.
Visit teva.comWe analyzed Teva.com page load time and found that the first response time was 222 ms and then it took 87.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
teva.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value7.8 s
3/100
25%
Value13.5 s
2/100
10%
Value33,660 ms
0/100
30%
Value0.132
81/100
15%
Value50.0 s
0/100
10%
222 ms
930 ms
900 ms
828 ms
1618 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 7% of them (5 requests) were addressed to the original Teva.com, 30% (21 requests) were made to Demandware.edgesuite.net and 6% (4 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Cdn.cquotient.com.
Page size can be reduced by 1.7 MB (35%)
5.0 MB
3.2 MB
In fact, the total size of Teva.com main page is 5.0 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.5 MB which makes up the majority of the site volume.
Potential reduce by 54.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. 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 54.3 kB or 80% of the original size.
Potential reduce by 44.1 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. Teva images are well optimized though.
Potential reduce by 882.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 882.4 kB or 66% of the original size.
Potential reduce by 766.8 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. Teva.com needs all CSS files to be minified and compressed as it can save up to 766.8 kB or 77% of the original size.
Number of requests can be reduced by 38 (67%)
57
19
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teva. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
teva.com
222 ms
www.teva.com
930 ms
head.min.js
900 ms
storefront.css
828 ms
248292e06b9f3390abbe9021cb3dbc0f.js
1618 ms
fonts.css
1616 ms
modernizr-min.js
1499 ms
polyfill.min.js
1498 ms
jquery.min.js
1542 ms
jquery.mobile.custom.min.js
1541 ms
responsive.min.js
1539 ms
slider.min.js
1540 ms
Resources-Load
3251 ms
plugins.min.js
3237 ms
app.min.js
3211 ms
BrightcoveExperiences.js
3212 ms
utag.js
3212 ms
dwanalytics-16.9.js
3210 ms
dwac-16.9.js
3209 ms
gretel.min.js
3901 ms
applepay.js
3172 ms
FE5069AA5A7BE711F.css
2522 ms
geolocAndWeather.php
3440 ms
teva-site-logo.svg
1351 ms
sprite.svg
879 ms
F17-SEP-BootsGuide_Banner_HP-Desktop.jpg
1653 ms
Aug_EmberMoc_Banner_HP-Desktop.jpg
1654 ms
Aug_ArrowoodFamily_Banner_HP-Desktop.jpg
1653 ms
F17-SEP-SocksAndSandals_Banner_HP-Desktop.jpg
1651 ms
apple-pay.png
1650 ms
Hxwc6DOzk+J+UvDME9UQ==
160 ms
yE3FH1NRDAfenF3UYwtBKbsRU8h2CxT23gccxT3YNFctX8HrTW+lqWU0MXFwkD4GOsxifHuw8uJPj76T8DfyLPU0=
3 ms
Hxwc6DOzk+J+UvDME9UQ==
2 ms
A38iz1N
2 ms
select-arrow.png
78 ms
Cart-MiniCart
2034 ms
SEWVW-6VWNN-MYAL3-6YWK6-YKFWT
567 ms
sprite--white.svg
1253 ms
id
1958 ms
ga.js
1955 ms
fbevents.js
1714 ms
utag.332.js
1711 ms
utag.367.js
1621 ms
i.gif
2238 ms
main.min.js
1395 ms
pxPixel.gif
1383 ms
activityi;src=8112555;type=gener0;cat=unive0;u13=TEVA-US;u14=storefront;u19=false;ord=7788798352703.452
1521 ms
activityi;src=8112555;type=gener0;cat=homep0;u13=TEVA-US;u14=storefront;u19=false;ord=8557705753482.878
1737 ms
config.js
466 ms
pebble
0 ms
id
0 ms
__utm.gif
0 ms
974057282662515
0 ms
utag.v.js
0 ms
collector
0 ms
collect
841 ms
s79463219172321
485 ms
970 ms
920 ms
ga-audiences
851 ms
ct.pinterest.com
1966 ms
conversion_async.js
1525 ms
smarttag.js
1180 ms
ld.js
775 ms
iui3
1184 ms
__Analytics-Tracking
1353 ms
event
1025 ms
smarttagevent
947 ms
14 ms
dis.aspx
2233 ms
2054 ms
teva.com accessibility score
teva.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
Missing source maps for large first-party JavaScript
teva.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teva.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 Teva.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.
teva.com
Open Graph description is not detected on the main page of Teva. 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: