Tools & Wizards About Us
tavern.no screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    65% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 85% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

tavern.no

Tavern på Sverresborg - Hjemmesiden tavern.no innehas og driftes av Oscar AS. - Restaurant og selskapslokale i Trondheim

Page Load Speed

1.6 sec in total

First Response

218 ms

Resources Loaded

1.1 sec

Page Rendered

311 ms

tavern.no screenshot

About Website

Visit tavern.no now to see the best up-to-date Tavern content and also check out these interesting facts you probably never knew about tavern.no

Tavern på Sverresborg. Tradisjonell norsk mat. Hverdagsmat. Restaurant og selsskapslokaler i Trondheim.

Visit tavern.no

Key Findings

We analyzed Tavern.no page load time and found that the first response time was 218 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

tavern.no performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.1 s

51/100

10%

Network Requests Diagram

tavern.no

218 ms

www.tavern.no

259 ms

bootstrap.css

199 ms

color-styles.css

208 ms

ui-elements.css

208 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 58% of them (18 requests) were addressed to the original Tavern.no, 29% (9 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (471 ms) belongs to the original domain Tavern.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.6 kB (10%)

Content Size

183.3 kB

After Optimization

164.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tavern.no main page is 183.3 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 86.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 11.0 kB

  • Original 14.4 kB
  • After minification 10.9 kB
  • After compression 3.4 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 3.5 kB, which is 24% 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 11.0 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 420 B

  • Original 40.3 kB
  • After minification 39.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. Tavern images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.8 kB

  • Original 86.2 kB
  • After minification 86.2 kB
  • After compression 84.4 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

-13%

Potential reduce by 5.3 kB

  • Original 42.4 kB
  • After minification 42.4 kB
  • After compression 37.1 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. Tavern.no needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (84%)

Requests Now

19

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tavern.no

tavern.no

218 ms

www.tavern.no

www.tavern.no

259 ms

bootstrap.css

bootstrap.css

199 ms

color-styles.css

color-styles.css

208 ms

ui-elements.css

ui-elements.css

208 ms

custom.css

custom.css

212 ms

fresco.css

fresco.css

208 ms

tavern.css

tavern.css

195 ms

animate.css

animate.css

289 ms

font-awesome.min.css

font-awesome.min.css

294 ms

css

css

19 ms

css

css

35 ms

jquery.min.js

jquery.min.js

41 ms

bootstrap.min.js

bootstrap.min.js

285 ms

scrolltopcontrol.js

scrolltopcontrol.js

288 ms

jquery.sticky.js

jquery.sticky.js

282 ms

grids.js

grids.js

328 ms

custom.js

custom.js

392 ms

fresco.js

fresco.js

393 ms

1-Desktop2-copy.jpg

1-Desktop2-copy.jpg

471 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

62 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

62 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

63 ms

analytics.js

analytics.js

37 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

101 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

39 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

39 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

40 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

40 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

41 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

38 ms

Accessibility Review

tavern.no accessibility score

94

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

tavern.no best practices score

83

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

SEO Factors

tavern.no SEO score

77

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

High

robots.txt is not valid

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

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tavern.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Tavern.no 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

tavern.no

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