2.4 sec in total
193 ms
1.9 sec
253 ms
Click here to check amazing Excess DB content. Otherwise, check out these important facts you probably never knew about excessdb.com
Marketing & Brand Strategy agency specializing in music and entertainment properties.
Visit excessdb.comWe analyzed Excessdb.com page load time and found that the first response time was 193 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
excessdb.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value18.1 s
0/100
25%
Value12.6 s
3/100
10%
Value3,160 ms
2/100
30%
Value0.105
88/100
15%
Value20.5 s
2/100
10%
193 ms
318 ms
319 ms
265 ms
197 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 46% of them (40 requests) were addressed to the original Excessdb.com, 21% (18 requests) were made to Pbs.twimg.com and 6% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (595 ms) relates to the external source Api.ticketweb.com.
Page size can be reduced by 407.1 kB (18%)
2.3 MB
1.9 MB
In fact, the total size of Excessdb.com main page is 2.3 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 8.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 8.1 kB or 73% of the original size.
Potential reduce by 34.5 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. Excess DB images are well optimized though.
Potential reduce by 332.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 332.4 kB or 64% of the original size.
Potential reduce by 32.1 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. Excessdb.com needs all CSS files to be minified and compressed as it can save up to 32.1 kB or 83% of the original size.
Number of requests can be reduced by 44 (52%)
85
41
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Excess DB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
excessdb.com
193 ms
HttpRequest.js
318 ms
pageTracking.js
319 ms
TrackingAjax.aspx
265 ms
excessbg.gif
197 ms
concertlistingheader.php
113 ms
twitter-feed.html
75 ms
concertlisting.php
113 ms
excessdb_01.gif
77 ms
excessdb_02.gif
76 ms
excessdb_03.gif
185 ms
excessdb_04.gif
184 ms
excessdb_05.gif
182 ms
excessdb_06.gif
218 ms
excessdb_09.gif
218 ms
excessdb_10.gif
220 ms
excessdb_11.gif
256 ms
excessdb_12.gif
256 ms
excessdb_13.gif
257 ms
excessdb_14.gif
290 ms
excessdb_15.gif
290 ms
excessdb_16.gif
293 ms
excessdb_17.gif
348 ms
excessdb_18.gif
348 ms
excessdb_19.gif
347 ms
excessdb_20.gif
376 ms
excessdb_21.gif
375 ms
excessdb_22.gif
375 ms
excessdb_23.gif
412 ms
excessdb_24.gif
414 ms
excessdb_26.gif
413 ms
excessdb_27.gif
448 ms
excessdb_28.gif
448 ms
right.gif
448 ms
excessdb_48.gif
484 ms
excessdb_49.gif
485 ms
excessdb_50.gif
486 ms
excessdb_51.gif
521 ms
excessdb_54.gif
520 ms
excessdb_55.gif
521 ms
widgets.js
112 ms
spacer.gif
495 ms
lg-share-en.gif
74 ms
addthis_widget.js
10 ms
TWEventAPIPlugin.js
171 ms
tw-db-listings.css
465 ms
pub.140101.min.js
592 ms
concertlistingheader.gif
461 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
131 ms
jquery.min.js
30 ms
syndication
97 ms
346644370738524160
193 ms
proxy.jpg
103 ms
proxy.jpg
138 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
84 ms
style.css
132 ms
EventAPI.action
595 ms
db-sq_normal.jpg
53 ms
08xnZIT4_normal.jpg
92 ms
arjlixg1o49yvfd6fl6r_normal.png
92 ms
EQquJgLn_normal.jpeg
90 ms
7ubFSOX0_normal.jpg
90 ms
tTNPwJej_normal.jpg
146 ms
pindesign_crass_tealorange_normal.jpg
92 ms
Qvc-5-0d_normal.jpeg
94 ms
Wpf4C8dv_normal.jpeg
93 ms
Lt1jJfgk_normal.png
94 ms
COfTrh5UcAE-Omc.jpg:small
219 ms
CNLdEQ4WwAEMoCu.jpg:small
210 ms
CNMnc3sWIAA7lbx.jpg:small
225 ms
CNDk-6kUAAA5G5b.jpg:small
211 ms
CK8BSvRUcAAPHZ_.png:small
211 ms
CLAXM_oWgAArPgA.jpg:small
152 ms
CK73GsyWcAASCoa.png:small
332 ms
CCQp4RRW4AAIbA_.png:small
212 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
48 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
88 ms
ga.js
4 ms
__utm.gif
37 ms
300lo.json
26 ms
sh.8e5f85691f9aaa082472a194.html
38 ms
proxy.jpg
35 ms
proxy.jpg
52 ms
pixel
16 ms
pixel
13 ms
jot.html
29 ms
excessdb.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
<frame> or <iframe> elements do not have a title
excessdb.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
Page has valid source maps
excessdb.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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Excessdb.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 Excessdb.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
excessdb.com
Open Graph description is not detected on the main page of Excess DB. 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: