Tools & Wizards About Us
nahrmannbass.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

nahrmannbass.com

Nahrmann Bass Shop

Page Load Speed

1.8 sec in total

First Response

113 ms

Resources Loaded

1.3 sec

Page Rendered

408 ms

nahrmannbass.com screenshot

About Website

Welcome to nahrmannbass.com homepage info - get ready to check Nahrmann Bass best content right away, or after learning these important things about nahrmannbass.com

Visit nahrmannbass.com

Key Findings

We analyzed Nahrmannbass.com page load time and found that the first response time was 113 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

nahrmannbass.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.117

85/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

www.nahrmannbass.com

113 ms

wU8dthzsb2FJ-ZKXVGOuH9Itix3Fiw0W0MBqepKXIZJfeCtIfFHN4UJLFRbh52jhWDjkjRJuZQqowAFRFeBcwhBcwcJuFe9ajy7iMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0dAB0ZeBk-AtlSeBkShoTSfuti29tO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CdeNRjAUGdaFXOeuydcsySc80OWgyS1F0-WMlpYbu5foDSWmyScmDSeBRZPoRdhXCdcBGScuydcoKjWFDOcFzdPUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80Zko0ZWbCiaiaOcBDOcu8OYiaikoljAoqjW4TdKu3jW4Ddc83OWyXFQ60SaBujW48Sagyjh90jhNlOYiaiko0jAykdAB0dc4ySaw0jhNlOYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJ6U3ScNt-AuyOAozicIK2cUXjkuKdhszdcqlwQSuH6qJtKGbMg62JMJ7fbKzMsMMeMb6MKGHfO2IMsMMeM96MKG4fJCgIMMjgkMfH6qJtkGbMg6FJMJ7fbK3MsMMeMt6MKG4fJ3gIMMjIPMfH6qJxkCbMs6IJMJ7fbRrHUMgeMt6MTMgy7KtcMj.js

60 ms

legacy.js

66 ms

modern.js

69 ms

extract-css-runtime-c4e90a63935fb6c45c9d-min.en-US.js

66 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Nahrmannbass.com, 44% (16 requests) were made to Use.typekit.net and 25% (9 requests) were made to Assets.squarespace.com. The less responsive or slowest element that took the longest time to load (574 ms) relates to the external source Static1.squarespace.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.4 kB (7%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 128.0 kB

  • Original 146.2 kB
  • After minification 137.3 kB
  • After compression 18.2 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 128.0 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 1.9 kB

  • Original 854.7 kB
  • After minification 852.7 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. Nahrmann Bass images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 6.4 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 999.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.

CSS Optimization

-1%

Potential reduce by 78 B

  • Original 9.9 kB
  • After minification 9.9 kB
  • After compression 9.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. Nahrmannbass.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (53%)

Requests Now

19

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.nahrmannbass.com

www.nahrmannbass.com

113 ms

wU8dthzsb2FJ-ZKXVGOuH9Itix3Fiw0W0MBqepKXIZJfeCtIfFHN4UJLFRbh52jhWDjkjRJuZQqowAFRFeBcwhBcwcJuFe9ajy7iMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0dAB0ZeBk-AtlSeBkShoTSfuti29tO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CdeNRjAUGdaFXOeuydcsySc80OWgyS1F0-WMlpYbu5foDSWmyScmDSeBRZPoRdhXCdcBGScuydcoKjWFDOcFzdPUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80Zko0ZWbCiaiaOcBDOcu8OYiaikoljAoqjW4TdKu3jW4Ddc83OWyXFQ60SaBujW48Sagyjh90jhNlOYiaiko0jAykdAB0dc4ySaw0jhNlOYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJ6U3ScNt-AuyOAozicIK2cUXjkuKdhszdcqlwQSuH6qJtKGbMg62JMJ7fbKzMsMMeMb6MKGHfO2IMsMMeM96MKG4fJCgIMMjgkMfH6qJtkGbMg6FJMJ7fbK3MsMMeMt6MKG4fJ3gIMMjIPMfH6qJxkCbMs6IJMJ7fbRrHUMgeMt6MTMgy7KtcMj.js

wU8dthzsb2FJ-ZKXVGOuH9Itix3Fiw0W0MBqepKXIZJfeCtIfFHN4UJLFRbh52jhWDjkjRJuZQqowAFRFeBcwhBcwcJuFe9ajy7iMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0dAB0ZeBk-AtlSeBkShoTSfuti29tO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CdeNRjAUGdaFXOeuydcsySc80OWgyS1F0-WMlpYbu5foDSWmyScmDSeBRZPoRdhXCdcBGScuydcoKjWFDOcFzdPUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80Zko0ZWbCiaiaOcBDOcu8OYiaikoljAoqjW4TdKu3jW4Ddc83OWyXFQ60SaBujW48Sagyjh90jhNlOYiaiko0jAykdAB0dc4ySaw0jhNlOYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJ6U3ScNt-AuyOAozicIK2cUXjkuKdhszdcqlwQSuH6qJtKGbMg62JMJ7fbKzMsMMeMb6MKGHfO2IMsMMeM96MKG4fJCgIMMjgkMfH6qJtkGbMg6FJMJ7fbK3MsMMeMt6MKG4fJ3gIMMjIPMfH6qJxkCbMs6IJMJ7fbRrHUMgeMt6MTMgy7KtcMj.js

60 ms

legacy.js

legacy.js

66 ms

modern.js

modern.js

69 ms

extract-css-runtime-c4e90a63935fb6c45c9d-min.en-US.js

extract-css-runtime-c4e90a63935fb6c45c9d-min.en-US.js

66 ms

extract-css-moment-js-vendor-675f9459672cf966ca51-min.en-US.js

extract-css-moment-js-vendor-675f9459672cf966ca51-min.en-US.js

92 ms

cldr-resource-pack-a682f7ad337741eb05d6-min.en-US.js

cldr-resource-pack-a682f7ad337741eb05d6-min.en-US.js

70 ms

common-vendors-stable-f9df4447a2af25df5875-min.en-US.js

common-vendors-stable-f9df4447a2af25df5875-min.en-US.js

70 ms

common-vendors-e9765446cecc0854c8fc-min.en-US.js

common-vendors-e9765446cecc0854c8fc-min.en-US.js

71 ms

common-1f9ce3a07207b3dbcdd8-min.en-US.js

common-1f9ce3a07207b3dbcdd8-min.en-US.js

94 ms

performance-c8955e48a6ba99b14af2-min.en-US.js

performance-c8955e48a6ba99b14af2-min.en-US.js

72 ms

site.css

site.css

574 ms

static.css

static.css

66 ms

site-bundle.50b4de10587967c63a6c38385a95664b.js

site-bundle.50b4de10587967c63a6c38385a95664b.js

60 ms

Logo_Font%28NewUpdate%29.png

Logo_Font%28NewUpdate%29.png

205 ms

Volker_Showroom.jpg

Volker_Showroom.jpg

428 ms

Restoration_Home.jpg

Restoration_Home.jpg

418 ms

Collections_Home.jpg

Collections_Home.jpg

369 ms

Bass%2BTest.jpg

Bass%2BTest.jpg

404 ms

Workshop.jpg

Workshop.jpg

384 ms

ZapfChancery-Italic.otf

ZapfChancery-Italic.otf

476 ms

i

i

32 ms

i

i

33 ms

i

i

13 ms

i

i

44 ms

i

i

33 ms

i

i

23 ms

i

i

32 ms

i

i

42 ms

i

i

43 ms

i

i

46 ms

i

i

65 ms

i

i

56 ms

i

i

134 ms

i

i

65 ms

i

i

74 ms

Accessibility Review

nahrmannbass.com accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

nahrmannbass.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

nahrmannbass.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

nahrmannbass.com

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