3.6 sec in total
55 ms
3.1 sec
456 ms
Welcome to seehear.live homepage info - get ready to check See Hear best content right away, or after learning these important things about seehear.live
Leading regional retailer of Professional Audio & Visual equipment including: Mics, Speakers, Mixers, Earphones, Headphones, Mounts/Stands, Studio Players/Recorders, Interfaces & Power Management. Get...
Visit seehear.liveWe analyzed Seehear.live page load time and found that the first response time was 55 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
seehear.live performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value28.1 s
0/100
25%
Value17.8 s
0/100
10%
Value8,480 ms
0/100
30%
Value0.112
86/100
15%
Value34.8 s
0/100
10%
55 ms
324 ms
39 ms
47 ms
64 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 19% of them (20 requests) were addressed to the original Seehear.live, 71% (75 requests) were made to Cdn.myshopline.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (960 ms) relates to the external source Img.myshopline.com.
Page size can be reduced by 1.4 MB (42%)
3.5 MB
2.0 MB
In fact, the total size of Seehear.live main page is 3.5 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. Only a small number of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.
Potential reduce by 1.3 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.3 MB or 79% of the original size.
Potential reduce by 87.4 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. Obviously, See Hear needs image optimization as it can save up to 87.4 kB or 42% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.9 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.
Number of requests can be reduced by 88 (86%)
102
14
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of See Hear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 89 to 1 for JavaScripts and as a result speed up the page load time.
seehear.live
55 ms
seehear.live
324 ms
reference-sdk.umd.min.js
39 ms
tune.js
47 ms
global.min.js
64 ms
index.min.js
303 ms
app-embed-block.js
47 ms
global.min.css
57 ms
index.min.css
62 ms
app-embed-block.css
74 ms
entry.js
28 ms
entry.js
37 ms
entry.js
38 ms
entry.js
38 ms
entry.js
36 ms
entry.js
36 ms
entry.js
44 ms
entry.js
52 ms
entry.js
50 ms
entry.js
50 ms
entry.js
50 ms
entry.js
49 ms
entry.js
274 ms
entry.js
53 ms
proxy-polyfill.min.js
53 ms
fbevents.js
274 ms
hdsdk-1.6.40.min.js
52 ms
js
281 ms
js
325 ms
index.min.js
280 ms
recommend-polyfills-legacy.js
46 ms
recommend-index.js
46 ms
color-palette-polyfills-legacy.js
271 ms
color-palette-index.js
271 ms
conversionBooster-polyfills-legacy.js
270 ms
conversionBooster-index.js
270 ms
currency_translate.es.js
268 ms
currency_translate.umd.js
269 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
276 ms
SHL-Logo-Black.png
320 ms
gtm.js
221 ms
General-SHL-Website-1920-x-650-px-3.png
960 ms
League%20Spartan:regular_v11.woff
960 ms
Actor:regular_v17.woff
127 ms
conversionBooster-index-legacy.js
788 ms
polyfills-legacy-1e76e182.js
69 ms
polyfills-legacy-3b658452.js
71 ms
polyfills-legacy-9e35377b.js
68 ms
polyfills-legacy-318ce9ff.js
69 ms
polyfills-legacy-d5d27785.js
68 ms
polyfills-legacy-bd6cd413.js
70 ms
polyfills-legacy-7f219720.js
70 ms
polyfills-legacy-28dfad26.js
69 ms
polyfills-legacy-3365adf2.js
71 ms
polyfills-legacy-64722980.js
70 ms
polyfills-legacy-d73de3ea.js
72 ms
polyfills-legacy-7a941f29.js
71 ms
polyfills-legacy-a1c8c456.js
71 ms
polyfills-legacy-3f1b7faa.js
71 ms
index-legacy-a9f205fb.js
726 ms
index-legacy-c52e1fe7.js
414 ms
index-legacy-9233e2a6.js
391 ms
index-legacy-d27a1678.js
354 ms
index-legacy-00944119.js
313 ms
index-legacy-257782e4.js
400 ms
index-legacy-5088a3bd.js
378 ms
index-legacy-8a5423d5.js
223 ms
index-legacy-b3ed5b0c.js
316 ms
index-legacy-73f8b49d.js
271 ms
index-legacy-9dc09f54.js
369 ms
index-legacy-9911bed7.js
330 ms
index-legacy-d964750a.js
304 ms
index-legacy-d366fe3e.js
148 ms
js
139 ms
effective_details
295 ms
simpleBootstrap-legacy-chunk-9a45771a.js
230 ms
holiday
264 ms
get
283 ms
simpleBootstrap-legacy-chunk-2b822215.js
660 ms
sales_pop
334 ms
polyfills-legacy-bundle.js
169 ms
bootstrap-legacy-chunk-939c785f.js
317 ms
bootstrap-legacy-chunk-fa1caf66.js
316 ms
cart_popup_config
315 ms
simpleBootstrap-legacy-chunk-026898f1.js
306 ms
42 ms
simpleBootstrap-legacy-chunk-cb26a41d.js
307 ms
simpleBootstrap-legacy-chunk-fef5ebcf.js
303 ms
index-legacy-bundle.js
139 ms
App-legacy-chunk-bd6d6764.js
312 ms
34 ms
simpleBootstrap-legacy-chunk-fa3618aa.js
303 ms
simpleBootstrap-legacy-chunk-d1dd0abe.js
277 ms
App-legacy-chunk-5a40e2a0.js
254 ms
default-legacy-chunk-8181b834.js
227 ms
App-legacy-chunk-310be84b.js
91 ms
App-legacy-chunk-943c25db.js
318 ms
default-legacy-chunk-719996af.js
220 ms
App-legacy-chunk-61da9b5a.js
265 ms
App-legacy-chunk-38cbbfcd.js
339 ms
get_tag_by_product
302 ms
App-legacy-chunk-7c5d52a3.js
690 ms
activities
266 ms
default-legacy-chunk-94266150.js
11 ms
index-legacy-chunk-1bd0f3d9.js
5 ms
global-legacy-chunk-bedf97ff.js
258 ms
seehear.live 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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
seehear.live 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
Missing source maps for large first-party JavaScript
seehear.live 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 doesn't use 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 Seehear.live 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 Seehear.live 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.
seehear.live
Open Graph data is detected on the main page of See Hear. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: