3.1 sec in total
302 ms
2 sec
796 ms
Click here to check amazing Nimb content for Denmark. Otherwise, check out these important facts you probably never knew about nimb.dk
I Tivolis mauriske madpalads lever familien Nimbs traditionsrige navn og ånd: eksklusiv gourmetoplevelse & folkelig hverdagsluksus, bar og brunch, hotel og terrasse: Over alt dog hersker den gode smag...
Visit nimb.dkWe analyzed Nimb.dk page load time and found that the first response time was 302 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
nimb.dk performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value24.4 s
0/100
25%
Value20.1 s
0/100
10%
Value26,610 ms
0/100
30%
Value1
2/100
15%
Value36.5 s
0/100
10%
302 ms
411 ms
49 ms
175 ms
334 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 27% of them (15 requests) were addressed to the original Nimb.dk, 36% (20 requests) were made to Dg2kj7uuq7g1w.cloudfront.net and 11% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (783 ms) belongs to the original domain Nimb.dk.
Page size can be reduced by 437.9 kB (9%)
4.7 MB
4.3 MB
In fact, the total size of Nimb.dk main page is 4.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 52.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 52.2 kB or 81% of the original size.
Potential reduce by 309.2 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. Nimb images are well optimized though.
Potential reduce by 7.0 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 7.0 kB or 13% of the original size.
Potential reduce by 69.5 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. Nimb.dk needs all CSS files to be minified and compressed as it can save up to 69.5 kB or 30% of the original size.
Number of requests can be reduced by 15 (33%)
46
31
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nimb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
nimb.dk
302 ms
www.nimb.dk
411 ms
uc.js
49 ms
nimbv2-main-style-eea4f83c2a2c547453f076a6b732efd3.css
175 ms
react-nimb-style-0e5310d495e0c919b9c6a4141afc78d0.css
334 ms
css
48 ms
fonts.css
248 ms
launch-ENfe976dc39c8843b781fa679802a16dce.min.js
54 ms
nimbv2-vendor-ab962fba4aa73355d1349ec0244c717d.js
663 ms
nimbv2-main-a1f9cbc3236467ae50b9edbf427072a2.js
350 ms
react-nimb-256e01a42254f5efee91a40d49ca1a89.js
783 ms
iframe_api
64 ms
gtm.js
70 ms
52296AAED650B94D7.css
258 ms
nimb-black.svg
62 ms
icon-facebook.svg
116 ms
icon-instagram.svg
114 ms
icon-empty.svg
114 ms
id
78 ms
AppMeasurement.min.js
28 ms
fbevents.js
42 ms
hotel_price_widget.js
181 ms
EJRVQgYoZZY2vCFuvAFWzro.ttf
62 ms
EJRSQgYoZZY2vCFuvAnt66qSVy4.ttf
63 ms
u-440qyriQwlOrhSvowK_l5-fCZJ.ttf
63 ms
nimb.ttf
179 ms
identity.js
25 ms
375195230211705
125 ms
dest5.html
45 ms
ibs:dpid=411&dpuuid=YzXc3AAAAFvgoAN-
80 ms
www-widgetapi.js
161 ms
nimb-black2.svg
152 ms
Nimb_Pattern_Small.svg
117 ms
Nimb_Pattern_Level_1.svg
121 ms
icon-dropdown.svg
109 ms
nimb_logo_white_shadow.png
70 ms
bar_small_white.svg
102 ms
nimb-brasserie-white.svg
99 ms
cakenhagen_small_white.svg
100 ms
gemysehvid.svg
79 ms
frunimb-white.svg
81 ms
nimb_roof_logo_white.svg
103 ms
nimbsummerfrontpage.jpg
136 ms
nimb_bar_500x500.jpg
131 ms
nimb_brasserie_500x500.jpg
106 ms
cakenhagen_teaserbox_500x500.jpg
104 ms
gemyse_teaser_500x500.jpg
128 ms
fru_nimb_500x500.jpg
105 ms
nimb_roof_500x500.jpg
131 ms
events_nimb_nights_choro-vivo_1220x910.png
132 ms
nimb_bar_afternoon_tea_910x610.jpg
127 ms
nimb_hotel_intro_sommer_1220x920.jpg
136 ms
nimb_small_gray.svg
132 ms
6xKhdSpbNNCT-sWPCms.ttf
21 ms
EJRTQgYoZZY2vCFuvAFT_r21dw.ttf
27 ms
EJRQQgYoZZY2vCFuvAFT9gaQZynfpQ.ttf
29 ms
nimb.dk accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[role] values are not valid
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
Image elements do not have [alt] attributes
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
nimb.dk 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
nimb.dk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nimb.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish 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 Nimb.dk 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.
nimb.dk
Open Graph data is detected on the main page of Nimb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: