3.1 sec in total
492 ms
2 sec
636 ms
Click here to check amazing Whale content. Otherwise, check out these important facts you probably never knew about whale.re
Smart links for music marketing and podcast promotion. From your first single to your first world tour, Linkfire simplifies music and podcast promotion every step of the way. Trusted by major labels a...
Visit whale.reWe analyzed Whale.re page load time and found that the first response time was 492 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
whale.re performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.7 s
17/100
25%
Value6.0 s
46/100
10%
Value790 ms
37/100
30%
Value0.214
58/100
15%
Value7.9 s
44/100
10%
492 ms
151 ms
268 ms
370 ms
383 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whale.re, 9% (3 requests) were made to Cdn.cookielaw.org and 6% (2 requests) were made to 25446013.fs1.hubspotusercontent-eu1.net. The less responsive or slowest element that took the longest time to load (733 ms) relates to the external source Js-eu1.hscollectedforms.net.
Page size can be reduced by 140.9 kB (33%)
431.0 kB
290.1 kB
In fact, the total size of Whale.re main page is 431.0 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. 45% of websites need less resources to load. Javascripts take 248.9 kB which makes up the majority of the site volume.
Potential reduce by 126.8 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 126.8 kB or 86% of the original size.
Potential reduce by 0 B
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. Whale images are well optimized though.
Potential reduce by 7.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 6.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. Whale.re needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 23% of the original size.
Number of requests can be reduced by 24 (77%)
31
7
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whale. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.linkfire.com
492 ms
pwr.min.css
151 ms
pwr-burger.min.css
268 ms
scroll-shadow.min.css
370 ms
module_50162273254_CTA_Section_2022_Custom.min.css
383 ms
otSDKStub.js
39 ms
jquery-1.11.2.js
418 ms
embed.js
62 ms
pwr.min.js
471 ms
child.min.js
369 ms
project.js
471 ms
pwr-burger.min.js
476 ms
scroll-shadow.min.js
486 ms
project.js
483 ms
Typewriter.min.js
513 ms
pwr-heights.min.js
618 ms
_swiper-bundle.min.js
627 ms
pwr-swiper.min.js
619 ms
25446013.js
468 ms
index.js
619 ms
js.cookie.js
639 ms
6730c662-ee4e-4224-b51d-0768adc92afe.json
94 ms
gtm.js
157 ms
stat.js
120 ms
Linkfire%20smart%20links%20home%20page%20hero.png
549 ms
linkfire-logo-dark.svg
273 ms
arrow-right-black.svg
645 ms
regular.woff
355 ms
500.woff
390 ms
700.woff
565 ms
location
59 ms
25446013.js
572 ms
collectedforms.js
733 ms
banner.js
573 ms
otBannerSdk.js
50 ms
whale.re 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.
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
whale.re 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
whale.re 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
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 Whale.re 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 Whale.re 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.
whale.re
Open Graph data is detected on the main page of Whale. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: