webtoppings.bar

webtoppings.bar is SSL secured

Free website and domain report on webtoppings.bar

Last Updated: 14th November, 2024
Overview

Snoop Summary for webtoppings.bar

This is a free and comprehensive report about webtoppings.bar. The domain webtoppings.bar is currently hosted on a server located in United States with the IP address 104.21.58.156, where the local currency is USD and English is the local language. Our records indicate that webtoppings.bar is owned/operated by Surfly. Webtoppings.bar has the potential to be earning an estimated $1 USD per day from advertising revenue. If webtoppings.bar was to be sold it would possibly be worth $869 USD (based on the daily revenue potential of the website over a 24 month period). Webtoppings.bar is somewhat popular with an estimated 413 daily unique visitors. This report was last updated 14th November, 2024.

About webtoppings.bar

Site Preview: webtoppings.bar webtoppings.bar
Title: WebToppings
Description:
Keywords and Tags:
Related Terms: webtoppings
Fav Icon:
Age: Over 3 years old
Domain Created: 21st March, 2021
Domain Updated: 5th June, 2024
Domain Expires: 21st March, 2025
Review

Snoop Score

1/5

Valuation

$869 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,626,166
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 413
Monthly Visitors: 12,570
Yearly Visitors: 150,745
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $36 USD
Yearly Revenue: $430 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: webtoppings.bar 15
Domain Name: webtoppings 11
Extension (TLD): bar 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 97
Accessibility 73
Best Practices 92
SEO 73
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://webtoppings.bar/
Updated: 4th February, 2022

2.49 seconds
First Contentful Paint (FCP)
46%
39%
15%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
97

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for webtoppings.bar. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://webtoppings.bar/
http/1.1
0
76.075999997556
720
0
301
text/plain
https://webtoppings.bar/
h2
76.408999972045
200.20000007935
2536
5275
200
text/html
Document
https://cdn.iubenda.com/cs/ccpa/stub.js
h2
212.36000000499
273.45199999399
1943
4106
200
application/javascript
Script
https://cdn.iubenda.com/cs/iubenda_cs.js
h2
212.70700008608
253.99000011384
723
591
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.1/normalize.css
h2
213.01800012589
236.68100009672
2512
6138
200
text/css
Stylesheet
https://webtoppings.bar/main.css
h2
213.28800008632
273.90999998897
1643
2418
200
text/css
Stylesheet
https://webtoppings.bar/assets/index.42392481.js
h2
213.57600018382
348.49500004202
13749
36118
200
application/javascript
Script
https://webtoppings.bar/assets/vendor.c2c71b6d.js
h2
213.90100009739
332.06399995834
97010
274390
200
application/javascript
Script
https://webtoppings.bar/assets/index.212e81d2.css
h2
214.34499998577
1312.055000104
3724
9972
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Nunito+Sans
h2
277.4690000806
295.91200011782
1289
1643
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Nunito
h2
277.6770000346
292.87400003523
1298
1654
200
text/css
Stylesheet
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
h2
280.06700007245
314.98700007796
57586
277423
200
application/javascript
Script
https://www.iubenda.com/cookie-solution/confs/js/25094004.js
h2
347.34200011007
732.10100014694
788
159
200
application/javascript
Script
https://webtoppings.bar/assets/webtoppings_front.c8c60398.svg
h2
449.50400013477
512.59100018069
98664
314101
200
image/svg+xml
Image
https://webtoppings.bar/assets/chef.d67d3e54.png
h2
449.62800014764
1527.4130001199
7542
6698
200
image/png
Image
https://webtoppings.bar/assets/pizza.aea082fc.png
h2
449.81500017457
495.11800007895
16940
16093
200
image/png
Image
https://webtoppings.bar/assets/privacy-centered.cc55a2eb.png
h2
450.2330000978
508.85400013067
20102
19253
200
image/png
Image
https://webtoppings.bar/assets/privacy.64c639c6.png
h2
450.48000011593
534.73299997859
12996
12143
200
image/png
Image
https://webtoppings.bar/assets/annotation-centered.84fe5136.png
h2
450.885000173
508.38400004432
25521
24666
200
image/png
Image
https://webtoppings.bar/assets/annotation.3ee7029d.png
h2
451.05000003241
509.9760000594
15825
14984
200
image/png
Image
https://webtoppings.bar/assets/translator-centered.0b5120c3.png
h2
451.34200016037
492.0240000356
19720
18875
200
image/png
Image
https://webtoppings.bar/assets/translator.0b8fe40b.png
h2
451.52800017968
567.05099996179
12635
11794
200
image/png
Image
https://webtoppings.bar/assets/darkmode-centered.6da5dd92.png
h2
451.85100007802
494.66400011443
13384
12535
200
image/png
Image
https://webtoppings.bar/assets/darkmode.9530b71a.svg
h2
452.08099996671
511.90600008704
125758
277643
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-sepia.0377f712.svg
h2
452.23499997519
493.72699996457
1622
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-night.326b062d.svg
h2
452.45400001295
1518.296000082
1623
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-noir.7add3fa7.svg
h2
452.65000010841
503.77700012177
1621
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-contrast.e8a81854.svg
h2
452.86400010809
1555.3610001225
1628
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/surfly-logo.bdbb80b1.svg
h2
453.28900008462
509.35399997979
5950
12887
200
image/svg+xml
Image
https://webtoppings.bar/assets/bg_pizza.8caadc70.svg
h2
1316.0060001537
1362.1819999535
9149
20734
200
image/svg+xml
Image
https://fonts.gstatic.com/s/nunitosans/v11/pe0qMImSLYBIv1o4X1M8cce9I9tAcVwo.woff2
h2
1319.2010000348
1323.3720001299
12319
11380
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
241.71
7.904
320.254
9.684
362.925
23.486
409.894
83.485
554.391
14.527
569.132
34.536
772.621
6.599
1353.429
47.759
1406.757
11.263
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Webtoppings.bar should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Webtoppings.bar should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Webtoppings.bar should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Webtoppings.bar should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Webtoppings.bar should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 99 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://webtoppings.bar/assets/vendor.c2c71b6d.js
97010
59049
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
57586
42119
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 104 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://webtoppings.bar/assets/annotation-centered.84fe5136.png
24666
20873.4
https://webtoppings.bar/assets/privacy-centered.cc55a2eb.png
19253
16367.7
https://webtoppings.bar/assets/translator-centered.0b5120c3.png
18875
16018.95
https://webtoppings.bar/assets/pizza.aea082fc.png
16093
13011.8
https://webtoppings.bar/assets/annotation.3ee7029d.png
14984
11282.5
https://webtoppings.bar/assets/darkmode-centered.6da5dd92.png
12535
10521.8
https://webtoppings.bar/assets/privacy.64c639c6.png
12143
9372.25
https://webtoppings.bar/assets/translator.0b8fe40b.png
11794
9031.9
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 120 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://webtoppings.bar/
124.785
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Webtoppings.bar should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://webtoppings.bar/
190
https://webtoppings.bar/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Webtoppings.bar should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn.iubenda.com/cs/ccpa/stub.js
79
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
35
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 575 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://webtoppings.bar/assets/darkmode.9530b71a.svg
125758
https://webtoppings.bar/assets/webtoppings_front.c8c60398.svg
98664
https://webtoppings.bar/assets/vendor.c2c71b6d.js
97010
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
57586
https://webtoppings.bar/assets/annotation-centered.84fe5136.png
25521
https://webtoppings.bar/assets/privacy-centered.cc55a2eb.png
20102
https://webtoppings.bar/assets/translator-centered.0b5120c3.png
19720
https://webtoppings.bar/assets/pizza.aea082fc.png
16940
https://webtoppings.bar/assets/annotation.3ee7029d.png
15825
https://webtoppings.bar/assets/index.42392481.js
13749
Uses efficient cache policy on static assets — 1 resource found
Webtoppings.bar can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.iubenda.com/cookie-solution/confs/js/25094004.js
86400000
788
Avoids an excessive DOM size — 341 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
341
Maximum DOM Depth
15
Maximum Child Elements
11
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Webtoppings.bar should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Unattributable
104.862
8.617
0.19
https://webtoppings.bar/assets/vendor.c2c71b6d.js
86.016
81.118
1.018
https://webtoppings.bar/
72.396
2.492
1.125
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
123.655
Other
84.508
Style & Layout
74.774
Rendering
13.12
Script Parsing & Compilation
8.335
Parse HTML & CSS
5.29
Keep request counts low and transfer sizes small — 31 requests • 575 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
31
588520
Image
17
390680
Script
6
171799
Font
1
12319
Stylesheet
5
10466
Document
1
2536
Other
1
720
Media
0
0
Third-party
8
78458
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
61040
0
14906
0
2512
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://webtoppings.bar/assets/vendor.c2c71b6d.js
341
83
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of webtoppings.bar on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Eliminate render-blocking resources — Potential savings of 380 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Webtoppings.bar should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.1/normalize.css
2512
230
https://cdn.iubenda.com/cs/ccpa/stub.js
1943
230

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/nunitosans/v11/pe0qMImSLYBIv1o4X1M8cce9I9tAcVwo.woff2
4.1710000950843
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://webtoppings.bar/assets/surfly-logo.bdbb80b1.svg
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of webtoppings.bar. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Webtoppings.bar may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Failing Elements
ARIA IDs are not unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Failing Elements

Contrast

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that webtoppings.bar should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://webtoppings.bar/
Allowed
73

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for webtoppings.bar. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of webtoppings.bar on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — 101 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
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
<link
Syntax not understood
6
rel="icon"
Syntax not understood
7
type="image/svg+xml"
Syntax not understood
8
href="/assets/pizza.aea082fc.png"
Syntax not understood
9
/>
Syntax not understood
10
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
Syntax not understood
12
<script type="text/javascript">
Syntax not understood
13
var _iub = _iub || [];
Syntax not understood
14
_iub.csConfiguration = {"enableCcpa":true,"countryDetection":true,"invalidateConsentWithoutLog":true,"consentOnContinuedBrowsing":false,"ccpaAcknowledgeOnDisplay":true,"lang":"en","siteId":2463150,"floatingPreferencesButtonDisplay":false,"cookiePolicyId":25094004, "banner":{ "closeButtonDisplay":false,"acceptButtonDisplay":true,"customizeButtonDisplay":true,"acceptButtonColor":"#488646","acceptButtonCaptionColor":"white","customizeButtonColor":"#919191","customizeButtonCaptionColor":"white","rejectButtonDisplay":true,"rejectButtonColor":"#443e3e","rejectButtonCaptionColor":"white","listPurposes":true,"explicitWithdrawal":true,"position":"float-bottom-left","textColor":"#757575","backgroundColor":"#ebe7dc" }};
Unknown directive
15
</script>
Syntax not understood
16
<script type="text/javascript" src="//cdn.iubenda.com/cs/ccpa/stub.js"></script>
Syntax not understood
17
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>
Syntax not understood
19
<link
Syntax not understood
20
rel="stylesheet"
Syntax not understood
21
href="https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.1/normalize.css"
Unknown directive
22
/>
Syntax not understood
23
<link
Syntax not understood
24
rel="stylesheet"
Syntax not understood
25
href="/main.css"
Syntax not understood
26
/>
Syntax not understood
28
<!-- Hotjar Tracking Code for https://webtoppings.bar -->
Unknown directive
29
<script
Syntax not understood
30
comment="attributes below enable automatic blocking by iubenda"
Syntax not understood
31
class="_iub_cs_activate-inline" type="text/plain"
Syntax not understood
32
>
Syntax not understood
33
if (location.origin === 'https://webtoppings.bar') {
Unknown directive
34
(function (h, o, t, j, a, r) {
Syntax not understood
35
h.hj =
Syntax not understood
36
h.hj ||
Syntax not understood
37
function () {
Syntax not understood
38
(h.hj.q = h.hj.q || []).push(arguments);
Syntax not understood
39
};
Syntax not understood
40
h._hjSettings = { hjid: 2401001, hjsv: 6 };
Unknown directive
41
a = o.getElementsByTagName('head')[0];
Syntax not understood
42
r = o.createElement('script');
Syntax not understood
43
r.async = 1;
Syntax not understood
44
r.src = t + h._hjSettings.hjid + j + h._hjSettings.hjsv;
Syntax not understood
45
a.appendChild(r);
Syntax not understood
46
})(
Syntax not understood
47
window,
Syntax not understood
48
document,
Syntax not understood
49
'https://static.hotjar.com/c/hotjar-',
Unknown directive
50
'.js?sv=',
Syntax not understood
51
);
Syntax not understood
52
}
Syntax not understood
53
</script>
Syntax not understood
55
<script class="_iub_cs_activate" type="text/plain" src="https://www.googleoptimize.com/optimize.js?id=OPT-598LG6H"></script>
Unknown directive
57
<script class="_iub_cs_activate" type="text/plain" async src="https://www.googletagmanager.com/gtag/js?id=G-TBJTNQEBJ1"></script>
Unknown directive
58
<script class="_iub_cs_activate-inline" type="text/plain">
Syntax not understood
59
window.dataLayer = window.dataLayer || [];
Syntax not understood
60
function gtag(){dataLayer.push(arguments);}
Syntax not understood
61
gtag('js', new Date());
Syntax not understood
62
gtag('config', 'G-TBJTNQEBJ1');
Syntax not understood
63
</script>
Syntax not understood
65
<meta
Syntax not understood
66
property="og:title"
Unknown directive
67
content="WebToppings: spice up your browsing!"
Unknown directive
68
/>
Syntax not understood
69
<meta property="og:url" content="https://webtoppings.bar" />
Unknown directive
70
<meta
Syntax not understood
71
property="og:description"
Unknown directive
72
content="WebToppings is a proxy service that can add extra features to any website. It does not require installation and is completely free!"
Syntax not understood
73
/>
Syntax not understood
74
<meta property="og:image" content="https://webtoppings.bar/pizza.png" />
Unknown directive
75
<meta property="og:image:type" content="image/png" />
Unknown directive
76
<meta name="twitter:card" content="summary" />
Unknown directive
78
<title>WebToppings</title>
Syntax not understood
79
<script type="module" crossorigin src="/assets/index.42392481.js"></script>
Syntax not understood
80
<link rel="modulepreload" href="/assets/vendor.c2c71b6d.js">
Syntax not understood
81
<link rel="stylesheet" href="/assets/index.212e81d2.css">
Syntax not understood
82
</head>
Syntax not understood
84
<body>
Syntax not understood
85
<div id="app"></div>
Syntax not understood
87
<!-- This is used just to make Netlify detect the form. It is not actually used by users -->
Syntax not understood
88
<form name='bugreport' style='display: none' method='post'>
Unknown directive
89
<input type="hidden" name="form-name" value="bugreport" />
Syntax not understood
90
<input name="hp-field" />
Syntax not understood
91
<input name="affected-url" type="url" />
Syntax not understood
92
<input name="affected-origin" />
Syntax not understood
94
<select name="report-topping"></select>
Syntax not understood
96
<select name="report-type">
Syntax not understood
97
<option value="unspecified" disabled selected></option>
Syntax not understood
98
<option value="links"></option>
Syntax not understood
99
<option value="images"></option>
Syntax not understood
100
<option value="login"></option>
Syntax not understood
101
<option value="content"></option>
Syntax not understood
102
<option value="blank"></option>
Syntax not understood
103
<option value="other"></option>
Syntax not understood
104
</select>
Syntax not understood
106
<input type="checkbox" name="browser-chromium" value="on" />
Syntax not understood
107
<input type="checkbox" name="browser-gecko" value="on" />
Syntax not understood
108
<input type="checkbox" name="browser-webkit" value="on" />
Syntax not understood
109
<textarea name="steps"></textarea>
Syntax not understood
110
<textarea name="extra"></textarea>
Syntax not understood
111
</form>
Syntax not understood
112
</body>
Syntax not understood
113
</html>
Syntax not understood

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of webtoppings.bar. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of webtoppings.bar on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 66
Performance 67
Accessibility 73
Best Practices 85
SEO 77
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://webtoppings.bar/
Updated: 4th February, 2022

3.41 seconds
First Contentful Paint (FCP)
36%
38%
26%

0.02 seconds
First Input Delay (FID)
96%
3%
1%

Simulate loading on mobile
67

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for webtoppings.bar. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Time to Interactive — 3.7 s
The time taken for the page to become fully interactive.
Speed Index — 2.9 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Webtoppings.bar should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Webtoppings.bar should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Webtoppings.bar should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Webtoppings.bar should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Webtoppings.bar should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 60 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://webtoppings.bar/
59.12
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Webtoppings.bar should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://webtoppings.bar/
630
https://webtoppings.bar/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Webtoppings.bar should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn.iubenda.com/cs/ccpa/stub.js
79
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
35
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 575 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://webtoppings.bar/assets/darkmode.9530b71a.svg
125756
https://webtoppings.bar/assets/webtoppings_front.c8c60398.svg
98658
https://webtoppings.bar/assets/vendor.c2c71b6d.js
97012
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
57586
https://webtoppings.bar/assets/annotation-centered.84fe5136.png
25511
https://webtoppings.bar/assets/privacy-centered.cc55a2eb.png
20094
https://webtoppings.bar/assets/translator-centered.0b5120c3.png
19714
https://webtoppings.bar/assets/pizza.aea082fc.png
16940
https://webtoppings.bar/assets/annotation.3ee7029d.png
15831
https://webtoppings.bar/assets/index.42392481.js
13751
Uses efficient cache policy on static assets — 1 resource found
Webtoppings.bar can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.iubenda.com/cookie-solution/confs/js/25094004.js
86400000
788
Avoids an excessive DOM size — 341 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
341
Maximum DOM Depth
15
Maximum Child Elements
11
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Webtoppings.bar should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Unattributable
612.808
36.628
0.656
https://webtoppings.bar/
512.192
17.044
5.532
https://webtoppings.bar/assets/vendor.c2c71b6d.js
492.696
464.964
4.376
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
125.228
87.112
19.272
https://cdn.iubenda.com/cs/ccpa/stub.js
57.916
48.064
5.756
Minimizes main-thread work — 1.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
662.784
Other
527.284
Style & Layout
409.82
Rendering
171.104
Script Parsing & Compilation
39.76
Parse HTML & CSS
24.14
Garbage Collection
4.172
Keep request counts low and transfer sizes small — 31 requests • 575 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
31
588548
Image
17
390650
Script
6
171803
Font
1
12320
Stylesheet
5
10465
Document
1
2581
Other
1
729
Media
0
0
Third-party
8
78444
Minimize third-party usage — Third-party code blocked the main thread for 10 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
61040
5.876
14905
0
2499
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
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.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.001365234375
0.001365234375
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 6 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://webtoppings.bar/assets/vendor.c2c71b6d.js
3210
506
Unattributable
1189
162
https://webtoppings.bar/
630
113
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
3090
95
https://webtoppings.bar/
844
76
Unattributable
782
62
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of webtoppings.bar on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://webtoppings.bar/
http/1.1
0
48.909000004642
729
0
301
text/plain
https://webtoppings.bar/
h2
49.306999979308
107.43499998352
2581
5275
200
text/html
Document
https://cdn.iubenda.com/cs/ccpa/stub.js
h2
126.49100000272
149.2529999814
1943
4106
200
application/javascript
Script
https://cdn.iubenda.com/cs/iubenda_cs.js
h2
127.16499998351
151.32199999061
723
591
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.1/normalize.css
h2
127.25999997929
161.0679999867
2499
6138
200
text/css
Stylesheet
https://webtoppings.bar/main.css
h2
127.35299998894
208.34599999944
1647
2418
200
text/css
Stylesheet
https://webtoppings.bar/assets/index.42392481.js
h2
127.45699999505
181.81399998139
13751
36118
200
application/javascript
Script
https://webtoppings.bar/assets/vendor.c2c71b6d.js
h2
127.55199999083
333.00600000075
97012
274390
200
application/javascript
Script
https://webtoppings.bar/assets/index.212e81d2.css
h2
127.72200000472
330.99600000423
3734
9972
200
text/css
Stylesheet
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
h2
158.91899997951
192.43500000448
57586
277423
200
application/javascript
Script
https://www.iubenda.com/cookie-solution/confs/js/25094004.js
h2
226.93999999319
273.30800000345
788
159
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Nunito+Sans
h2
227.86799998721
245.91900000814
1289
1643
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Nunito
h2
228.36300000199
246.32299999939
1296
1653
200
text/css
Stylesheet
https://webtoppings.bar/assets/webtoppings_front.c8c60398.svg
h2
489.02300000191
548.23200000101
98658
314101
200
image/svg+xml
Image
https://webtoppings.bar/assets/chef.d67d3e54.png
h2
489.27600000752
540.78399998252
7552
6698
200
image/png
Image
https://webtoppings.bar/assets/pizza.aea082fc.png
h2
489.49000000721
527.24399999715
16940
16093
200
image/png
Image
https://webtoppings.bar/assets/privacy-centered.cc55a2eb.png
h2
489.70499998541
589.08999999403
20094
19253
200
image/png
Image
https://webtoppings.bar/assets/privacy.64c639c6.png
h2
490.68899999838
594.16399998008
12986
12143
200
image/png
Image
https://webtoppings.bar/assets/annotation-centered.84fe5136.png
h2
490.86200000602
536.94200000609
25511
24666
200
image/png
Image
https://webtoppings.bar/assets/annotation.3ee7029d.png
h2
490.98000000231
536.38000000501
15831
14984
200
image/png
Image
https://webtoppings.bar/assets/translator-centered.0b5120c3.png
h2
491.76800000714
632.09699999425
19714
18875
200
image/png
Image
https://webtoppings.bar/assets/translator.0b8fe40b.png
h2
492.10199998925
541.17599999881
12641
11794
200
image/png
Image
https://webtoppings.bar/assets/darkmode-centered.6da5dd92.png
h2
492.35499999486
541.49299999699
13384
12535
200
image/png
Image
https://webtoppings.bar/assets/darkmode.9530b71a.svg
h2
492.72399998154
557.99800000386
125756
277643
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-sepia.0377f712.svg
h2
493.11300000409
554.50899997959
1626
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-night.326b062d.svg
h2
493.37099998957
535.77600000426
1619
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-noir.7add3fa7.svg
h2
493.68899999536
632.55999999819
1617
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/darkmode-contrast.e8a81854.svg
h2
493.94200000097
528.17299999879
1624
3261
200
image/svg+xml
Image
https://webtoppings.bar/assets/surfly-logo.bdbb80b1.svg
h2
494.27100000321
527.84599998267
5952
12887
200
image/svg+xml
Image
https://webtoppings.bar/assets/bg_pizza.8caadc70.svg
h2
495.11899999925
538.50999998394
9145
20734
200
image/svg+xml
Image
https://fonts.gstatic.com/s/nunitosans/v11/pe0qMImSLYBIv1o4X1M8cce9I9tAcVwo.woff2
h2
499.47599999723
504.55399998464
12320
11380
200
font/woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
167.681
10.095
215.199
12.675
259.649
23.843
331.764
8.244
427.103
5.107
432.223
126.524
558.766
56.672
619.369
7.539
626.921
19.649
663.171
14.613
690.336
8.691
699.285
40.38
739.856
15.411
763.818
5.415
775.401
19.01
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.9 s
The time taken for the first image or text on the page to be rendered.
Total Blocking Time — 500 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Audits

First Meaningful Paint — 2.9 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 99 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://webtoppings.bar/assets/vendor.c2c71b6d.js
97012
59050
https://cdn.iubenda.com/cookie_solution/iubenda_cs/1.36.1/core-en.js
57586
42119
Serve images in next-gen formats — Potential savings of 104 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://webtoppings.bar/assets/annotation-centered.84fe5136.png
24666
20873.4
https://webtoppings.bar/assets/privacy-centered.cc55a2eb.png
19253
16367.7
https://webtoppings.bar/assets/translator-centered.0b5120c3.png
18875
16018.95
https://webtoppings.bar/assets/pizza.aea082fc.png
16093
13011.8
https://webtoppings.bar/assets/annotation.3ee7029d.png
14984
11282.5
https://webtoppings.bar/assets/darkmode-centered.6da5dd92.png
12535
10521.8
https://webtoppings.bar/assets/privacy.64c639c6.png
12143
9372.25
https://webtoppings.bar/assets/translator.0b8fe40b.png
11794
9031.9

Metrics

Largest Contentful Paint — 4.3 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 510 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 1,050 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Webtoppings.bar should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.1/normalize.css
2499
780
https://cdn.iubenda.com/cs/ccpa/stub.js
1943
780
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/nunitosans/v11/pe0qMImSLYBIv1o4X1M8cce9I9tAcVwo.woff2
5.0779999874067
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://webtoppings.bar/assets/surfly-logo.bdbb80b1.svg
First Contentful Paint (3G) — 6060 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of webtoppings.bar. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Webtoppings.bar may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Failing Elements
ARIA IDs are not unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Failing Elements

Contrast

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that webtoppings.bar should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://webtoppings.bar/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://webtoppings.bar/assets/chef.d67d3e54.png
60 x 136
60 x 136
120 x 272
77

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for webtoppings.bar. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of webtoppings.bar on mobile screens.
Document uses legible font sizes — 99.98% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.new-topping
0.02%
10.8px
99.98%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — 101 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
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
<link
Syntax not understood
6
rel="icon"
Syntax not understood
7
type="image/svg+xml"
Syntax not understood
8
href="/assets/pizza.aea082fc.png"
Syntax not understood
9
/>
Syntax not understood
10
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
Syntax not understood
12
<script type="text/javascript">
Syntax not understood
13
var _iub = _iub || [];
Syntax not understood
14
_iub.csConfiguration = {"enableCcpa":true,"countryDetection":true,"invalidateConsentWithoutLog":true,"consentOnContinuedBrowsing":false,"ccpaAcknowledgeOnDisplay":true,"lang":"en","siteId":2463150,"floatingPreferencesButtonDisplay":false,"cookiePolicyId":25094004, "banner":{ "closeButtonDisplay":false,"acceptButtonDisplay":true,"customizeButtonDisplay":true,"acceptButtonColor":"#488646","acceptButtonCaptionColor":"white","customizeButtonColor":"#919191","customizeButtonCaptionColor":"white","rejectButtonDisplay":true,"rejectButtonColor":"#443e3e","rejectButtonCaptionColor":"white","listPurposes":true,"explicitWithdrawal":true,"position":"float-bottom-left","textColor":"#757575","backgroundColor":"#ebe7dc" }};
Unknown directive
15
</script>
Syntax not understood
16
<script type="text/javascript" src="//cdn.iubenda.com/cs/ccpa/stub.js"></script>
Syntax not understood
17
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>
Syntax not understood
19
<link
Syntax not understood
20
rel="stylesheet"
Syntax not understood
21
href="https://cdnjs.cloudflare.com/ajax/libs/normalize/8.0.1/normalize.css"
Unknown directive
22
/>
Syntax not understood
23
<link
Syntax not understood
24
rel="stylesheet"
Syntax not understood
25
href="/main.css"
Syntax not understood
26
/>
Syntax not understood
28
<!-- Hotjar Tracking Code for https://webtoppings.bar -->
Unknown directive
29
<script
Syntax not understood
30
comment="attributes below enable automatic blocking by iubenda"
Syntax not understood
31
class="_iub_cs_activate-inline" type="text/plain"
Syntax not understood
32
>
Syntax not understood
33
if (location.origin === 'https://webtoppings.bar') {
Unknown directive
34
(function (h, o, t, j, a, r) {
Syntax not understood
35
h.hj =
Syntax not understood
36
h.hj ||
Syntax not understood
37
function () {
Syntax not understood
38
(h.hj.q = h.hj.q || []).push(arguments);
Syntax not understood
39
};
Syntax not understood
40
h._hjSettings = { hjid: 2401001, hjsv: 6 };
Unknown directive
41
a = o.getElementsByTagName('head')[0];
Syntax not understood
42
r = o.createElement('script');
Syntax not understood
43
r.async = 1;
Syntax not understood
44
r.src = t + h._hjSettings.hjid + j + h._hjSettings.hjsv;
Syntax not understood
45
a.appendChild(r);
Syntax not understood
46
})(
Syntax not understood
47
window,
Syntax not understood
48
document,
Syntax not understood
49
'https://static.hotjar.com/c/hotjar-',
Unknown directive
50
'.js?sv=',
Syntax not understood
51
);
Syntax not understood
52
}
Syntax not understood
53
</script>
Syntax not understood
55
<script class="_iub_cs_activate" type="text/plain" src="https://www.googleoptimize.com/optimize.js?id=OPT-598LG6H"></script>
Unknown directive
57
<script class="_iub_cs_activate" type="text/plain" async src="https://www.googletagmanager.com/gtag/js?id=G-TBJTNQEBJ1"></script>
Unknown directive
58
<script class="_iub_cs_activate-inline" type="text/plain">
Syntax not understood
59
window.dataLayer = window.dataLayer || [];
Syntax not understood
60
function gtag(){dataLayer.push(arguments);}
Syntax not understood
61
gtag('js', new Date());
Syntax not understood
62
gtag('config', 'G-TBJTNQEBJ1');
Syntax not understood
63
</script>
Syntax not understood
65
<meta
Syntax not understood
66
property="og:title"
Unknown directive
67
content="WebToppings: spice up your browsing!"
Unknown directive
68
/>
Syntax not understood
69
<meta property="og:url" content="https://webtoppings.bar" />
Unknown directive
70
<meta
Syntax not understood
71
property="og:description"
Unknown directive
72
content="WebToppings is a proxy service that can add extra features to any website. It does not require installation and is completely free!"
Syntax not understood
73
/>
Syntax not understood
74
<meta property="og:image" content="https://webtoppings.bar/pizza.png" />
Unknown directive
75
<meta property="og:image:type" content="image/png" />
Unknown directive
76
<meta name="twitter:card" content="summary" />
Unknown directive
78
<title>WebToppings</title>
Syntax not understood
79
<script type="module" crossorigin src="/assets/index.42392481.js"></script>
Syntax not understood
80
<link rel="modulepreload" href="/assets/vendor.c2c71b6d.js">
Syntax not understood
81
<link rel="stylesheet" href="/assets/index.212e81d2.css">
Syntax not understood
82
</head>
Syntax not understood
84
<body>
Syntax not understood
85
<div id="app"></div>
Syntax not understood
87
<!-- This is used just to make Netlify detect the form. It is not actually used by users -->
Syntax not understood
88
<form name='bugreport' style='display: none' method='post'>
Unknown directive
89
<input type="hidden" name="form-name" value="bugreport" />
Syntax not understood
90
<input name="hp-field" />
Syntax not understood
91
<input name="affected-url" type="url" />
Syntax not understood
92
<input name="affected-origin" />
Syntax not understood
94
<select name="report-topping"></select>
Syntax not understood
96
<select name="report-type">
Syntax not understood
97
<option value="unspecified" disabled selected></option>
Syntax not understood
98
<option value="links"></option>
Syntax not understood
99
<option value="images"></option>
Syntax not understood
100
<option value="login"></option>
Syntax not understood
101
<option value="content"></option>
Syntax not understood
102
<option value="blank"></option>
Syntax not understood
103
<option value="other"></option>
Syntax not understood
104
</select>
Syntax not understood
106
<input type="checkbox" name="browser-chromium" value="on" />
Syntax not understood
107
<input type="checkbox" name="browser-gecko" value="on" />
Syntax not understood
108
<input type="checkbox" name="browser-webkit" value="on" />
Syntax not understood
109
<textarea name="steps"></textarea>
Syntax not understood
110
<textarea name="extra"></textarea>
Syntax not understood
111
</form>
Syntax not understood
112
</body>
Syntax not understood
113
</html>
Syntax not understood

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of webtoppings.bar. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of webtoppings.bar on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 104.21.58.156
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Surfly
Country: NL
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Key-Systems, LLC 172.67.15.178
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: webtoppings.bar
Issued By: WE1
Valid From: 8th November, 2024
Valid To: 6th February, 2025
Subject: CN = webtoppings.bar
Hash: 143fd9a9
Issuer: CN = WE1
O = Google Trust Services
S = US
Version: 2
Serial Number: 26349853386963991607159956687278976413
Serial Number (Hex): 13D2CC131FDF58760DF36C38DB322D9D
Valid From: 8th November, 2024
Valid To: 6th February, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:90:77:92:35:67:C4:FF:A8:CC:A9:E6:7B:D9:80:79:7B:CC:93:F9:38
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://c.pki.goog/we1/FucB3_abY94.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://o.pki.goog/s/we1/E9I
CA Issuers - URI:http://i.pki.goog/we1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
Timestamp : Nov 8 10:41:14.831 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:63:30:80:2F:65:67:64:95:6D:ED:B4:35:
3A:26:C0:2E:C1:B5:7C:0E:B0:B9:71:AA:64:E1:7F:E2:
90:AC:36:0E:02:20:44:68:CD:40:37:57:4F:6D:42:49:
CC:1A:02:3B:1A:22:D6:31:1F:5E:A8:EC:ED:35:E1:20:
64:A0:DA:8E:D9:CD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
Timestamp : Nov 8 10:41:14.796 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:25:E2:FA:1B:C6:E1:4A:EA:29:7D:BA:43:
B1:21:9E:0B:3A:08:36:82:59:56:E6:E6:4A:FE:F9:67:
D8:F8:34:73:02:21:00:99:B6:54:57:A7:89:09:71:75:
E4:DE:59:4C:90:F8:60:DF:1D:A7:D7:79:5F:F9:B2:33:
30:9B:48:BF:8E:52:67
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.webtoppings.bar
DNS:webtoppings.bar
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/2 200
date: 14th November, 2024
content-type: text/html; charset=UTF-8
cache-control: public,max-age=0,must-revalidate
server: cloudflare
age: 15138
cache-status: "Netlify Edge"; hit
vary: Accept-Encoding
x-nf-request-id: 01JCP0HZKCBTANACWJQPXJETP7
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=n75991eCFUN3eQj1UFZLkCDe5BDjVV8%2FKB6L9rS7dH32uIHJKF97bxafNJNcI8AQe1GEKo4ZCgvNDcMFFaTstsyMnalcXQKQA5%2BZxlPLhK9bKeM8vlYprh4N2HawahHQGcw%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
cf-ray: 8e29393688f4c5b7-IAD
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=1009&sent=6&recv=10&lost=0&retrans=0&sent_bytes=3397&recv_bytes=921&delivery_rate=2901803&cwnd=243&unsent_bytes=0&cid=3d90ed554193691f&ts=101&x=0"

Whois Lookup

Created: 21st March, 2021
Changed: 5th June, 2024
Expires: 21st March, 2025
Registrar: Key-Systems, LLC
Status: ok
Nameservers: clark.ns.cloudflare.com
jillian.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Surfly
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner Country: NL
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Post Code: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: webtoppings.bar
Registry Domain ID: D229298058-CNIC
Registrar WHOIS Server: http://www.key-systems.net
Registrar URL: http://www.key-systems.net
Updated Date: 2024-05-06T00:00:21.560Z
Creation Date: 2021-03-21T13:35:55.000Z
Registry Expiry Date: 2025-03-21T23:59:59.000Z
Registrar: Key-Systems, LLC
Registrar IANA ID: 1345
Registrar Abuse Contact Email: info@key-systems.net
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Surfly
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: NL
Registrant Phone: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: clark.ns.cloudflare.com
Name Server: jillian.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN RDDS Inaccuracy Complaint Form: https://www.icann.org/wicf/

>>> Last update of WHOIS database: 2024-11-14T18:56:48.619Z <<<

For more information on domain status codes, please visit https://icann.org/epp

The WHOIS information provided in this page has been redacted
in compliance with ICANN's Temporary Specification for gTLD
Registration Data.

The data in this record is provided by Uniregistry for informational
purposes only, and it does not guarantee its accuracy. Uniregistry is
authoritative for whois information in top-level domains it operates
under contract with the Internet Corporation for Assigned Names and
Numbers. Whois information from other top-level domains is provided by
a third-party under license to Uniregistry.

This service is intended only for query-based access. By using this
service, you agree that you will use any data presented only for lawful
purposes and that, under no circumstances will you use (a) data
acquired for the purpose of allowing, enabling, or otherwise supporting
the transmission by e-mail, telephone, facsimile or other
communications mechanism of mass unsolicited, commercial advertising
or solicitations to entities other than your existing customers; or
(b) this service to enable high volume, automated, electronic processes
that send queries or data to the systems of any Registrar or any
Registry except as reasonably necessary to register domain names or
modify existing domain name registrations.

Uniregistry reserves the right to modify these terms at any time. By
submitting this query, you agree to abide by this policy. All rights
reserved.

Nameservers

Name IP Address
clark.ns.cloudflare.com 172.64.33.87
jillian.ns.cloudflare.com 172.64.34.44
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address