2.2 sec in total
239 ms
1.7 sec
358 ms
Click here to check amazing Geffen content. Otherwise, check out these important facts you probably never knew about geffen.com
Visit geffen.comWe analyzed Geffen.com page load time and found that the first response time was 239 ms and then it took 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.
geffen.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value9.9 s
0/100
25%
Value13.6 s
2/100
10%
Value3,430 ms
2/100
30%
Value0.098
90/100
15%
Value36.0 s
0/100
10%
239 ms
422 ms
61 ms
62 ms
63 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Geffen.com, 45% (55 requests) were made to Interscope.com and 32% (39 requests) were made to Cache.umusic.com. The less responsive or slowest element that took the longest time to load (486 ms) relates to the external source Platform.twitter.com.
Page size can be reduced by 538.0 kB (66%)
811.9 kB
273.9 kB
In fact, the total size of Geffen.com main page is 811.9 kB. 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 548.7 kB which makes up the majority of the site volume.
Potential reduce by 45.6 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 45.6 kB or 77% of the original size.
Potential reduce by 4.9 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. Geffen images are well optimized though.
Potential reduce by 373.0 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 373.0 kB or 68% of the original size.
Potential reduce by 114.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. Geffen.com needs all CSS files to be minified and compressed as it can save up to 114.5 kB or 84% of the original size.
Number of requests can be reduced by 105 (91%)
115
10
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geffen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
geffen.com
239 ms
www.interscope.com
422 ms
system.base.css
61 ms
system.messages.css
62 ms
system.theme.css
63 ms
comment.css
72 ms
date.css
71 ms
field.css
73 ms
google_analytics_reports.css
75 ms
node.css
73 ms
search.css
75 ms
user.css
75 ms
views.css
75 ms
colorbox_style.css
57 ms
ctools.css
57 ms
taxonomy_access.css
58 ms
normalize.css
59 ms
wireframes.css
59 ms
responsive-sidebars.css
60 ms
tabs.css
71 ms
pages.css
71 ms
blocks.css
72 ms
navigation.css
72 ms
views-styles.css
74 ms
nodes.css
74 ms
comments.css
74 ms
forms.css
92 ms
fields.css
87 ms
print.css
88 ms
fonts.css
75 ms
layout-combined.css
87 ms
jquery.min.js
93 ms
jquery.once.js
197 ms
drupal.js
116 ms
require.js
111 ms
iga.require.main.min.js
113 ms
iga.livefyre.min.js
112 ms
iga_common-social-script-init.js
174 ms
google_analytics_reports.js
239 ms
iga_common.js
190 ms
colorbox.js
240 ms
jquery.mousewheel.js
107 ms
mwheelIntent.js
107 ms
colorbox_style.js
148 ms
googleanalytics.js
252 ms
iga_common-social-analytics.js
249 ms
config.prod.js
326 ms
iga.followbar.js
310 ms
iga.carousel.js
324 ms
iga.footer.js
308 ms
interscope-main.js
339 ms
bounce
19 ms
all.js
356 ms
widgets.js
486 ms
plusone.js
283 ms
ga.js
154 ms
logo.png
216 ms
IGA.jpg
223 ms
favicon.ico
221 ms
interscope.png
220 ms
arrow-light-left.png
211 ms
arrow-light-right.png
210 ms
arrow-dark-left.png
231 ms
arrow-dark-right.png
231 ms
async_usersync.html
88 ms
23C632_0_0.woff
442 ms
_Incapsula_Resource
123 ms
async_usersync
74 ms
circular-linked-list.js
66 ms
jquery.cookie.min.js
67 ms
hogan-2.0.0.min.amd.js
65 ms
iga.livefyre-isotope-river.min.js
63 ms
InterscopeView.opt.min.js
67 ms
jquery.isotope.masonry-modified-layouts.min.js
66 ms
__utm.gif
40 ms
jquery.mousewheel.min.js
69 ms
mwheelIntent.min.js
69 ms
collect
222 ms
jquery.qtip.min.js
53 ms
css.js
51 ms
core.js
51 ms
cb=gapi.loaded_0
54 ms
iga.livefyre-river.min.js
53 ms
main.js
52 ms
main.js
51 ms
jquery.viewport.min.js
52 ms
jquery.isotope.min.js
41 ms
jquery.qtip.min.css
41 ms
u.php
371 ms
match-user.html
252 ms
gif
178 ms
sync
394 ms
_Incapsula_Resource
139 ms
livefyre.js
220 ms
jquery.jscrollpane.min.js
136 ms
jquery.history.min.js
135 ms
backbone.js
140 ms
imagesloaded.min.js
138 ms
jquery.isotope-appendedFiltered.js
65 ms
Collection.js
65 ms
FeedView.js
71 ms
Content.js
71 ms
types.js
71 ms
iga.livefyre.auth.js
69 ms
pixel
60 ms
268 ms
pixel
105 ms
tap.php
102 ms
setuid
91 ms
transformers.js
106 ms
mustache.js
97 ms
iga.require.text.js
101 ms
ContentView.js
96 ms
sfp-user-match.js
115 ms
mapuid
90 ms
mapuid
26 ms
mapuid
22 ms
Tweet.js
43 ms
RSS.js
50 ms
match.sharethrough.com
47 ms
Content.html.js
21 ms
geffen.com accessibility score
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
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
geffen.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
Issues were logged in the Issues panel in Chrome Devtools
geffen.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geffen.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Geffen.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.
geffen.com
Open Graph description is not detected on the main page of Geffen. 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: