Catchpoint named a Leader in the first Gartner® Magic Quadrant™ for Digital Experience Monitoring. Read the report

Menu:

Save Test Results with a Free Account Sign Up & Save Test Result

Webpage Performance Test Result

Screenshot

View:

Tools:

Export

Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. Overall scoring color key: (0-49 50-89 90-100).

For scripted tests, Lighthouse report will only be available on the final step.

Did you know? Lighthouse runs in Chrome and provides a great complementary analysis alongside the many browsers, devices, and locations WebPageTest offers. To see how this site performs in more environments: Start a new test

Performance 99

Lighthouse Metrics

Values are estimated and may vary.

The performance score is calculated directly from these metrics. See calculator.

First Contentful Paint Speed Index Largest Contentful Paint Time to Interactive Total Blocking Time Cumulative Layout Shift
0.4s 0.5s 1.0s 0.8s 0ms 0.004

Aiming to improve? check out our Opportunities & Experiments for suggestions and run No-Code Experiments to see how changes impact this site!

Filmstrip

Show audits relevant to metrics: ALL FCP LCP TBT CLS

View Tree Map

Opportunities (5)

  1. Initial server response time was short

    Root document took 60 ms

    Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

    URL Time Spent (ms)
    https://bppresents.nl/ 65

  2. Reduce unused JavaScript

    Potential savings of 21 KiB

    Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

    URL Transfer Size (bytes) Potential Savings (bytes)
    https://bppresents.nl/assets/js/vendors.js 30330 21212

  3. Properly size images

    Potential savings of 237 KiB

    Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

    URL Resource Size (bytes) Potential Savings (bytes)
    https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-1920x.jpg 270114 242812

  4. Defer offscreen images

    View Experiment!

    Potential savings of 133 KiB

    Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

    URL Resource Size (bytes) Potential Savings (bytes)
    https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-1920x.png 136572 136572

  5. Serve images in next-gen formats

    Potential savings of 169 KiB

    Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

    URL Resource Size (bytes) Potential Savings (bytes)
    https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-1920x.jpg 270114 131561
    https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-1920x.png 136572 41190

Diagnostics (10)

  1. Avoid chaining critical requests

    4 chains found

    The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.

    1. https://bppresents.nl/ 12kb
      1. https://bppresents.nl/assets/css/app.css 1kb
        1. https://bppresents.nl/assets/fonts/FavoritStd-MediumItalicIntense20.otf 123kb
        2. https://bppresents.nl/assets/fonts/FavoritStd-Regular.otf 107kb
      2. https://bppresents.nl/assets/js/vendors.js 30kb
      3. https://bppresents.nl/assets/js/app.js 0kb

  2. Ensure text remains visible during webfont load

    View Experiment!

    Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

    URL Potential Savings
    https://bppresents.nl/assets/fonts/FavoritStd-MediumItalicIntense20.otf 257
    https://bppresents.nl/assets/fonts/FavoritStd-Regular.otf 396

  3. Largest Contentful Paint element

    970 ms

    This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element

  4. Avoids enormous network payloads

    Total size was 672 KiB

    Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

    URL Transfer Size (bytes)
    https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-1920x.jpg 270355
    https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-1920x.png 136741
    https://bppresents.nl/assets/fonts/FavoritStd-MediumItalicIntense20.otf 125999
    https://bppresents.nl/assets/fonts/FavoritStd-Regular.otf 109916
    https://bppresents.nl/assets/js/vendors.js 30429
    https://bppresents.nl/ 12141
    https://bppresents.nl/assets/css/app.css 1528
    https://bppresents.nl/assets/images/favicon/favicon-32x32.png 715
    https://bppresents.nl/assets/images/favicon/site.webmanifest 456
    https://bppresents.nl/assets/js/app.js 291

  5. Avoid long main-thread tasks

    1 long task found

    Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

    URL Start Time Duration
    https://bppresents.nl/ 316 51

  6. JavaScript execution time

    0.0 s

    Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

    URL Total CPU Time Script Evaluation Script Parse
    https://bppresents.nl/ 72 1 0
    Unattributable 67 1 0

  7. Minimizes main-thread work

    0.2 s

    Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

    Category Time Spent
    Other 73
    Style & Layout 55
    Script Evaluation 11
    Parse HTML & CSS 7
    Rendering 5
    Script Parsing & Compilation 2

  8. Avoids an excessive DOM size

    279 elements

    A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

    Statistic Element Value
    Total DOM Elements
    Maximum DOM Depth span.nav-module__toggle > svg > defs > style
    Maximum Child Elements div.layer > div.grid-container > section.module-cell > p

  9. Avoid large layout shifts

    3 elements found

    These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

    Element Layout shift impact
    main.site-container > div.layer > div.grid-container > div.module-cell 0
    main.site-container > div.layer > div.grid-container > section.module-cell 0
    main.site-container > div.layer > div.grid-container > section.module-cell 0

  10. Serve static assets with an efficient cache policy

    7 resources found

    A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

    URL Cache TTL Transfer Size (bytes)
    https://bppresents.nl/assets/fonts/FavoritStd-MediumItalicIntense20.otf 0 125999
    https://bppresents.nl/assets/fonts/FavoritStd-Regular.otf 0 109916
    https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-1920x.jpg 604800000 270355
    https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-1920x.png 604800000 136741
    https://bppresents.nl/assets/js/vendors.js 604800000 30429
    https://bppresents.nl/assets/css/app.css 604800000 1528
    https://bppresents.nl/assets/js/app.js 604800000 291

Passed Audits (24)

  1. Eliminate render-blocking resources

    Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

  2. Avoid multiple page redirects

    Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

  3. Enable text compression

    Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

  4. Preconnect to required origins

    Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.

  5. Preload key requests

    Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn how to preload key requests.

  6. Minify JavaScript

    Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

  7. Minify CSS

    Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

  8. Reduce unused CSS

    Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

  9. Preload Largest Contentful Paint image

    If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.

  10. Use video formats for animated content

    Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats

  11. Largest Contentful Paint image was not lazily loaded

    Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.

    Element
    div.grid-container > div.module-cell > figure > img

  12. Minimize third-party usage

    Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

  13. Lazy load third-party resources with facades

    Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.

  14. Remove duplicate modules in JavaScript bundles

    Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

  15. Avoid serving legacy JavaScript to modern browsers

    Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript

  16. Has a <meta name="viewport"> tag with width or initial-scale

    A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

  17. Avoid non-composited animations

    Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animations

  18. Image elements have explicit width and height

    Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

  19. Efficiently encode images

    Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

  20. Use HTTP/2

    HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.

  21. User Timing marks and measures

    Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.

  22. Uses passive listeners to improve scrolling performance

    Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

  23. Avoids document.write()

    For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().

  24. Page didn't prevent back/forward cache restoration

    Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Accessibility 75

Best practices (1)

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

    View Experiment!

    Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

    Failing Elements
    head > meta Fix any of the following:
    maximum-scale on <meta> tag disables zooming on mobile devices

Names and labels (1)

  1. Buttons do not have an accessible name

    When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

    Failing Elements
    div.body-inner > main.site-container > nav.nav-module > button.nav-module__button Fix any of the following:
    Element does not have inner text that is visible to screen readers
    aria-label attribute does not exist or is empty
    aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
    Element has no title attribute
    Element's default semantics were not overridden with role="none" or role="presentation"

Additional Items to Check Manually (10)

  1. Interactive controls are keyboard focusable

    Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.

  2. Interactive elements indicate their purpose and state

    Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.

  3. The page has a logical tab order

    Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.

  4. Visual order on the page follows DOM order

    DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.

  5. User focus is not accidentally trapped in a region

    A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.

  6. The user's focus is directed to new content added to the page

    If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.

  7. HTML5 landmark elements are used to improve navigation

    Landmark elements (`<main>`, `<nav>`, etc.) are used to improve the keyboard navigation of the page for assistive technology.

  8. Offscreen content is hidden from assistive technology

    Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.

  9. Custom controls have associated labels

    Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.

  10. Custom controls have ARIA roles

    Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.

Passed Audits (9)

  1. [aria-hidden="true"] is not present on the document <body>

    Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.

  2. Background and foreground colors have a sufficient contrast ratio

    Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

  3. Document has a <title> element

    The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

  4. Heading elements appear in a sequentially-descending order

    Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

  5. <html> element has a [lang] attribute

    If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.

  6. <html> element has a valid value for its [lang] attribute

    Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.

  7. Image elements have [alt] attributes

    Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.

  8. Image elements do not have [alt] attributes that are redundant text.

    Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.

  9. Links have a discernible name

    Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Not Applicable (43)

  1. [accesskey] values are unique

    Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.

  2. [aria-*] attributes match their roles

    Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.

  3. Values assigned to role="" are valid ARIA roles.

    ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.

  4. button, link, and menuitem elements have accessible names

    When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

  5. Elements with role="dialog" or role="alertdialog" have accessible names.

    ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

  6. [aria-hidden="true"] elements do not contain focusable descendents

    Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.

  7. ARIA input fields have accessible names

    When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

  8. ARIA meter elements have accessible names

    When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.

  9. ARIA progressbar elements have accessible names

    When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.

  10. [role]s have all required [aria-*] attributes

    Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

  11. Elements with an ARIA [role] that require children to contain a specific [role] have all required children.

    Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

  12. [role]s are contained by their required parent element

    Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

  13. [role] values are valid

    ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

  14. Elements with the role=text attribute do not have focusable descendents.

    Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.

  15. ARIA toggle fields have accessible names

    When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

  16. ARIA tooltip elements have accessible names

    When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.

  17. ARIA treeitem elements have accessible names

    When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.

  18. [aria-*] attributes have valid values

    Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

  19. [aria-*] attributes are valid and not misspelled

    Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

  20. The page contains a heading, skip link, or landmark region

    Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.

  21. <dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

    When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

  22. Definition list items are wrapped in <dl> elements

    Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.

  23. [id] attributes on active, focusable elements are unique

    All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn how to fix duplicate ids.

  24. ARIA IDs are unique

    The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.

  25. No form fields have multiple labels

    Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.

  26. <frame> or <iframe> elements have a title

    Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

  27. <html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.

    If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.

  28. Input buttons have discernible text.

    Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

  29. <input type="image"> elements have [alt] text

    When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.

  30. Form elements have associated labels

    Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

  31. Links are distinguishable without relying on color.

    Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

  32. Lists contain only <li> elements and script supporting elements (<script> and <template>).

    Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

  33. List items (<li>) are contained within <ul>, <ol> or <menu> parent elements

    Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.

  34. The document does not use <meta http-equiv="refresh">

    Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

  35. <object> elements have alternate text

    Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.

  36. Select elements have associated label elements.

    Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.

  37. Skip links are focusable.

    Including a skip link can help users skip to the main content to save time. Learn more about skip links.

  38. No element has a [tabindex] value greater than 0

    A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.

  39. Tables have different content in the summary attribute and <caption>.

    The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.

  40. Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

    Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.

  41. <th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

    Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.

  42. [lang] attributes have a valid value

    Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.

  43. <video> elements contain a <track> element with [kind="captions"]

    When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.

Best Practices 100

Trust and Safety (1)

  1. Ensure CSP is effective against XSS attacks

    A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS

    Description Directive Severity
    `script-src` directive is missing. This can allow the execution of unsafe scripts. script-src High
    Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can. object-src High

General (1)

  1. Detected JavaScript libraries

    All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

    Name Version
    jQuery 3.5.1

Passed Audits (14)

  1. Uses HTTPS

    All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

  2. Avoids requesting the geolocation permission on page load

    Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.

  3. Avoids requesting the notification permission on page load

    Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.

  4. Allows users to paste into input fields

    Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.

  5. Displays images with correct aspect ratio

    Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

  6. Serves images with appropriate resolution

    Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

  7. Page has the HTML doctype

    Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

  8. Properly defines charset

    A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

  9. Avoids unload event listeners

    The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners

  10. Avoids deprecated APIs

    Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

  11. Avoids third-party cookies

    Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.

  12. No browser errors logged to the console

    Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

  13. Page has valid source maps

    Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

  14. No issues in the Issues panel in Chrome Devtools

    Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Not Applicable (1)

  1. Fonts with font-display: optional are preloaded

    Preload optional fonts so first-time visitors may use them. Learn more about preloading fonts

SEO 91

Crawling and Indexing (1)

  1. robots.txt is not valid

    289 errors found

    If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

    Line # Content Error
    1 <!DOCTYPE html> Syntax not understood
    2 <html lang="en"> Syntax not understood
    3 <head> Syntax not understood
    4 <meta charset="utf-8"> Syntax not understood
    5 <meta http-equiv="content-type" content="text/html; charset=utf-8"> Syntax not understood
    6 <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, minimum-scale=1"> Syntax not understood
    8 <title>Bureau Postjesweg Presents: Afscheid Bureau Postjesweg</title> Unknown directive
    9 <meta property='og:title' content="Bureau Postjesweg Presents: Afscheid Bureau Postjesweg" /> Unknown directive
    10 <meta name="description" content="Something about bp..."> Syntax not understood
    11 <meta property='og:site_name' content='Bureau Postjesweg' /> Unknown directive
    12 <meta property="og:image" content="https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2.jpg" /> Unknown directive
    13 <meta property="og:type" content="website" /> Unknown directive
    14 <meta property='og:url' content="https://bppresents.nl" /> Unknown directive
    17 <!-- Syntax not understood
    20 Concept, Design and Development Syntax not understood
    21 Amir Avraham Syntax not understood
    24 --> Syntax not understood
    26 <link href="https://bppresents.nl/assets/css/app.css" rel="stylesheet"> Unknown directive
    27 <link rel="apple-touch-icon" sizes="180x180" href="https://bppresents.nl/assets/images/favicon/apple-touch-icon.png"> Unknown directive
    28 <link rel="icon" type="image/png" sizes="32x32" href="https://bppresents.nl/assets/images/favicon/favicon-32x32.png"> Unknown directive
    29 <link rel="icon" type="image/png" sizes="16x16" href="https://bppresents.nl/assets/images/favicon/favicon-16x16.png"> Unknown directive
    30 <link rel="manifest" href="https://bppresents.nl/assets/images/favicon/site.webmanifest"> Unknown directive
    31 <link rel="mask-icon" href="https://bppresents.nl/assets/images/favicon/safari-pinned-tab.svg" color="#424242"> Unknown directive
    32 <meta name="msapplication-TileColor" content="#2d89ef"> Syntax not understood
    33 <meta name="theme-color" content="#ffffff"> Syntax not understood
    35 </head> Syntax not understood
    37 <body class="is-locked"> Syntax not understood
    39 <div class="body-inner"> Syntax not understood
    40 <main class="site-container"> Syntax not understood
    43 <nav class="nav-module"> Syntax not understood
    44 <button class="nav-module__button is-clickable"> Syntax not understood
    45 <span class="nav-module__toggle nav-module__button-text" style="display: none;" ><h3>Right Now</h3></span> Unknown directive
    46 <span class="nav-module__toggle nav-module__button-icon"><svg data-name="close" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20"><defs><style>.cls-1{fill:none;stroke:#000;stroke-width:2px}</style></defs><path class="cls-1" d="M1 1l18 18M19 1L1 19"/></svg></span> Unknown directive
    47 </button> Syntax not understood
    48 </nav> Syntax not understood
    50 <div class="layer layer__bottom-info" style="display: none;"> Unknown directive
    51 <div class="grid-container"> Syntax not understood
    54 <div class="module-cell content-module__title content-module__title-info"> Syntax not understood
    55 <h2> Syntax not understood
    56 Bureau Syntax not understood
    57 <br> Syntax not understood
    58 Postjesweg Syntax not understood
    59 </h2> Syntax not understood
    60 </div> Syntax not understood
    62 <section class="module-cell content-module__text content-module__text-about"> Syntax not understood
    63 <h3>NL:</h3> Unknown directive
    64 <p>Bureau Postjesweg is een platform voor tentoonstellingen, presentaties en uitwisseling in Amsterdam Nieuw-West. Gelegen aan de metrohalte Postjesweg, verkent en bevraagt Bureau Postjesweg de transities in Amsterdam Nieuw-West en brengt deze in kaart samen met kunstenaars, deskundigen, bewoners en publiek. Als gastvrije én kritische ruimte voor reflectie, interactie en verbinding, werkt Bureau Postjesweg als een groeiend collectief van kunstenaars en curatoren. We werken procesgericht aan lange termijn projecten die zijn ingebed in de sociale en culturele context van Nieuw-West.<br /> Syntax not understood
    65 Het Bureau Postjesweg kernteam bestaat in 2023/24 uit Iris Dik (kunsthistoricus, hoofd curator, communicator), Tobias Krasenberg (curator, adviseur) Amine Habti (audiovisueel ontwerper, facilitator) en Holger Nickisch (kunstenaar, curator, facilitator). Er is een vacature voor een zakelijk leider.</p> Syntax not understood
    66 <p>Sinds 2021 presenteren we projecten met onder andere <a href="https://bppresents.nl/events/on-protection">M&uuml;ge Yilmaz</a>, <a href="https://bppresents.nl/events/i-burn-for-you">Sarah van Sonsbeeck</a>, <a href="https://bppresents.nl/events/under-supreme-patronage">Hamid El Kanbouhi</a>, <a href="https://bppresents.nl/events/heidi-vogels-final-days">Heidi Vogels</a>, <a href="https://erikhagoort.nl/Erik_Hagoort_NL_thuispagina.html">Erik Hagoort</a>, <a href="https://bppresents.nl/events/furious-transhumance">Constance Hinfray</a>, <a href="https://bppresents.nl/events/basics-of-complexity">Bushra Arbawi &amp; Joana Cuiko</a>, <a href="https://bppresents.nl/events/tutku-passion-for-the-birds">AnneMarie van Splunter</a>, <a href="https://bppresents.nl/events/knotted-tales">Mina Abouzahra</a>, <a href="https://bppresents.nl/events/de-praktikant">Holger Nickisch</a>, <a href="https://bppresents.nl/events/public-life-otherwise">Dimitri van den Wittenboer</a>, <a href="https://bppresents.nl/events/richard-kofi-en-junadry-leocaria">Richard Kofi en Junadry Leocaria</a>, <a href="https://bppresents.nl/events/the-yalda-preparations">Delaram Hosseinioun</a>, <a href="https://bppresents.nl/events/the-yalda-preparations">Asha Alizadeh</a>, <a href="https://bppresents.nl/events/the-yalda-preparations">Iliada Charalambous &amp; Afrang Malekian</a>, <a href="https://bppresents.nl/events/bringing-back-cheb">Amine Habti</a>, <a href="https://bppresents.nl/events/bringing-back-cheb">Abdelkader Benali</a>, <a href="https://bppresents.nl/events/nieuwjaar-2024-yennayer-2974">Saida Nadi Benali</a>, <a href="https://bppresents.nl/events/weaving-voices-slotervaart-in-transitie">Nina van Hartskamp</a>, <a href="https://bppresents.nl/events/weaving-voices-slotervaart-in-transitie">Rosa Smits</a>, <a href="https://bppresents.nl/events/quin-biervliet">Quin</a>, <a href="https://bppresents.nl/events/rosa-johanna">Rosa Johanna</a>, <a href="https://bppresents.nl/events/asefeh-tayebani">Asefeh Tayebani</a>, <a href="https://bppresents.nl/events/hanna-steenbergen-cockerton">Hanna Steenbergen-Cockerton</a>, <a href="https://bppresents.nl/events/margherita-soldati">Margherita Soldati</a>, <a href="https://bppresents.nl/events/wie-ben-ik-wat-was-ik-en-wie-kan-ik-nog-worden">Ren&eacute;e Kool &amp; Holger Nickisch</a>, <a href="https://bppresents.nl/events/een-brug-naar-huis">Karima &amp; Said Aissaoui</a>, <a href="https://bppresents.nl/events/back-to-the-future">Jantien Jongsma</a>, <a href="https://bppresents.nl/events/filmavond-bij-oba-woensdag-24-1-18-21u">Dominique Panhuysen &amp; Danielle van Vree</a>, <a href="https://bppresents.nl/events/harbour-of-action">Olivier Delebecque</a>, <a href="https://bppresents.nl/events/le-bateau">Le Bateau</a>, <a href="https://bppresents.nl/events/alle-dagen-feest">Myrthe Lanting &amp; Sophie Wartenbergh</a>, Arnon Grunberg en een netwerk van jonge kunstenaars en academici rond Bureau Postjesweg, The Supremes. </p> Unknown directive
    67 <p>Hier lees je meer over <a href="https://bppresents.nl/events/board-partners-funding-bureau-postjesweg">het bestuur, partners en funding</a>.</p> Unknown directive
    68 <p>Bij Bureau Postjesweg, een lichte ruimte van 100 m2, ingebed in een levendig deel van Amsterdam, kun je ook een meeting of bijeenkomst organiseren. Altijd tussen inspirerende kunst.<br /> Syntax not understood
    69 In opdracht verzorgen we kunstadvies, workshops, excursies en exposities voor bedrijven en organisaties.<br /> Syntax not understood
    70 Voor GGD Amsterdam presenteerden we van maart &#8216;21 tot maart &#8216;22&#160;<a href="https://bppresents.nl/events/ggd-testpaviljoen-sloterdijk">zes series kunstdoeken</a>, een grote buitenexpo bij Testpaviljoen Sloterdijk. Met werk van Abdelkader Benali, Hamid El Kanbouhi, Marlies Rijneveld, Rosa Johanna, Müge Yilmaz en Sarah van Sonsbeeck.</p> Syntax not understood
    71 <h3>EN:</h3> Unknown directive
    72 <p>Bureau Postjesweg is a platform for exhibitions, presentations and exchange in Amsterdam Nieuw-West. Located at the Postjesweg metro stop, Bureau Postjesweg explores and questions the transitions in Amsterdam Nieuw-West and maps these together with artists, experts, residents and the public. As a welcoming and critical space for reflection, interaction and connection, Bureau Postjesweg works as a growing collective of artists and curators. We work process-oriented on long-term projects that are embedded in the social and cultural context of New West.<br /> Syntax not understood
    73 In 2023/24 the Bureau Postjesweg coreteam consists of Iris Dik (art historian, main curator, communicator), Tobias Krasenberg (curator, adviser) Amine Habti (audiovisual designer, facilitator) and Holger Nickisch (artist, curator, facilitator).<br /> Syntax not understood
    74 There is a vacancy for a business leader.</p> Syntax not understood
    75 <p>Since 2021 we present projects with <a href="https://bppresents.nl/events/on-protection">M&uuml;ge Yilmaz</a>, <a href="https://bppresents.nl/events/i-burn-for-you">Sarah van Sonsbeeck</a>, <a href="https://bppresents.nl/events/under-supreme-patronage">Hamid El Kanbouhi</a>, <a href="https://bppresents.nl/events/heidi-vogels-final-days">Heidi Vogels</a>, <a href="https://erikhagoort.nl/Erik_Hagoort_NL_thuispagina.html">Erik Hagoort</a>, <a href="https://bppresents.nl/events/furious-transhumance">Constance Hinfray</a>, <a href="https://bppresents.nl/events/co-existence">Bushra Arbawi &amp; Joana Cuiko</a>, <a href="https://bppresents.nl/events/tutku-passion-for-the-birds">AnneMarie van Splunter</a>, <a href="https://bppresents.nl/events/knotted-tales">Mina Abouzahra</a>, <a href="https://bppresents.nl/events/de-praktikant">Holger Nickisch</a>, <a href="https://bppresents.nl/events/public-life-otherwise">Dimitri van den Wittenboer</a>, <a href="https://bppresents.nl/events/richard-kofi-en-junadry-leocaria">Richard Kofi and Junadry Leocaria</a>, <a href="https://bppresents.nl/events/the-yalda-preparations">Delaram Hosseinioun</a>, <a href="https://bppresents.nl/events/the-yalda-preparations">Asha Alizadeh</a>, <a href="https://bppresents.nl/events/the-yalda-preparations">Iliada Charalambous &amp; Afrang Malekian</a>, <a href="https://bppresents.nl/events/bringing-back-cheb">Amine Habti</a>, <a href="https://bppresents.nl/events/bringing-back-cheb">Abdelkader Benali</a>, <a href="https://bppresents.nl/events/nieuwjaar-2024-yennayer-2974">Saida Nadi Benali</a>, <a href="https://bppresents.nl/events/weaving-voices-slotervaart-in-transitie">Nina van Hartskamp</a>, <a href="https://bppresents.nl/events/weaving-voices-slotervaart-in-transitie">Rosa Smits</a>, <a href="https://bppresents.nl/events/quin-biervliet">Quin</a>, <a href="https://bppresents.nl/events/rosa-johanna">Rosa Johanna</a>, <a href="https://bppresents.nl/events/asefeh-tayebani">Asefeh Tayebani</a>, <a href="https://bppresents.nl/events/hanna-steenbergen-cockerton">Hanna Steenbergen-Cockerton</a>, <a href="https://bppresents.nl/events/margherita-soldati">Margherita Soldati</a>, <a href="https://bppresents.nl/events/wie-ben-ik-wat-was-ik-en-wie-kan-ik-nog-worden">Ren&eacute;e Kool &amp; Holger Nickisch</a>, <a href="https://bppresents.nl/events/een-brug-naar-huis">Karima &amp; Said Aissaoui</a>, <a href="https://bppresents.nl/events/back-to-the-future">Jantien Jongsma</a>, <a href="https://bppresents.nl/events/filmavond-bij-oba-woensdag-24-1-18-21u">Dominique Panhuysen &amp; Danielle van Vree</a>, <a href="https://bppresents.nl/events/harbour-of-action">Olivier Delebecque</a>, <a href="https://bppresents.nl/events/le-bateau">Le Bateau</a>, <a href="https://bppresents.nl/events/alle-dagen-feest">Myrthe Lanting &amp; Sophie Wartenbergh</a>, Arnon Grunberg en een netwerk van jonge kunstenaars en academici rond Bureau Postjesweg, The Supremes. </p> Unknown directive
    76 <p>Here you can read more about our <a href="https://bppresents.nl/events/board-partners-funding-bureau-postjesweg">board, partners and funding</a>.</p> Unknown directive
    77 <p>At Bureau Postjesweg, a light space of 100 m2, embedded in a lively part of Amsterdam, you can also organize a meeting or gathering. Always amidst inspiring art.<br /> Syntax not understood
    78 We provide art advice, workshops, tours and exhibitions for companies and organizations on commission.<br /> Syntax not understood
    79 For GGD Amsterdam, we presented from March &#8216;21 to March &#8216;22&#160;<a href="https://bppresents.nl/events/ggd-testpaviljoen-sloterdijk">six series of art banners</a>, a large outdoor expo around Testpaviljoen Sloterdijk. With work by Abdelkader Benali, Hamid El Kanbouhi, Marlies Rijneveld, Rosa Johanna, Müge Yilmaz and Sarah van Sonsbeeck.</p> </section> Syntax not understood
    81 <div class="module-cell content-module__divider"></div> Syntax not understood
    83 <section class="module-cell content-module__text content-module__text-previous-events"> Syntax not understood
    84 <h3>Previous Events:</h3> Unknown directive
    85 <ul class="previous-events__list"> Syntax not understood
    86 <li class="previous-events__list-item"> Syntax not understood
    87 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/alle-dagen-feest">Myrthe Lanting & Sophie Wartenbergh, Alle Dagen Feest?, 09.04 - 23.04 2024</a> Unknown directive
    88 </li> Syntax not understood
    89 <li class="previous-events__list-item"> Syntax not understood
    90 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/le-bateau">Le Bateau, From B, the Hundred to De Walvis, 13.03 - 29.03 2024</a> Unknown directive
    91 </li> Syntax not understood
    92 <li class="previous-events__list-item"> Syntax not understood
    93 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/panel/pages/events+harbour-of-action">Olivier Delebecque & Bayan Jouma, Harbour of Action, 03.02 - 28.02 2024</a> Unknown directive
    94 </li> Syntax not understood
    95 <li class="previous-events__list-item"> Syntax not understood
    96 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/filmavond-bij-oba-woensdag-24-1-18-21u">Dominique Panhuysen & Danielle Van Vree, De Lijnen Waarlangs Wij Lopen, 24.01 2024</a> Unknown directive
    97 </li> Syntax not understood
    98 <li class="previous-events__list-item"> Syntax not understood
    99 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/nieuwjaar-2024-yennayer-2974">Saida Nadi-Benali, Hamid El Kanbouhi, Myrthe Lanting & Sophie Wartenbergh: Nieuwjaar 2024 Yennayer 2974, 14.01 2024</a> Unknown directive
    100 </li> Syntax not understood
    101 <li class="previous-events__list-item"> Syntax not understood
    102 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/back-to-the-future">Jantien Jongsma: Back to the Future, 20.11 - 21.12 2023</a> Unknown directive
    103 </li> Syntax not understood
    104 <li class="previous-events__list-item"> Syntax not understood
    105 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/panel/pages/events+een-brug-naar-huis">Karima Aissaoui, Said Assaoui en Gasten: Museumnacht / Een Brug Naar Huis, 04.11 - 18.11 2023</a> Unknown directive
    106 </li> Syntax not understood
    107 <li class="previous-events__list-item"> Syntax not understood
    108 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/postjesweg-moves-bp-x-oba">Abdelkader Benali en Gasten: Postjesweg Moves / Slotervaart Buurt Fest, 23.09 - 30.09 2023</a> Unknown directive
    109 </li> Syntax not understood
    110 <li class="previous-events__list-item"> Syntax not understood
    111 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/strands-of-resilience">Margherita Soldati, Hanna Steenbergen-Cockerton & Asefeh Tayebani: Strands of Resilience, 08.07 - 22.07 2023</a> Unknown directive
    112 </li> Syntax not understood
    113 <li class="previous-events__list-item"> Syntax not understood
    114 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/rosa-johanna">Rosa Johanna & Quin: Learning Unlearning, 31.05 - 01.07 2023</a> Unknown directive
    115 </li> Syntax not understood
    116 <li class="previous-events__list-item"> Syntax not understood
    117 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/istota-meet-the-forces-of-your-imagination">Growing Pains & Ola Lanko: Istota, Workshop for Children, 21.05 2023</a> Unknown directive
    118 </li> Syntax not understood
    119 <li class="previous-events__list-item"> Syntax not understood
    120 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/weaving-voices-slotervaart-in-transitie">Nina Van Hartskamp & Rosa Smits: Weaving Voices: Slotervaart in Transitie, 01.04-07.05 2023</a> Unknown directive
    121 </li> Syntax not understood
    122 <li class="previous-events__list-item"> Syntax not understood
    123 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/bringing-back-cheb">Abdelkader Benali & Amine Habti: Bringing Back Cheb, 01.03 - 30.03 2023</a> Unknown directive
    124 </li> Syntax not understood
    125 <li class="previous-events__list-item"> Syntax not understood
    126 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/the-yalda-preparations">Delaram Hosseinioun & Various Artists: The Yalda Preparations, 07.12 2022 - 15.02 2023</a> Unknown directive
    127 </li> Syntax not understood
    128 <li class="previous-events__list-item"> Syntax not understood
    129 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/richard-kofi-en-junadry-leocaria">Richard Kofi & Junadry Leocaria: Krusada, 01.08 - 01.11 2022</a> Unknown directive
    130 </li> Syntax not understood
    131 <li class="previous-events__list-item"> Syntax not understood
    132 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/citymarket-otherwise">Dimitri Van Den Wittenboer & Holger Nickisch: Stadsmarkt Anders, 03.05 - 08.07 2022</a> Unknown directive
    133 </li> Syntax not understood
    134 <li class="previous-events__list-item"> Syntax not understood
    135 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/knotted-tales">Mina Abouzahra: Verknoopte Verhalen, 24.03 - 24.04 2022</a> Unknown directive
    136 </li> Syntax not understood
    137 <li class="previous-events__list-item"> Syntax not understood
    138 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/twee-korte-films">Mina Abouzahra, AnneMarie Van Splunter: 2 Korte Films, 04.03 - 20.03 2022</a> Unknown directive
    139 </li> Syntax not understood
    140 <li class="previous-events__list-item"> Syntax not understood
    141 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/tutku-passion-for-the-birds">AnneMarie Van Splunter: Tutku (Passion), 24.02 - 20.03 2022</a> Unknown directive
    142 </li> Syntax not understood
    143 <li class="previous-events__list-item"> Syntax not understood
    144 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/basics-of-complexity">Bushra Arbawi & Joana Čuiko: Basics of Complexity, 03.02 2022</a> Unknown directive
    145 </li> Syntax not understood
    146 <li class="previous-events__list-item"> Syntax not understood
    147 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/co-existence">Bushra Arbawi & Joana Čuiko: Co-Existence, 17.01 - 24.01 2022</a> Unknown directive
    148 </li> Syntax not understood
    149 <li class="previous-events__list-item"> Syntax not understood
    150 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/heidi-vogels-final-days">Heidi Vogels: Assembly - Gardens of Fez Extended, 03.01 - 16.01 2022</a> Unknown directive
    151 </li> Syntax not understood
    152 <li class="previous-events__list-item"> Syntax not understood
    153 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/assembly-gardens-of-fez">Heidi Vogels: Assembly - Gardens of Fez, 25.11 - 19.12 2021</a> Unknown directive
    154 </li> Syntax not understood
    155 <li class="previous-events__list-item"> Syntax not understood
    156 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/public-life-otherwise/">Dimitri Van Den Wittenboer: Public Life Otherwise, 04.10-21.10 2021</a> Unknown directive
    157 </li> Syntax not understood
    158 <li class="previous-events__list-item"> Syntax not understood
    159 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/de-praktikant">Holger Nickisch: De Praktikant, 07.09- 21.10 2021</a> Unknown directive
    160 </li> Syntax not understood
    161 <li class="previous-events__list-item"> Syntax not understood
    162 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/furious-transhumance">Constance Hinfray: Furious Transhumance, 04.09 - 05.09 2021</a> Unknown directive
    163 </li> Syntax not understood
    164 <li class="previous-events__list-item"> Syntax not understood
    165 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/art-summer-school">Garden Collectives: Start From Where You Are, 15.07 - 05.09 2021</a> Unknown directive
    166 </li> Syntax not understood
    167 <li class="previous-events__list-item"> Syntax not understood
    168 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/under-supreme-patronage">Hamid El Kanbouhi: Under Supreme Patronage, 18.08 - 22.08 2021</a> Unknown directive
    169 </li> Syntax not understood
    170 <li class="previous-events__list-item"> Syntax not understood
    171 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/i-burn-for-you">Sarah Van Sonsbeeck: I Burn for You, 30.06 – 12.07.2021</a> Unknown directive
    172 </li> Syntax not understood
    173 <li class="previous-events__list-item"> Syntax not understood
    174 <a class="is-clickable has-before-arrow" href="https://bppresents.nl/events/on-protection">Müge Yilmaz: On Protection, 03.05 – 30.06 2021</a> Unknown directive
    175 </li> Syntax not understood
    176 <li class="previous-events__list-item"> Syntax not understood
    177 <a class="is-clickable has-before-arrow" href="http://ringsporen2.bppresents.nl/">Ringsporen 2: Garden Collectives – Imagining Other Green Spaces, 14.09.2019</a> Unknown directive
    178 </li> Syntax not understood
    179 <li class="previous-events__list-item"> Syntax not understood
    180 <a class="is-clickable has-before-arrow" href="http://ringsporen1.bppresents.nl/">Ringsporen 1: A Preview – From Garden Collectives to New Frontier, 24.01 – 03.02 2019</a> Unknown directive
    181 </li> Syntax not understood
    182 </ul> Syntax not understood
    183 </section> Syntax not understood
    185 <div class="module-cell content-module__divider"></div> Syntax not understood
    187 <section class="module-cell content-module__text content-module__text-contact col left-col"> Syntax not understood
    188 <p> Syntax not understood
    189 Postjesweg 160 (aan de rechter achterhoek van het gebouw) <br> Syntax not understood
    190 1061 AX Amsterdam <br> Syntax not understood
    191 <a class="is-clickable" href="mailto:&#105;&#110;&#x66;&#x6f;&#x40;&#x62;&#x70;&#112;&#x72;&#101;&#115;&#101;&#x6e;&#x74;&#115;&#x2e;&#110;&#x6c;">&#x69;&#x6e;&#102;&#111;&#x40;&#x62;&#x70;&#x70;&#114;&#x65;&#115;&#101;&#110;&#116;&#x73;&#x2e;&#110;&#108;</a> Unknown directive
    192 <br> Syntax not understood
    193 +31 6 24641400 <br> Syntax not understood
    194 <a class="is-clickable underline" href="https://goo.gl/maps/w1hkA5ynggcn4B6A9">Google Maps</a> Unknown directive
    195 </p> Syntax not understood
    197 <div class="disclaimer"> Syntax not understood
    198 <p>We are gradually developing our website and socials, in the meantime subscribe to our <a href="http://eepurl.com/hA1RYX">newsletter</a> or follow us on <a href="https://www.facebook.com/Bureau-Postjesweg-2092215654403096">facebook</a>, <a href="https://www.linkedin.com/company/bureau-postjesweg-presents/">linkedin</a> and <a href="https://www.instagram.com/bureaupostjesweg/">instagram</a> to see our other activities and updates.</p> </div> Unknown directive
    199 </section> Syntax not understood
    201 <section class="module-cell content-module__text content-module__text-contact col right-col"> Syntax not understood
    202 <p> Syntax not understood
    203 See current event on our frontpage and by appointment: <br> Unknown directive
    204 info@bppresents.nl <br> Syntax not understood
    205 06 24 64 14 00 </p> Syntax not understood
    206 </section> Syntax not understood
    208 <div class="module-cell content-module__spacer-half"></div> Syntax not understood
    210 <section class="module-cell content-module__sign"> Syntax not understood
    211 <figure> Syntax not understood
    212 <img class="is-vertical" src="https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge_yilmaz.png" srcset="https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-800x.png 800w, https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-1024x.png 1024w, https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-1440x.png 1440w, https://bppresents.nl/media/pages/info/88d6640d68-1670077275/hamsa-muge-yilmaz-1920x.png 1920w" width="1000" height="1342" alt="‘Hamsa’ against the evil eye by Müge Yilmaz, for you and for us."> Unknown directive
    213 </figure> Syntax not understood
    214 </section> Syntax not understood
    215 <section class="module-cell content-module__sign-caption"> Syntax not understood
    216 <figcaption class="small-text">‘Hamsa’ against the evil eye by Müge Yilmaz, for you and for us.</figcaption> Syntax not understood
    217 </section> Syntax not understood
    219 </div> Syntax not understood
    220 </div> Syntax not understood
    222 <div class="layer layer__top-event"> Syntax not understood
    223 <div class="grid-container event-module" style="background-color: #e3d6aa"> Unknown directive
    225 <div class="module-cell content-module__title"> Syntax not understood
    226 <h2> Syntax not understood
    227 Bureau Syntax not understood
    228 <br> Syntax not understood
    229 Postjesweg Syntax not understood
    230 <br> Syntax not understood
    231 Presents: Unknown directive
    232 </h2> Syntax not understood
    233 </div> Syntax not understood
    235 <div class="module-cell content-module__title content-module__title-event"> Syntax not understood
    236 <h3 class="has-line-height-1_5">Right Now</h3> Syntax not understood
    237 <h2>‘Afscheid Bureau Postjesweg’, Syntax not understood
    238 <br> Syntax not understood
    239 Team Bureau Postjesweg</h2> Syntax not understood
    240 </div> Syntax not understood
    242 <div class="module-cell content-module__cover"> Syntax not understood
    243 <figure> Syntax not understood
    244 <img src="https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2.jpg" srcset="https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-800x.jpg 800w, https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-1024x.jpg 1024w, https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-1440x.jpg 1440w, https://bppresents.nl/media/pages/events/afscheid-bureau-postjesweg/604053168c-1725092837/foto-nieuwsbrief-afscheid-2-1920x.jpg 1920w" width="1800" height="1201" alt="Afscheid Bureau Postjesweg"> Unknown directive
    245 <figcaption class="small-text">Bureau Postjesweg tijdens de expositie van Heidi Vogels, foto: Thomas Lenden</figcaption> Unknown directive
    246 </figure> Syntax not understood
    247 </div> Syntax not understood
    249 <section class="module-cell content-module__opening-times"> Syntax not understood
    250 <h3><p>21 september 24<br /> Syntax not understood
    251 16-20 u<br /> Syntax not understood
    252 (open inloop/ walk-in)</p></h3> Syntax not understood
    253 </section> Syntax not understood
    255 <section class="module-cell content-module__text content-module__text-event"> Syntax not understood
    256 <h3>NL:</h3> Unknown directive
    257 <p>Save the date: Afscheid projectruimte Bureau Postjesweg,<br /> Unknown directive
    258 zaterdag 21 september 16.00-20.00 u</p> Syntax not understood
    259 <p>&#8216;Het team maakte van BP een unieke en veilige plek om je artistieke ideeën te kunnen ontplooien en omdat je midden in de buurt bent, sta je altijd in contact met de mensen uit de omgeving.&#8217;<br /> Syntax not understood
    260 Karima Aissaoui</p> Syntax not understood
    261 <p>Na jaren intensief programma maken sluit Bureau Postjesweg de deuren. Graag nodigen we je uit om samen terug te kijken en afscheid te nemen in onze projectruimte in Nieuw-West.<br /> Syntax not understood
    262 Het begon allemaal in 2016 met een uitnodiging van architect Olaf Gipser en projectontwikkelaar Heutink om een kunstruimte te ontwikkelen, op een toen nog braakliggend grasveld aan de Postjesweg. Dit leidde tot bijeenkomsten met collega kunstenaars en curatoren in de bouwkeet, en via verkennende programma’s van presentaties en ontmoetingen in de buurt tot de opening van de projectruimte in 2021. Talloze kunstenaars waren te gast. We bouwden installaties, organiseerden filmpresentaties en performances, kunstenaars verbleven in huis als artist-in-residence voor korte intensieve werkperiodes, er werd buiten pizza gebakken en buurtkinderen renden in en uit, we bezochten de binnentuinen van de buren, organiseerden een zomerschool met New Metropolis, ontvingen buurtinitiatieven van Ru Paré Community tot Lab6&#160;en werkten samen met de OBA, The Beach en vele anderen. Tijdens de lockdown presenteerden we een buitenexpositie bij de GGD testlocatie Sloterdijk. Het uitgangspunt was altijd de context van de buurt of het stadsdeel, dat waar je vaak aan voorbij loopt, tastbaar maken en bevragen. Of het nu ging over de mechanismen van gentrificatie van de buurt, een performance over de migratieroutes van vogels in het park, of een onderzoek naar de herkomst van Harira (soep): dat wat zich vanuit het perspectief van kunstenaars aandiende zorgde vaak voor verrassende ontmoetingen. Bureau Postjesweg is en was een genereuze structuur van samenwerken, een uitnodiging om elkaar op andere wijze te treffen, samen te kijken en spreken over kunst in verhouding tot onze dagelijkse realiteit.<br /> Syntax not understood
    263 Een ambitieuze inzet, die leidde tot veel artistiek hoogstaande exposities en events. Een intensief traject dat nu door omstandigheden helaas tot een einde komt. Het is niet gelukt om versterking te vinden voor ons programmateam, en tegelijkertijd de financiële voorwaarden te scheppen om door te bouwen op het programma en de vele contacten en uitwisseling en vriendschappen in Nieuw-West.<br /> Syntax not understood
    264 Graag kijken we samen nog een keer terug op die bijzondere kunstprojecten die hier hebben plaatsgevonden, en iedereen die daarbij betrokken was en Bureau Postjesweg kleur, beweging en invulling gaf.</p> Syntax not understood
    265 <p>Hartelijke groet van het initiatiefteam sinds 2017:<br /> Unknown directive
    266 Iris Dik, curator, buurtverbinder<br /> Syntax not understood
    267 Holger Nickisch, kunstenaar/curator<br /> Syntax not understood
    268 Heidi Vogels, kunstenaar/curator </p> Syntax not understood
    269 <p>Met bijzondere dank aan:</p> Unknown directive
    270 <p>Helmich Heutink en Wilco Westendorp van HWH Investments voor het beschikbaar stellen van de ruimte.<br /> Syntax not understood
    271 Olaf Gipser (architect van het gebouw en voorzitter van het bestuur)<br /> Syntax not understood
    272 Abdelkader en Saida Benali voor hun inhoudelijke en culinaire bijdragen én burenhulp</p> Syntax not understood
    273 <p>Kunstenaars en curatoren die vanaf het begin meedachten en betrokken waren: Müge Yilmaz, Rosa Johanna, Sarah van Sonsbeeck, Tayfun Balçik, Delaram Hosseinioun, Tobias Krasenberg, Anissa Foukalne, Hamid El Kanbouhi, Richard Kofi, Dimitri van den Wittenboer, Amine Habti, Sophie Throsby, Naomi Poelsma, Karima Aissaoui, Samira Dainan, Tobias Krasenberg en alle andere kunstenaars/curatoren voor hun bijzondere presentaties (voor het totaal overzicht zie &#8216;previous events&#8217; op de infopagina)</p> Unknown directive
    274 <p>Alle betrokken (oud) medewerkers en bestuurders van:<br /> Unknown directive
    275 Stadsdeel Nieuw-West, Openbare Bibliotheek Amsterdam, Samen Wonen Samen Leven, New Metropolis, Van Eesteren Museum, The Beach, Buurtwerkplaats Noorderhof, CBK Zuidoost, MTS Audiovisueel</p> Syntax not understood
    276 <p>Lokale ondernemers Abi Patat, Pizzeria Nieuw West, Tante Toorop<br /> Syntax not understood
    277 en <a href="https://bppresents.nl/events/board-partners-funding-bureau-postjesweg">alle andere partners</a></p> Unknown directive
    278 <p>Bestuurders en oud bestuurders van <a href="https://bppresents.nl/events/board-partners-funding-bureau-postjesweg">Stichting Bureau Postjesweg Presents</a> (deze zal blijven bestaan voor toekomstige projecten)</p> Unknown directive
    279 <p>Amir Avraham voor het ontwerp van de huisstijl </p> Syntax not understood
    280 <p>Vaste fotograaf Thomas Lenden</p> Syntax not understood
    281 <p>Mondriaanfonds en AFK voor het ondersteunen van de jaarprogramma’s in 2021&#160;en 2022, Oranjefonds voor de ‘Reuring in de Buurt’ bijdrage in 2023, Stadsdeel Nieuw-West voor diverse gebiedsgerichte subsidies en aan alle andere subsidienten van de verschillende projecten</p> Syntax not understood
    282 <p>En tot slot: dank aan alle bezoekers van binnen en buiten de wijk voor jullie belangstelling en deelname.<br /> Unknown directive
    283 We hebben veel van elkaar geleerd!</p> Syntax not understood
    284 <h3>EN:</h3> Unknown directive
    285 <p>Save the date: Farewell Bureau Postjesweg projectspace,<br /> Unknown directive
    286 Saturday, September 21, 4:00 - 8:00 PM</p> Unknown directive
    287 <p>‘The team made BP a unique and safe place to develop artistic ideas, and by being in the heart of the neighborhood, you were always in contact with the people in the area.’<br /> Syntax not understood
    288 — Karima Aissaoui</p> Syntax not understood
    289 <p>After years of intensive programming, Bureau Postjesweg is closing its doors. We would like to invite you to look back and say goodbye together in our project space in New West.<br /> Syntax not understood
    290 It all started in 2016 with an invitation from architect Olaf Gipser and project developer Heutink to develop an art space on what was then an undeveloped lawn on the Postjesweg. This led to meetings with fellow artists and curators in the construction shed. Through exploratory programs of presentations and neighborhood meetings, this journey culminated in the opening of the project space in 2021. Numerous artists were guests. We built installations, organized film presentations and performances, hosted artists-in-residence for short, intensive work periods, baked pizza outside while neighborhood kids ran in and out, visited neighbors’ courtyards, organized a summer school with New Metropolis, hosted neighborhood initiatives from Ru Paré Community to Lab6, and collaborated with OBA, The Beach, and many others. During the lockdown, we presented an outdoor exhibition at the GGD test site in Sloterdijk. Our starting point was always to make the neighborhood&#8217;s context tangible and open to questioning—those elements that often go unnoticed. Whether exploring the mechanisms of gentrification, a performance about the migration routes of birds in the park, or an investigation into the origins of Harira (soup), the perspectives of artists often led to surprising encounters. Bureau Postjesweg was and remains a generous structure of collaboration—an invitation to meet in various ways, to look and talk together about art in relation to our everyday reality.<br /> Syntax not understood
    291 This ambitious effort led to many high-quality exhibitions and events. However, due to circumstances, this intensive process is now unfortunately coming to an end. It has not been possible to find reinforcements for our program team, or to secure the financial conditions needed to continue building on the program and the many contacts, exchanges, and friendships in New West.<br /> Syntax not understood
    292 We would like to reflect once more on the special art projects that took place here, and all those who were involved and contributed to the color, movement, and interpretation of Bureau Postjesweg.</p> Syntax not understood
    293 <p>Warm regards from the initiative team since 2017:<br /> Unknown directive
    294 Iris Dik, curator and neighborhood liaison<br /> Syntax not understood
    295 Holger Nickisch, artist/curator<br /> Syntax not understood
    296 Heidi Vogels, artist/curator</p> Syntax not understood
    297 <p>Special thanks to:</p> Unknown directive
    298 <p>Helmich Heutink and Wilco Westendorp of HWH Investments for providing the space<br /> Syntax not understood
    299 Olaf Gipser (architect of the building and chairman of the board)<br /> Syntax not understood
    300 Abdelkader and Saida Benali for their substantive and culinary contributions and neighborly help</p> Syntax not understood
    301 <p>Artists and curators who were involved from the beginning: Müge Yilmaz, Rosa Johanna, Sarah van Sonsbeeck, Tayfun Balçik, Delaram Hosseinioun, Tobias Krasenberg, Anissa Foukalne, Hamid El Kanbouhi, Richard Kofi, Dimitri van den Wittenboer, Amine Habti, Sophie Throsby, Naomi Poelsma, Karima Aissaoui, Samira Dainan, Tobias Krasenberg and all other artists/curators for their special presentations<br /> Unknown directive
    302 (for the total overview see under &#8216;previous events&#8217; on the info page)</p> Syntax not understood
    303 <p>All involved (former) employees and administrators of:<br /> Unknown directive
    304 Stadsdeel Nieuw-West, Openbare Bibliotheek Amsterdam, Samen Wonen Samen Leven, New Metropolis, Van Eesteren Museum, The Beach, Buurtwerkplaats Noorderhof, CBK Zuidoost, MTS Audiovisueel</p> Syntax not understood
    305 <p>Local entrepreneurs Abi Patat, Pizzeria New West, Tante Toorop,<br /> Syntax not understood
    306 and <a href="https://bppresents.nl/events/board-partners-funding-bureau-postjesweg">all other partners</a></p> Unknown directive
    307 <p>Directors and former directors of <a href="https://bppresents.nl/events/board-partners-funding-bureau-postjesweg">Stichting Bureau Postjesweg Presents</a> (which will continue for future projects)</p> Unknown directive
    308 <p>Amir Avraham for designing the corporate identity</p> Syntax not understood
    309 <p>Our regular photographer Thomas Lenden</p> Syntax not understood
    310 <p>Mondriaanfonds and AFK for supporting the annual programs in 2021 and 2022, Oranjefonds for the ‘Reuring in de Buurt’ contribution in 2023, Stadsdeel Nieuw-West for various area-specific subsidies, and all other subsidizers of the various projects</p> Syntax not understood
    311 <p>And finally, thank you to all visitors from inside and outside the neighborhood for your interest and participation.<br /> Syntax not understood
    312 We learned a lot from each other!</p> </section> Syntax not understood
    314 <div class="module-cell content-module__spacer"></div> Syntax not understood
    316 </div> Syntax not understood
    317 </div> Syntax not understood
    319 </main> Syntax not understood
    320 </div> Syntax not understood
    322 <script src="https://bppresents.nl/assets/js/vendors.js"></script> Unknown directive
    323 <script src="https://bppresents.nl/assets/js/app.js"></script> Unknown directive
    324 </body> Syntax not understood
    325 </html> Syntax not understood

Additional Items to Check Manually (1)

  1. Structured data is valid

    Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.

Passed Audits (10)

  1. Has a <meta name="viewport"> tag with width or initial-scale

    A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

  2. Document has a <title> element

    The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

  3. Document has a meta description

    Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

  4. Page has successful HTTP status code

    Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

  5. Links have descriptive text

    Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

  6. Links are crawlable

    Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

  7. Page isn’t blocked from indexing

    Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

  8. Image elements have [alt] attributes

    Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.

  9. Document has a valid hreflang

    hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.

  10. Document avoids plugins

    Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more about avoiding plugins.

Not Applicable (3)

  1. Document has a valid rel=canonical

    Canonical links suggest which URL to show in search results. Learn more about canonical links.

  2. Document uses legible font sizes

    Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.

  3. Tap targets are sized appropriately

    Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

PWA 43

Installable (1)

  1. Web app manifest or service worker do not meet the installability requirements

    3 reasons

    Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.

    Failure reason
    Manifest start URL is not valid
    Manifest does not contain a `name` or `short_name` field
    No supplied icon is at least 144 px square in PNG, SVG or WebP format, with the purpose attribute unset or set to "any"

PWA Optimized (5)

  1. Is not configured for a custom splash screen

    A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens.

    Failures:

    • Manifest does not have name

  2. Sets a theme color for the address bar.

    The browser address bar can be themed to match your site. Learn more about theming the address bar.

  3. Content is sized correctly for the viewport

    If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn how to size content for the viewport.

  4. Has a <meta name="viewport"> tag with width or initial-scale

    A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.

  5. Manifest doesn't have a maskable icon

    A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.

Additional Items to Check Manually (3)

  1. Site works cross-browser

    To reach the most number of users, sites should work across every major browser. Learn about cross-browser compatibility.

  2. Page transitions don't feel like they block on the network

    Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more about page transitions.

  3. Each page has a URL

    Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more about providing deep links.