2 sec in total
149 ms
1.4 sec
423 ms
Click here to check amazing Staging Api Close 5 content for United States. Otherwise, check out these important facts you probably never knew about staging-api.close5.com
Buy & sell electronics, cars, clothes, collectibles & more on eBay, the world's online marketplace. Top brands, low prices & free shipping on many items.
Visit staging-api.close5.comWe analyzed Staging-api.close5.com page load time and found that the first response time was 149 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
staging-api.close5.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value7.1 s
5/100
25%
Value7.5 s
27/100
10%
Value1,560 ms
13/100
30%
Value0.013
100/100
15%
Value17.1 s
4/100
10%
149 ms
473 ms
26 ms
62 ms
33 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Staging-api.close5.com, 51% (26 requests) were made to I.ebayimg.com and 39% (20 requests) were made to Ir.ebaystatic.com. The less responsive or slowest element that took the longest time to load (473 ms) relates to the external source Ebay.com.
Page size can be reduced by 1.1 MB (40%)
2.7 MB
1.6 MB
In fact, the total size of Staging-api.close5.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. 60% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.
Potential reduce by 1.1 MB
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 1.1 MB or 90% of the original size.
Potential reduce by 28.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. Staging Api Close 5 images are well optimized though.
Potential reduce by 0 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 311 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. Staging-api.close5.com has all CSS files already compressed.
Number of requests can be reduced by 14 (30%)
47
33
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Staging Api Close 5. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
staging-api.close5.com
149 ms
www.ebay.com
473 ms
kt4lmpewo203tcaltpljn4gcuyw.css
26 ms
r.6618b3ca.js
62 ms
r.5efe8cf9.css
33 ms
s_1x2.gif
113 ms
s-w300.jpg
115 ms
jquery-3.7.0.min.js
155 ms
h0uj1osj1y1nlldfgf21ohvmvug.css
90 ms
dimst35tei5k5cjwlytmmoocgq2.js
91 ms
5.js
90 ms
nh24070265b74ffae1964cce828.js
99 ms
ubt24070236dd1e675d8f4e7497.js
100 ms
$_7.JPG
99 ms
s-w300.jpg
101 ms
$_7.JPG
98 ms
s-w300.jpg
142 ms
$_7.JPG
97 ms
s-w300.jpg
103 ms
s-l140.webp
104 ms
s-w300.jpg
141 ms
s-l140.webp
198 ms
s-w300.jpg
140 ms
$_7.JPG
139 ms
s-w300.jpg
143 ms
$_7.JPG
141 ms
s-w300.jpg
142 ms
$_7.PNG
143 ms
s-w300.jpg
145 ms
s-w300.jpg
145 ms
$_7.PNG
145 ms
s-w300.jpg
156 ms
s-w300.jpg
159 ms
s-w300.jpg
156 ms
s-l140.webp
157 ms
s-w300.jpg
158 ms
$_7.JPG
160 ms
s-w300.jpg
160 ms
s_1x2.gif
90 ms
s_1x2.gif
92 ms
s_1x2.gif
95 ms
s_1x2.gif
96 ms
s_1x2.gif
96 ms
s_1x2.gif
98 ms
MarketSans-Regular-WebS.woff
28 ms
MarketSans-SemiBold-WebS.woff
88 ms
sprds3_20.png
30 ms
fxxj3ttftm5ltcqnto1o4baovyl.png
27 ms
autocomplete
150 ms
9
324 ms
ac-080124220202.dweb.min.js
2 ms
staging-api.close5.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
Image elements do not have [alt] attributes
staging-api.close5.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
Missing source maps for large first-party JavaScript
staging-api.close5.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
Image elements do not have [alt] attributes
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 Staging-api.close5.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 Staging-api.close5.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.
staging-api.close5.com
Open Graph data is detected on the main page of Staging Api Close 5. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: