Tools & Wizards About Us
noisebreaker.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

noisebreaker.com

Silicone Ear Plugs | Custom Moulded NoiseBreaker Ear Plugs UK

Page Load Speed

6.1 sec in total

First Response

360 ms

Resources Loaded

5.5 sec

Page Rendered

236 ms

noisebreaker.com screenshot

About Website

Click here to check amazing Noise Breaker content. Otherwise, check out these important facts you probably never knew about noisebreaker.com

For 40 years, we have manufactured & distributed NoiseBreaker silicone ear plugs; our customised moulded ear plugs that are tailor-made for comfort.

Visit noisebreaker.com

Key Findings

We analyzed Noisebreaker.com page load time and found that the first response time was 360 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

noisebreaker.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value4,260 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.234

53/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

noisebreaker.com

360 ms

www.noisebreaker.com

700 ms

_css.inc.php

465 ms

_javascript.inc.php

805 ms

jquery.fancybox.css

177 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 88% of them (58 requests) were addressed to the original Noisebreaker.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Noisebreaker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 907.1 kB (58%)

Content Size

1.6 MB

After Optimization

659.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Noisebreaker.com main page is 1.6 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. 35% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 23.8 kB

  • Original 29.0 kB
  • After minification 21.2 kB
  • After compression 5.3 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. This page needs HTML code to be minified as it can gain 7.8 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.8 kB or 82% of the original size.

Image Optimization

-18%

Potential reduce by 81.3 kB

  • Original 444.5 kB
  • After minification 363.3 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, Noise Breaker needs image optimization as it can save up to 81.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 767.0 kB

  • Original 1.1 MB
  • After minification 983.3 kB
  • After compression 283.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 767.0 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 35.1 kB

  • Original 42.5 kB
  • After minification 32.5 kB
  • After compression 7.4 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. Noisebreaker.com needs all CSS files to be minified and compressed as it can save up to 35.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (20%)

Requests Now

61

After Optimization

49

  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Noise Breaker. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

noisebreaker.com

noisebreaker.com

360 ms

www.noisebreaker.com

www.noisebreaker.com

700 ms

_css.inc.php

_css.inc.php

465 ms

_javascript.inc.php

_javascript.inc.php

805 ms

jquery.fancybox.css

jquery.fancybox.css

177 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

310 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

405 ms

css

css

24 ms

three.min.js

three.min.js

1147 ms

OrbitControls.js

OrbitControls.js

584 ms

ColladaLoader.js

ColladaLoader.js

1357 ms

threejs.css

threejs.css

2118 ms

js

js

23 ms

javascript.gp

javascript.gp

176 ms

cookiecontrol.min.js

cookiecontrol.min.js

1228 ms

banner-setup.js.php

banner-setup.js.php

2149 ms

0.jpg

0.jpg

32 ms

logo.png

logo.png

169 ms

blue-trans.png

blue-trans.png

170 ms

megamenu-arrow.png

megamenu-arrow.png

173 ms

search-link-bg.png

search-link-bg.png

186 ms

grad-top-bg.png

grad-top-bg.png

190 ms

banner_3d.png

banner_3d.png

343 ms

401

401

626 ms

402

402

604 ms

403

403

674 ms

377

377

538 ms

video-overlay.png

video-overlay.png

374 ms

404

404

704 ms

405

405

747 ms

406

406

758 ms

407

407

930 ms

408

408

892 ms

409

409

929 ms

410

410

975 ms

411

411

1134 ms

412

412

1006 ms

413

413

1232 ms

414

414

1251 ms

mailing-list.png

mailing-list.png

1112 ms

phone.png

phone.png

1163 ms

fax.png

fax.png

1181 ms

email.png

email.png

1296 ms

twitter-icon.png

twitter-icon.png

1292 ms

linkedin-icon.png

linkedin-icon.png

1336 ms

ga.js

ga.js

20 ms

326

326

1364 ms

357

357

1466 ms

331

331

1433 ms

369

369

1501 ms

335

335

1644 ms

1TiHc9yag0wq3lDO9cw0viZ2oysoEQEeKwjgmXLRnTc.ttf

1TiHc9yag0wq3lDO9cw0viZ2oysoEQEeKwjgmXLRnTc.ttf

5 ms

mUangSEE-PUZJVLGz-Lt6-vvDin1pK8aKteLpeZ5c0A.ttf

mUangSEE-PUZJVLGz-Lt6-vvDin1pK8aKteLpeZ5c0A.ttf

12 ms

379

379

1686 ms

__utm.gif

__utm.gif

13 ms

339

339

1674 ms

341

341

1704 ms

343

343

1820 ms

470

470

1860 ms

363

363

1893 ms

349

349

1806 ms

351

351

1856 ms

361

361

1741 ms

474

474

1714 ms

arrow-left.png

arrow-left.png

1704 ms

arrow-right.png

arrow-right.png

1721 ms

Accessibility Review

noisebreaker.com accessibility score

62

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

noisebreaker.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

noisebreaker.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Noisebreaker.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 Noisebreaker.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.

Social Sharing Optimization

noisebreaker.com

Open Graph description is not detected on the main page of Noise Breaker. 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: