5.6 sec in total
14 ms
5.4 sec
244 ms
Visit gazelle.com now to see the best up-to-date Gazelle content for United States and also check out these interesting facts you probably never knew about gazelle.com
Buy and Sell your used cell phones and electronics. Sell your iPhone, Samsung Galaxy, iPad and more for cash, or buy used iPhones, iPads and other cell phones. More than one million customers trust Ga...
Visit gazelle.comWe analyzed Gazelle.com page load time and found that the first response time was 14 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
gazelle.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value17.5 s
0/100
25%
Value11.1 s
6/100
10%
Value16,010 ms
0/100
30%
Value0
100/100
15%
Value31.7 s
0/100
10%
14 ms
64 ms
192 ms
85 ms
66 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Gazelle.com, 19% (16 requests) were made to Cdn.gazelle.com and 18% (15 requests) were made to M3-beta.gazelle.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Ssif1.globalsign.com.
Page size can be reduced by 1.6 MB (59%)
2.7 MB
1.1 MB
In fact, the total size of Gazelle.com main page is 2.7 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. 55% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 177.1 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 177.1 kB or 82% of the original size.
Potential reduce by 29.8 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. Gazelle images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 64% of the original size.
Potential reduce by 158.5 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. Gazelle.com needs all CSS files to be minified and compressed as it can save up to 158.5 kB or 87% of the original size.
Number of requests can be reduced by 28 (35%)
80
52
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gazelle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
gazelle.com
14 ms
www.gazelle.com
64 ms
127283929.js
192 ms
core.js
85 ms
font-awesome.min.css
66 ms
gigya.js
77 ms
combined_home-ea3f25cf88ea8c293b455124b39cc765.css
95 ms
modernizr-2.6.2-respond-1.1.0.min-245b59cfb6f2cfc8c8f396b54605f488.js
98 ms
raven.min-4330f634506cef775f658221cb9dbf94.js
98 ms
107 ms
conversion.js
79 ms
geo2.js
187 ms
event
51 ms
dc.js
80 ms
go.js
373 ms
addthis_widget.js
67 ms
__utm.gif
71 ms
promo_box-e67c7315e660f45ba4c3cc7c041db3f3.png
117 ms
gazelle_grid1_original.png
304 ms
social_twitter-9a2030496cf49ae6cc9c46491b4d28b8.svg
115 ms
social_google-76d10ae9ca7a8d7dbfb64b59aeb676d6.svg
113 ms
social_facebook-a9aa9d31751a8850ea23a807c4aa83d0.svg
114 ms
gazelle_grid2_original.jpg
329 ms
gazelle_grid3b_original.png
302 ms
gazelle_grid3_original.png
300 ms
gazelle_grid4_original.jpg
330 ms
gazelle_grid5_original.jpg
301 ms
gazelle_grid6b_original.png
329 ms
gazelle_grid6_original.png
329 ms
gazelle_grid7_original.jpg
341 ms
Consumersareblownaway...._original.png
344 ms
gazelle_grid8_original.png
343 ms
gazelle_grid9_original.png
344 ms
gazelle_grid10_original.jpg
343 ms
gazelle_grid11b_original.png
344 ms
gazelle_grid11_original.png
345 ms
gazelle_grid12_original.png
348 ms
logo-c5d4140f29a759a5ab9da28075e8cfec.svg
166 ms
iphone_samsung_full_reflection-14a2992476739a00c3138387353e477b.png
294 ms
gazelle_buyarrow-3788b319fb849ef39a33211c7e8812d0.svg
240 ms
gazelle_sellarrow-21166bef422f712d03461b7021e3d550.svg
202 ms
social_blog-760b277546c49fd4d28ea7ba241f874b.svg
163 ms
event
35 ms
ga-audiences
142 ms
brandon_reg-webfont-4160fab47661162739279296b7ceeeaa.woff
202 ms
brandon_light-webfont-c0c190ec7cdc40baa9c12495e1565cb0.woff
201 ms
brandon_thin-webfont-aa928f17ef673cb3b0889ace05c050ac.woff
256 ms
brandon_med-webfont-cbc06601d53e84db8b0f5f6577996c06.woff
203 ms
brandon_bld-webfont-ed389a7750fe6dd6d2af22e03015948f.woff
289 ms
brandon_med_it-webfont-df88c1f74813329739f19816f37b385c.woff
288 ms
brandon_reg_it-webfont-4333bdf2e2d977f853aed61520dcc1eb.woff
289 ms
brandon_light_it-webfont-c0ab34a9fdde16aed10a8353c5b03a19.woff
288 ms
brandon_thin_it-webfont-3d00d6e2fb6943cc763dfae26697eda4.woff
287 ms
activity;src=4167343;type=gazel508;cat=httpw531;ord=b7c1decd-e9c4-4861-9ece-d1a7b4b0fbbb
258 ms
ld.js
277 ms
fbds.js
278 ms
bat.js
269 ms
221 ms
300lo.json
204 ms
sh.7c7179124ea24ac6ba46caac.html
89 ms
campaign_5373d33c5e29cc1624000003_20160114.0701.json
608 ms
50 ms
social_refer.png
20 ms
campaign_552d5bb86ad782ffb7000008_20160114.0701.json
164 ms
20 ms
nr-852.min.js
158 ms
cert_footer
15 ms
10 ms
blue-seal-200-42-gazelle-100835.png
577 ms
gs_noscript_110-45_en.gif
43 ms
gmogs_image_110-45_en_dblue.js
47 ms
siteSeal.do
4414 ms
address_books.js
65 ms
email.png
40 ms
facebook.png
83 ms
twitter.png
91 ms
extole-logo.png
110 ms
3d39f317e2
138 ms
floatbox.css
29 ms
options.js
29 ms
provider
28 ms
channel-8c52fcb10f6b624cf7740b7fa87ca2f5.js
6 ms
analytics.js
22 ms
core.js
8 ms
gazelle.com 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.
gazelle.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
Browser errors were logged to the console
Page has valid source maps
gazelle.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gazelle.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 Gazelle.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.
gazelle.com
Open Graph description is not detected on the main page of Gazelle. 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: