perftest.org Open in urlscan Pro
2604:f440:3:24::10  Public Scan

Form analysis
0 forms found in the DOM

Text Content

PERF-TEST


82.3 ms10.006 ms80.948 ms92.753 ms
-._.-*^*-._.-*^*-._.-







PERFORMANCE REPORT FOR:

https://flirt4free.jouwpagina.nl/
Report Generated 2022-11-10 07:59:36
Test Location Charlotte, NC, USA
Using Chromium 104.0.5112.79, Lighthouse 9.6.1
Created with Raphaël 2.2.0480100     Hosting Score
Created with Raphaël 2.2.0950100     Performance Score
Summary
Lighthouse
Hosting/CDN
All Reports


Speed Visualization


0.3 S

0.6 S

0.9 S

1.2 S

1.5 S

1.8 S

2.1 S

2.4 S

2.7 S

3 S

TTFB: 0.118 s
Redirect: 0 ms
Backend: 118ms
First Contentful Paint: 1.072 sTime to Interactive:1.072 sFully Loaded Time: 3 s
Onload Time: 1.811 sLargest Contentful Paint: 1.072 s

SUMMARY...
WebServer Location
null, null, FR, ✅
IPv4 connetivity
213.32.56.137 ✅
IPv6 connectivity
❌
HTTP response time
0.060 s ✅
HTTPS response time
28.328 s ✅
ISP of hosting
OVH SAS ✅
CDN Detected?



https://flirt4free.jouwpagina.nl/
العربية – Arabicالعربية (لكنات تجريبية ثنائية الاتجاه) – Arabic
(Pseudo-Bidi)български – Bulgariancatalà – Catalančeština – Czechdansk –
DanishDeutsch – GermanΕλληνικά – GreekBritish EnglishAmerican EnglishEnglish
(Pseudo-Accents)English (XL)español – Spanishespañol latinoamericano – Latin
American Spanishsuomi – FinnishFilipinofrançais – Frenchעברית – Hebrewहिन्दी –
Hindihrvatski – Croatianmagyar – HungarianIndonesia – Indonesianitaliano –
Italian日本語 – Japanese한국어 – Koreanlietuvių – Lithuanianlatviešu –
LatvianNederlands – Dutchnorsk – Norwegianpolski – Polishportuguês –
Portugueseportuguês europeu – European Portugueseromână – Romanianрусский –
Russianslovenčina – Slovakslovenščina – Slovenianсрпски – Serbiansrpski
(latinica) – Serbian (Latin)svenska – Swedishதமிழ் – Tamilతెలుగు – Teluguไทย –
ThaiTürkçe – Turkishукраїнська – UkrainianTiếng Việt – Vietnamese中文 –
Chinese中文（香港） – Chinese (Hong Kong)中文（台灣） – Chinese (Taiwan)
Print Summary Print Expanded Copy JSON Save as HTML Save as JSON Open in Viewer
Save as Gist Toggle Dark Theme
95
Performance

68
Accessibility

75
Best Practices

92
SEO
PWA

95
Performance

68
Accessibility

75
Best Practices

92
SEO
PWA
95
Performance
Values are estimated and may vary. The performance score is calculated directly
from these metrics.See calculator.
0–49 50–89 90–100


MetricsExpand viewCollapse view

First Contentful Paint
1.1 s
First Contentful Paint marks the time at which the first text or image is
painted. Learn more.

Time to Interactive
1.1 s
Time to interactive is the amount of time it takes for the page to become fully
interactive. Learn more.

Speed Index
1.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Learn more.

Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length
exceeded 50ms, expressed in milliseconds. Learn more.

Largest Contentful Paint
1.1 s
Largest Contentful Paint marks the time at which the largest text or image is
painted. Learn more

Cumulative Layout Shift
0.008
Cumulative Layout Shift measures the movement of visible elements within the
viewport. Learn more.
View Treemap

Show audits relevant to:AllFCPTBTLCPCLS
Opportunities
Opportunity
Estimated Savings
Eliminate render-blocking resources
0.50 sec

Resources are blocking the first paint of your page. Consider delivering
critical JS/CSS inline and deferring all non-critical JS/styles. Learn
more.FCPLCP

Show 3rd-party resources (2)
URL
Transfer Size
Potential Savings
…glossy/responsiveness.css
(jouwpagina.nl)
2.1 KiB
530 ms
…css/font-awesome.min.css
(maxcdn.bootstrapcdn.com)
6.6 KiB
260 ms
…2.1.4/jquery.min.js
(ajax.googleapis.com)
29.7 KiB
280 ms
…glossy/resizer.js
(jouwpagina.nl)
1.2 KiB
520 ms

These suggestions can help your page load faster. They don't directly affect the
Performance score.
Diagnostics
Image elements do not have explicit width and height

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

Show 3rd-party resources (0)
URL

header > div.langflags > a > img
<img src="https://jouwpagina.nl/misc/img/flags/flag_nl.png" height="25">
…flags/flag_nl.png
(jouwpagina.nl)

Avoid chaining critical requests 4 chains found

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

Maximum critical path latency: 1,573.649 ms
Initial Navigation
https://flirt4free.jouwpagina.nl
…glossy/responsiveness.css
(jouwpagina.nl)
- 629.926 ms, 2.06 KiB
…css/font-awesome.min.css
(maxcdn.bootstrapcdn.com)
- 82.86 ms, 6.61 KiB
…2.1.4/jquery.min.js
(ajax.googleapis.com)
- 24.054 ms, 29.73 KiB
…glossy/resizer.js
(jouwpagina.nl)
- 631.17 ms, 1.15 KiB
Keep request counts low and transfer sizes small 7 requests • 55 KiB

To set budgets for the quantity and size of page resources, add a budget.json
file. Learn more.

Resource Type
Requests
Transfer Size
Total
7.0
54.9 KiB
Script
2.0
30.9 KiB
Document
1.0
10.8 KiB
Stylesheet
2.0
8.7 KiB
Image
2.0
4.5 KiB
Media
0.0
0.0 KiB
Font
0.0
0.0 KiB
Other
0.0
0.0 KiB
Third-party
2.0
36.3 KiB

Largest Contentful Paint element 1 element found

This is the largest contentful element painted within the viewport. Learn
MoreLCP

Element

Interactive Sex Toy Cam Shows Have you been longing to interact more closely wi…
<p>

Avoid large layout shifts 2 elements found

These DOM elements contribute most to the CLS of the page.CLS

Element
CLS Contribution

Flirt4free Home Alphabet Categories Submit link Exchange link Advertise Login …
<div id="container">
0.008

div#container > div#header > header > div.langflags
<div class="langflags" style="">
0.000

More information about the performance of your application. These numbers don't
directly affect the Performance score.
Passed audits (33)
Show Hide
Properly size images

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

Defer offscreen images

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

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn
more.FCPLCP

Reduce unused CSS

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

Reduce unused JavaScript

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

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn more.

Serve images in next-gen formats

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

Enable text compression

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

Preconnect to required origins

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early
connections to important third-party origins. Learn more.FCPLCP

Initial server response time was short Root document took 120 ms

Keep the server response time for the main document short because all other
requests depend on it. Learn more.FCPLCP

Show 3rd-party resources (0)
URL
Time Spent
https://flirt4free.jouwpagina.nl
120 ms

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn
more.FCPLCP

Preload key requests

Consider using `<link rel=preload>` to prioritize fetching resources that are
currently requested later in page load. Learn more.FCPLCP

Use video formats for animated content

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

Remove duplicate modules in JavaScript bundles

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

Avoid serving legacy JavaScript to modern browsers

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

Preload Largest Contentful Paint image

Preload the image used by the LCP element in order to improve your LCP time.
Learn more.LCP

Avoids enormous network payloads Total size was 55 KiB

Large network payloads cost users real money and are highly correlated with long
load times. Learn more.LCP

Show 3rd-party resources (2)
URL
Transfer Size
…2.1.4/jquery.min.js
(ajax.googleapis.com)
29.7 KiB
https://flirt4free.jouwpagina.nl
10.8 KiB
…css/font-awesome.min.css
(maxcdn.bootstrapcdn.com)
6.6 KiB
…flags/flag_nl.png
(jouwpagina.nl)
3.1 KiB
…glossy/responsiveness.css
(jouwpagina.nl)
2.1 KiB
…glossy/arrow.svg
(jouwpagina.nl)
1.4 KiB
…glossy/resizer.js
(jouwpagina.nl)
1.2 KiB

Uses efficient cache policy on static assets 0 resources found

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

Avoids an excessive DOM size 486 elements

A large DOM will increase memory usage, cause longer style calculations, and
produce costly layout reflows. Learn more.TBT

Statistic
Element
Value
Total DOM Elements
486.0
Maximum DOM Depth
div.main > ul > li > img.svg
<img src="https://jouwpagina.nl/templates/glossy/arrow.svg" class="svg arrow">
11.0
Maximum Child Elements

FLIRT4 flirt4 Hi guys, I will tell you a little about myself and what I likern…
<div id="colLeft">
58.0

User Timing marks and measures

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

JavaScript execution time 0.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may
find delivering smaller JS payloads helps with this. Learn more.TBT

Show 3rd-party resources (0)
URL
Total CPU Time
Script Evaluation
Script Parse
https://flirt4free.jouwpagina.nl
78 ms
2 ms
1 ms

Minimizes main-thread work 0.1 s

Consider reducing the time spent parsing, compiling and executing JS. You may
find delivering smaller JS payloads helps with this. Learn moreTBT

Category
Time Spent
Style & Layout
52 ms
Other
39 ms
Script Evaluation
16 ms
Rendering
11 ms
Parse HTML & CSS
6 ms
Script Parsing & Compilation
2 ms

All text remains visible during webfont loads

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

Minimize third-party usage Third-party code blocked the main thread for 0 ms

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

Show 3rd-party resources (0)
Third-Party
Transfer Size
Main-Thread Blocking Time
Google CDN
30 KiB
0 ms
…2.1.4/jquery.min.js
(ajax.googleapis.com)
30 KiB
0 ms
Bootstrap CDN
7 KiB
0 ms
…css/font-awesome.min.css
(maxcdn.bootstrapcdn.com)
7 KiB
0 ms

Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a
facade until they are required. Learn more.TBT

Largest Contentful Paint image was not lazily loaded

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

Uses passive listeners to improve scrolling performance

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

Avoids document.write()

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

Avoid long main-thread tasks

Lists the longest tasks on the main thread, useful for identifying worst
contributors to input delay. Learn moreTBT

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn moreCLS

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

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

Avoids unload event listeners

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

68
Accessibility
These checks highlight opportunities to improve the accessibility of your web
app. Only a subset of accessibility issues can be automatically detected so
manual testing is also encouraged.
Names and labels
Image elements do not have [alt] attributes

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

Failing Elements

header > div.langflags > a > img
<img src="https://jouwpagina.nl/misc/img/flags/flag_nl.png" height="25">

Links do not have a discernible name

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

Failing Elements

div#header > header > div.langflags > a
<a href="https://jouwpagina.nl/?l=&amp;lang=nl">
div.main > ul > li > a.frelnk
<a href="https://flirt4.cam/tagged/interactivetoy/" target="_blank"
class="frelnk normallink">

These are opportunities to improve the semantics of the controls in your
application. This may enhance the experience for users of assistive technology,
like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.

Low-contrast text is difficult or impossible for many users to read. Learn more.

Failing Elements

Home
<a href="https://jouwpagina.nl/">

body
<body>

Alphabet
<a href="https://jouwpagina.nl/alphabet">

body
<body>

Categories
<a href="https://jouwpagina.nl/category">

body
<body>

Submit link
<a href="https://jouwpagina.nl/submit-link/">

body
<body>

Exchange link
<a href="https://jouwpagina.nl/changerequest.php">

body
<body>

Advertise
<a href="https://jouwpagina.nl/register.php">

body
<body>

Login
<a href="https://jouwpagina.nl/login.php">

body
<body>

Contact
<a href="https://jouwpagina.nl/contact/flirt4free" class="lastitem">

body
<body>

These are opportunities to improve the legibility of your content.
Tables and lists
Lists do not contain only <li> elements and script supporting elements (<script>
and <template>).

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

Failing Elements

flirt4free latina Flirt4 Flirt4free
<ul>
div.block > div.main > ul > a
<a name="l14930823">
div.block > div.main > ul > a
<a name="l14941485">
div.block > div.main > ul > a
<a name="l14953733">

flirt4 guy Fetish gay kink Gay 4 Gay livesexasian Gay performer of the yea…
<ul>
div.block > div.main > ul > a
<a name="l14944922">
div.block > div.main > ul > a
<a name="l14944924">
div.block > div.main > ul > a
<a name="l14944925">

Chaterbait
<ul>
div.block > div.main > ul > a
<a name="l14949734">

Cloe raven nude
<ul>
div.block > div.main > ul > a
<a name="l14960632">

Curie nude
<ul>
div.block > div.main > ul > a
<a name="l14960630">

Fliirt4free Flirt 4 cam Flirt4free live Www flirt4free com rooms
<ul>
div.block > div.main > ul > a
<a name="l14911359">
div.block > div.main > ul > a
<a name="l14911360">
div.block > div.main > ul > a
<a name="l14826247">

Flirt 4 free Helen stanley nude
<ul>
div.block > div.main > ul > a
<a name="l14937932">
div.block > div.main > ul > a
<a name="l14953758">

Flirt 4 free cam models
<ul>
div.block > div.main > ul > a
<a name="l14928443">

Flirt4 chat
<ul>
div.block > div.main > ul > a
<a name="l14930820">

Chatterbate Flirt4free amanda bond
<ul>
div.block > div.main > ul > a
<a name="l14996082">
div.block > div.main > ul > a
<a name="l14937918">

4k american girls American girls flirt xvid American pige flirt4 Bryster am…
<ul>
div.block > div.main > ul > a
<a name="l14930805">
div.block > div.main > ul > a
<a name="l14930814">
div.block > div.main > ul > a
<a name="l14930809">

Flirt4free calendar
<ul>
div.block > div.main > ul > a
<a name="l14930816">

Flirt4free cam2cam
<ul>
div.block > div.main > ul > a
<a name="l14930821">

Flirt4free chat
<ul>
div.block > div.main > ul > a
<a name="l14930819">

Flirt cam Flirt4free live Mfc free cam
<ul>
div.block > div.main > ul > a
<a name="l15003881">
div.block > div.main > ul > a
<a name="l14930818">
div.block > div.main > ul > a
<a name="l15003878">

Flirt4free private show
<ul>
div.block > div.main > ul > a
<a name="l14930799">

Flirt4free rooms MAJEK MOOR flirt4free
<ul>
div.block > div.main > ul > a
<a name="l14930817">
div.block > div.main > ul > a
<a name="l14930822">

Flirt4free vip
<ul>
div.block > div.main > ul > a
<a name="l14930798">

Interactive
<ul>
div.block > div.main > ul > a
<a name="l15003876">


<ul>
div.block > div.main > ul > a
<a name="l15003875">

69 pose chaturbate 69 sex cams Jasmin live Xvid camsex video chat
<ul>
div.block > div.main > ul > a
<a name="l15003880">
div.block > div.main > ul > a
<a name="l15003879">
div.block > div.main > ul > a
<a name="l14953628">

Julian bradly flirt4free
<ul>
div.block > div.main > ul > a
<a name="l14928446">

Logan hugh flirt4free
<ul>
div.block > div.main > ul > a
<a name="l14928445">

Mia melano nude
<ul>
div.block > div.main > ul > a
<a name="l14954490">

Milfcams
<ul>
div.block > div.main > ul > a
<a name="l14962198">

Nezuko nude
<ul>
div.block > div.main > ul > a
<a name="l14942198">

Onlyfun
<ul>
div.block > div.main > ul > a
<a name="l14947311">

Sheila larken nude
<ul>
div.block > div.main > ul > a
<a name="l14937917">

These are opportunities to improve the experience of reading tabular or list
data using assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
The page has a logical tab order

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

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus
indicator. Learn more.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and
be distinguishable from non-interactive elements. Learn more.

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

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

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally
trapping their focus. Learn more.

Custom controls have associated labels

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

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn more.

Visual order on the page follows DOM order

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

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn more.

HTML5 landmark elements are used to improve navigation

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

These items address areas which an automated testing tool cannot cover. Learn
more in our guide on conducting an accessibility review.
Passed audits (9)
Show Hide
[aria-hidden="true"] is not present on the document <body>

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

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

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

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

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

Document has a <title> element

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

[id] attributes on active, focusable elements are unique

All focusable elements must have a unique `id` to ensure that they're visible to
assistive technologies. Learn more.

<html> element has a [lang] attribute

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

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

Specifying a valid BCP 47 language helps screen readers announce text properly.
Learn more.

List items (<li>) are contained within <ul> or <ol> parent elements

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

Heading elements appear in a sequentially-descending order

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

Not applicable (31)
Show Hide
[accesskey] values are unique

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

[aria-*] attributes match their roles

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching
these invalidates the `aria-*` attributes. Learn more.

button, link, and menuitem elements have accessible names

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

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

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

ARIA input fields have accessible names

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

ARIA meter elements have accessible names

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

ARIA progressbar elements have accessible names

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

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

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

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

Some ARIA parent roles must contain specific child roles to perform their
intended accessibility functions. Learn more.

[role]s are contained by their required parent element

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

[role] values are valid

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

ARIA toggle fields have accessible names

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

ARIA tooltip elements have accessible names

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

ARIA treeitem elements have accessible names

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

[aria-*] attributes have valid values

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

[aria-*] attributes are valid and not misspelled

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

Buttons have an accessible name

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

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

When definition lists are not properly marked up, screen readers may produce
confusing or inaccurate output. Learn more.

Definition list items are wrapped in <dl> elements

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

ARIA IDs are unique

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

No form fields have multiple labels

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

<frame> or <iframe> elements have a title

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

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

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

Form elements have associated labels

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

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

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

<object> elements have alternate text

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

No element has a [tabindex] value greater than 0

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

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

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

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

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

[lang] attributes have a valid value

Specifying a valid BCP 47 language on elements helps ensure that text is
pronounced correctly by a screen reader. Learn more.

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

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

75
Best Practices

Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities 4
vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are
easily identified and exploited by attackers. Learn more.

Library Version
Vulnerability Count
Highest Severity
jQuery@2.1.4
4
Medium

Ensure CSP is effective against XSS attacks

A strong Content Security Policy (CSP) significantly reduces the risk of
cross-site scripting (XSS) attacks. Learn more

Description
Directive
Severity
No CSP found in enforcement mode
High

Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Expected publicId to be an empty string

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

General
Browser errors were logged to the console

Errors logged to the console indicate unresolved problems. They can come from
network request failures and other browser concerns. Learn more

Show 3rd-party resources (0)
Source
Description
https://flirt4free.jouwpagina.nl:49:0

ReferenceError: jQuery is not defined
    at https://flirt4free.jouwpagina.nl/:49:1

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more.

Name
Version
jQuery
2.1.4

Passed audits (10)
Show Hide
Uses HTTPS

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

Avoids requesting the geolocation permission on page load

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

Avoids requesting the notification permission on page load

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

Allows users to paste into password fields

Preventing password pasting undermines good security policy. Learn more.

Displays images with correct aspect ratio

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

Serves images with appropriate resolution

Image natural dimensions should be proportional to the display size and the
pixel ratio to maximize image clarity. Learn more.

Properly defines charset

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

Avoids deprecated APIs

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

No issues in the Issues panel in Chrome Devtools

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

Page has valid source maps

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

Show 3rd-party resources (1)
URL
Map URL
…2.1.4/jquery.min.js
(ajax.googleapis.com)
…2.1.4/jquery.min.map
(ajax.googleapis.com)

Warning: missing 1 item in `.sourcesContent`

Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded

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

92
SEO
These checks ensure that your page is following basic search engine optimization
advice. There are many additional factors Lighthouse does not score here that
may affect your search ranking, including performance on Core Web Vitals. Learn
more.
Content Best Practices
Image elements do not have [alt] attributes

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

Failing Elements

header > div.langflags > a > img
<img src="https://jouwpagina.nl/misc/img/flags/flag_nl.png" height="25">

Format your HTML in a way that enables crawlers to better understand your app’s
content.
Additional items to manually check (1)
Show Hide
Structured data is valid

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

Run these additional validators on your site to check additional SEO best
practices.
Passed audits (11)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale

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

Document has a <title> element

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

Document has a meta description

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

Page has successful HTTP status code

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

Links have descriptive text

Descriptive link text helps search engines understand your content. Learn more.

Links are crawlable

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

Page isn’t blocked from indexing

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

robots.txt is valid

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

Document has a valid hreflang

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

Document has a valid rel=canonical

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

Document avoids plugins

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

Not applicable (2)
Show Hide
Document uses legible font sizes

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

Tap targets are sized appropriately

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

PWA
These checks validate the aspects of a Progressive Web App. Learn more.
Installable
Web app manifest or service worker do not meet the installability requirements 1
reason

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

Failure reason
No manifest was fetched

PWA Optimized
Does not register a service worker that controls page and start_url

The service worker is the technology that enables your app to use many
Progressive Web App features, such as offline, add to homescreen, and push
notifications. Learn more.

Is not configured for a custom splash screen
Failures: No manifest was fetched.

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

Does not set a theme color for the address bar.
Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

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

Content is sized correctly for the viewport

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

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

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

Does not provide a valid apple-touch-icon

For ideal appearance on iOS when users add a progressive web app to the home
screen, define an `apple-touch-icon`. It must point to a non-transparent 192px
(or 180px) square PNG. Learn More.

Manifest doesn't have a maskable icon
No manifest was fetched

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

Additional items to manually check (3)
Show Hide
Site works cross-browser

To reach the most number of users, sites should work across every major browser.
Learn more.

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

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

Each page has a URL

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

These checks are required by the baseline PWA Checklist but are not
automatically checked by Lighthouse. They do not affect your score but it's
important that you verify them manually.
 * Captured at Nov 10, 2022, 12:59 PM GMT
 * Emulated Desktop with Lighthouse 9.6.7
   CPU/Memory Power: 1891 CPU throttling: 1x slowdown (Simulated) Axe version:
   4.4.1
 * Single page load
   This data is taken from a single page load, as opposed to field data
   summarizing many sessions.
 * Initial page load
 * Custom throttling
   Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated)
 * Using HeadlessChromium 107.0.5304.87 with node
   User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)
   AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4695.0 Safari/537.36
   Chrome-Lighthouse"

Generated by Lighthouse 9.6.7 | File an issue



FLIRT4FREE.JOUWPAGINA.NL PING IPV4


Source LocationDestination LocationDestination IP AddressPing Time in
msBahrainnull, null ,FR213.32.56.13782.3London, UKnull, null
,FR213.32.56.13710.006Calgary, Canadanull, null ,FR213.32.56.13780.948Newark,
New Jerseynull, null ,FR213.32.56.13792.753


FLIRT4FREE.JOUWPAGINA.NL PING IPV6


Source LocationDestination LocationDestination IP AddressPing Time in ms

IDcreated atCreate IPURLscreenshotreporttitleDescription17602022-11-10
07:59:362a02:678:6c2:8600:2190:48b0:2ae:1329https://flirt4free.jouwpagina.nl/
View Report

© perftest.org