Tools & Wizards About Us
weareamsterdam.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

weareamsterdam.com

Home - We Are Amsterdam

Page Load Speed

2.4 sec in total

First Response

147 ms

Resources Loaded

1.2 sec

Page Rendered

1.1 sec

weareamsterdam.com screenshot

About Website

Click here to check amazing Weare Amsterdam content. Otherwise, check out these important facts you probably never knew about weareamsterdam.com

Check out our large offer of Amsterdam tours & activities. Upgrade your visit to this beautiful city. We offer the best activities in town including our free Whatsapp assistent

Visit weareamsterdam.com

Key Findings

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

Performance Metrics

weareamsterdam.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

weareamsterdam.com

147 ms

weareamsterdam.com

215 ms

styles.css

115 ms

style.min.css

123 ms

style.min.css

119 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 80% of them (66 requests) were addressed to the original Weareamsterdam.com, 18% (15 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (664 ms) belongs to the original domain Weareamsterdam.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.0 kB (6%)

Content Size

3.9 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weareamsterdam.com main page is 3.9 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. 80% 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 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 155.3 kB

  • Original 192.2 kB
  • After minification 191.9 kB
  • After compression 36.9 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 155.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 82.3 kB

  • Original 3.5 MB
  • After minification 3.4 MB

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. Weare Amsterdam images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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 1.3 kB

  • Original 234.5 kB
  • After minification 234.5 kB
  • After compression 233.2 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. Weareamsterdam.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (48%)

Requests Now

62

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weareamsterdam.com

weareamsterdam.com

147 ms

weareamsterdam.com

weareamsterdam.com

215 ms

styles.css

styles.css

115 ms

style.min.css

style.min.css

123 ms

style.min.css

style.min.css

119 ms

comments.css

comments.css

127 ms

style.min.css

style.min.css

131 ms

theme.min.css

theme.min.css

133 ms

elementor-icons.min.css

elementor-icons.min.css

224 ms

frontend.min.css

frontend.min.css

234 ms

swiper.min.css

swiper.min.css

241 ms

post-8.css

post-8.css

241 ms

frontend.min.css

frontend.min.css

259 ms

uael-frontend.min.css

uael-frontend.min.css

270 ms

wpforms-full.min.css

wpforms-full.min.css

335 ms

global.css

global.css

351 ms

post-362.css

post-362.css

348 ms

post-446.css

post-446.css

353 ms

post-201.css

post-201.css

370 ms

post-13079.css

post-13079.css

380 ms

post-995.css

post-995.css

441 ms

font-awesome.min.css

font-awesome.min.css

457 ms

wp-review.css

wp-review.css

455 ms

default.css

default.css

460 ms

post-10254.css

post-10254.css

488 ms

fontawesome.min.css

fontawesome.min.css

503 ms

brands.min.css

brands.min.css

566 ms

solid.min.css

solid.min.css

561 ms

regular.min.css

regular.min.css

569 ms

css

css

34 ms

email-decode.min.js

email-decode.min.js

461 ms

animations.min.css

animations.min.css

658 ms

post-7985.css

post-7985.css

659 ms

post-7577.css

post-7577.css

664 ms

waa-logo-svg-1.svg

waa-logo-svg-1.svg

67 ms

united-kingdom.svg

united-kingdom.svg

64 ms

israel.svg

israel.svg

65 ms

italy.svg

italy.svg

67 ms

amsterdam-5752346-scaled.jpeg

amsterdam-5752346-scaled.jpeg

70 ms

Google-review-without-googe.png

Google-review-without-googe.png

71 ms

google2.0.0-1024x394.jpg

google2.0.0-1024x394.jpg

72 ms

Google-review-with-Google.png

Google-review-with-Google.png

71 ms

shutterstock_1663013188-1024x683.jpg

shutterstock_1663013188-1024x683.jpg

78 ms

shutterstock_565003417-1024x683.jpg

shutterstock_565003417-1024x683.jpg

72 ms

holding-hands-1149411_1920-1024x683.jpg

holding-hands-1149411_1920-1024x683.jpg

73 ms

business-suit-690048_1920-1024x385.jpg

business-suit-690048_1920-1024x385.jpg

72 ms

DSC09012edit4x5-819x1024-1.jpg

DSC09012edit4x5-819x1024-1.jpg

72 ms

kats-weil-CLD1i8hp008-unsplash-1024x684.jpg

kats-weil-CLD1i8hp008-unsplash-1024x684.jpg

73 ms

DSC1920-scaled-2.jpg

DSC1920-scaled-2.jpg

76 ms

DSC1510-2048x1365.jpg

DSC1510-2048x1365.jpg

74 ms

bitterballen-amseterdamjpg.jpg

bitterballen-amseterdamjpg.jpg

77 ms

canal-2681853_1920-1024x682.jpg

canal-2681853_1920-1024x682.jpg

78 ms

auto-1291491_1920-e1601043701557-1024x683.jpg

auto-1291491_1920-e1601043701557-1024x683.jpg

74 ms

grachtenpanden-2-scaled.jpg

grachtenpanden-2-scaled.jpg

82 ms

facebook_icon_130940.png

facebook_icon_130940.png

83 ms

ig-logo-email.png

ig-logo-email.png

93 ms

whatsapp-icon-1024x1024.png

whatsapp-icon-1024x1024.png

88 ms

021-ideal.svg

021-ideal.svg

85 ms

030-paypal.svg

030-paypal.svg

88 ms

025-mastercard.svg

025-mastercard.svg

84 ms

040-visa.svg

040-visa.svg

86 ms

002-american-express.svg

002-american-express.svg

89 ms

google2.0.0.jpg

google2.0.0.jpg

91 ms

waas.png

waas.png

91 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

40 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

40 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

128 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

128 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

130 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

130 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

131 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

131 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

132 ms

fa-solid-900.woff

fa-solid-900.woff

13 ms

fa-regular-400.woff

fa-regular-400.woff

126 ms

fa-brands-400.woff

fa-brands-400.woff

37 ms

Accessibility Review

weareamsterdam.com 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

weareamsterdam.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

SEO Factors

weareamsterdam.com SEO score

89

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

High

Tap targets are not sized appropriately

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 Weareamsterdam.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 Weareamsterdam.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

weareamsterdam.com

Open Graph data is detected on the main page of Weare Amsterdam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: