meetic.fr

meetic.fr is SSL secured

Free website and domain report on meetic.fr

Last Updated: 4th August, 2022 Update Now
Overview

Snoop Summary for meetic.fr

This is a free and comprehensive report about meetic.fr. Meetic.fr is hosted in Paris, Île-de-France in France on a server with an IP address of 62.23.26.24, where EUR is the local currency and the local language is French. Our records indicate that meetic.fr is owned/operated by Meetic. Meetic.fr is expected to earn an estimated $127 USD per day from advertising revenue. The sale of meetic.fr would possibly be worth $92,542 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Meetic.fr is wildly popular with an estimated 29,974 daily unique visitors. This report was last updated 4th August, 2022.

About meetic.fr

Site Preview: meetic.fr meetic.fr
Title: Meetic
Description: Inscrivez-vous gratuitement sur Meetic, site de rencontres sérieux où vous pourrez consulter les profils de milliers de célibataires à travers la France.
Keywords and Tags: dating, exemple sms premier rendez vous, liste de défauts dans un couple, meetic affinity prix, personals, popular, que veut dire trois petit point dans un sms, signes qu il faut rompre
Related Terms: celibataires, profils
Fav Icon:
Age: Over 22 years old
Domain Created: 19th December, 2001
Domain Updated: 7th September, 2021
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$92,542 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 26,085
Alexa Reach:
SEMrush Rank (US): 738,938
SEMrush Authority Score: 57
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 1,782 0
Traffic: 1,308 0
Cost: $52 USD $0 USD
Traffic

Visitors

Daily Visitors: 29,974
Monthly Visitors: 912,312
Yearly Visitors: 10,940,490
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $127 USD
Monthly Revenue: $3,858 USD
Yearly Revenue: $46,266 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 100,069
Referring Domains: 4,032
Referring IPs: 2,658
Meetic.fr has 100,069 backlinks according to SEMrush. 89% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve meetic.fr's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of meetic.fr's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://www.satizfaction.fr/classement-commercants-les-plus-moins-bien-notes?amp%3Bpage=2&page=25&pp=10
Target: http://meetic.fr/

2
Source: http://maplanete.blogs.sudouest.fr/archives/category/pollution/index-153.html/
Target: http://www.meetic.fr/

3
Source: http://maplanete.blogs.sudouest.fr/archives/category/developpement-durable/index-333.html/
Target: http://www.meetic.fr/

4
Source: http://maplanete.blogs.sudouest.fr/archives/category/ecologie/index-335.html/
Target: http://www.meetic.fr/

5
Source: http://maplanete.blogs.sudouest.fr/archives/category/commerce/index-28.html/
Target: http://www.meetic.fr/

Top Ranking Keywords (US)

1
Keyword: signes qu il faut rompre
Ranked Page: https://www.meetic.fr/p/conseils/20-signes-qui-vous-prouvent-quil-est-temps-de-rompre/

2
Keyword: que veut dire trois petit point dans un sms
Ranked Page: https://www.meetic.fr/p/conseils/ponctuation-sms-comment-comprendre/

3
Keyword: meetic affinity prix
Ranked Page: https://www.meetic.fr/faq/quelle-est-la-difference-entre-meetic-et-meetic-affinity/

4
Keyword: exemple sms premier rendez vous
Ranked Page: https://www.meetic.fr/p/conseils/8-sms-quon-adore-recevoir-premier-rendez/

5
Keyword: liste de défauts dans un couple
Ranked Page: https://www.meetic.fr/p/conseils/5-qualites-peuvent-etre-des-defauts-couple/

Domain Analysis

Value Length
Domain: meetic.fr 9
Domain Name: meetic 6
Extension (TLD): fr 2

Page Speed Analysis

Average Load Time: 0.47 seconds
Load Time Comparison: Faster than 96% of sites

PageSpeed Insights

Avg. (All Categories) 86
Performance 85
Accessibility 76
Best Practices 92
SEO 92
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.meetic.fr/
Updated: 4th August, 2022

1.14 seconds
First Contentful Paint (FCP)
88%
6%
6%

0.02 seconds
First Input Delay (FID)
92%
6%
2%

Simulate loading on desktop
85

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 120 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).
Cumulative Layout Shift — 0.025
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 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://meetic.fr/
http/1.1
0
215.75199998915
150
0
302
text/plain
https://meetic.fr/
http/1.1
216.94399998523
1478.7000000069
448
0
301
text/html
https://www.meetic.fr/
http/1.1
1479.7309999994
2770.9169999871
49105
219999
200
text/html
Document
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/positive-75570a615a9.svg
http/1.1
2789.46
3502.6690000086
1206
766
200
image/svg+xml
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/pinkwhite-44d5e901294.svg
http/1.1
2790.1899999997
3453.2619999954
2632
2191
200
image/svg+xml
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/conversational-bot-9d221733c14.png
http/1.1
2808.7020000094
3307.284999988
4031
3594
200
image/png
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
http/1.1
2808.5199999914
3436.7149999889
255217
876229
200
application/javascript
Script
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/large-a94cb755672.webp
http/1.1
2814.2569999909
3539.6360000013
114607
114290
200
image/webp
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-semi-bold-latin.woff2
http/1.1
2817.6579999854
3395.8310000016
20264
19824
200
font/woff2
Font
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-medium-latin.woff2
http/1.1
2819.319000002
3396.4660000056
20308
19868
200
font/woff2
Font
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-bold-latin.woff2
http/1.1
2821.0259999905
3311.8519999844
20480
20040
200
font/woff2
Font
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/arrow-146066c1e41.svg
http/1.1
2935.999999987
3634.5950000104
705
265
200
image/svg+xml
Image
https://www.meetic.fr/apida/oauth/accesstokens
http/1.1
3661.0050000018
4510.0410000014
1090
727
200
application/json
Fetch
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/couples.responsive-77ac646ec32.jpg
http/1.1
3705.6180000072
4199.5839999872
128450
128008
200
image/jpeg
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/audio-bb501bbab3d.png
http/1.1
3741.1879999854
4174.9849999906
21199
20760
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
h2
3752.5430000096
3769.8640000017
43508
113299
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
h2
3752.9470000009
3784.6340000106
78403
249803
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-K3V66S&l=dataLayer
h2
3753.4849999938
3774.0589999885
49890
130424
200
application/javascript
Script
data
3753.3239999902
3753.4349999914
0
34
200
image/webp
Image
https://www.meetic.fr/iojs/general5/static_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
http/1.1
3779.3919999967
4622.3020000034
40510
39996
200
text/javascript
Script
https://mpsnare.iesnare.com/general5/wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
http/1.1
3779.9039999954
3885.1509999949
19364
41806
200
text/javascript
Script
https://tk.ilius.net/tr.gif?lid=www.meetic.fr/hpv&co=000001&med=1&lmc=000001&url=www.meetic.fr&e=tl&fus=&lsid=unl0.4755984807685011659613060522&ts=1659613060522&klid=6944&ktid=0
http/1.1
3785.8359999955
4552.2179999971
323
43
200
image/gif
Image
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
h2
3855.7870000077
3884.5509999956
8080
21599
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
3930.125999992
3934.487999999
20631
50205
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
h2
3938.4870000067
3958.5009999864
73238
204986
200
application/javascript
Script
https://pagead2.googlesyndication.com/pagead/landing?gcs=G100&gcd=G100&rnd=1377040695.1659613061&url=https%3A%2F%2Fwww.meetic.fr%2F&gtm=2wg811WPNZTTN
3946.7019999865
3970.4949999868
0
0
-1
Ping
https://www.googletagmanager.com/gtag/destination?id=G-MM917N9JTW&l=dataLayer&cx=c
h2
3973.6939999857
3998.7959999999
73259
205072
200
application/javascript
Script
https://cdn.cookielaw.org/consent/4b922523-c183-48b8-a64c-4273f069bbbe/4b922523-c183-48b8-a64c-4273f069bbbe.json
h2
3983.9670000074
4010.7089999947
2441
3137
200
application/x-javascript
XHR
https://mpsnare.iesnare.com/5.5.0/logo.js
http/1.1
3993.5269999842
4102.7849999955
923
505
200
text/javascript
Script
https://mpsnare.iesnare.com/time.mp3?nocache=0.48799872887463835
http/1.1
4032.4789999868
4120.6609999936
881
504
206
audio/mpeg
Media
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
h2
4034.9869999918
4077.6379999879
82075
343016
200
application/javascript
Script
https://www.google-analytics.com/collect?v=1&_v=j96&aip=1&a=673069419&t=pageview&_s=1&dl=https%3A%2F%2Fwww.meetic.fr%2F&dp=%2Fsignup%2Fstep-1&ul=fr&de=UTF-8&dt=Site%20de%20rencontre%20s%C3%A9rieux%20pour%20trouver%20l%E2%80%99amour%20Meetic&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YGAAgAAB~&cid=538035397.1659613061&tid=UA-126752871-2&_gid=1036202927.1659613061&gtm=2wg811WPNZTTN&cd1=Landing&cd2=meetic&cd3=web&cd4=FR&cd43=pending&cd44=pending&cd45=pending&cd46=prod&cd47=GTM-WPNZTTN-187&cd52=0&cd53=6944&cd54=000001&cd55=www.meetic.fr%2Fhpv&cd59=none&cd62=no&gcs=G100&z=492340525
h2
4053.7999999942
4057.3670000012
597
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j96&aip=1&a=673069419&t=event&ni=1&_s=1&dl=https%3A%2F%2Fwww.meetic.fr%2F&dp=%2Fsignup%2Fstep-1&ul=fr&de=UTF-8&dt=Site%20de%20rencontre%20s%C3%A9rieux%20pour%20trouver%20l%E2%80%99amour%20Meetic&sd=24-bit&sr=800x600&vp=1350x940&je=0&ec=Acquisition&ea=RegFormVisit&el=AcquisitionRegFormVisit&_u=YGgAgAAB~&cid=538035397.1659613061&tid=UA-126752871-2&_gid=1743427836.1659613061&gtm=2wg811WPNZTTN&cd1=Landing&cd2=meetic&cd3=web&cd4=FR&cd43=pending&cd44=pending&cd45=pending&cd46=prod&cd47=GTM-WPNZTTN-187&cd52=0&cd53=6944&cd54=000001&cd55=www.meetic.fr%2Fhpv&cd59=none&gcs=G100&z=337212749
h2
4054.0529999998
4057.7270000067
597
35
200
image/gif
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-MM917N9JTW&gtm=2oe811&_p=673069419&_z=ccd.v9B&gcs=G100&cid=538035397.1659613061&ul=en-us&sr=800x600&_s=1&sid=1659613060&sct=1&seg=0&dl=https%3A%2F%2Fwww.meetic.fr%2F&dt=Site%20de%20rencontre%20s%C3%A9rieux%20pour%20trouver%20l%E2%80%99amour%20Meetic&en=page_view&_fv=1&_ss=2&ep.page=%2Fsignup%2Fstep-1&ep.langage=fr&up.page_category=Landing&up.site_country=FR&up.site_version=web&up.env=prod&up.brand_name=meetic
4106.1530000006
4116.1659999925
0
0
-1
Ping
https://cdn.cookielaw.org/consent/4b922523-c183-48b8-a64c-4273f069bbbe/1710f851-a31d-4258-bed3-fa3f6fb0c5ed/fr.json
h2
4178.9219999919
4208.9770000021
18810
72163
200
application/x-javascript
Fetch
https://cdn.cookielaw.org/scripttemplates/6.32.0/assets/otCenterRounded.json
h2
4272.5839999912
4297.8920000023
3558
9507
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/6.32.0/assets/v2/otPcCenter.json
h2
4273.5309999844
4300.0170000014
12600
48715
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/6.32.0/assets/otCommonStyles.css
h2
4274.047999992
4301.953999995
5133
21595
200
text/css
Fetch
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
h2
4390.6309999875
4422.155999986
2423
2998
200
image/svg+xml
Image
https://www.meetic.fr/apida/configurations
http/1.1
4512.9890000098
5017.9409999982
1905
3415
200
application/json
Fetch
https://www.meetic.fr/iojs/5.5.0/dyn_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
http/1.1
4629.1590000037
5451.9169999985
3017
2332
200
text/javascript
Script
https://mpsnare.iesnare.com/time.mp3?nocache=0.5214542302692737
http/1.1
4741.1910000083
4802.542999998
881
504
206
audio/mpeg
Media
https://www.meetic.fr/iojs/5.5.0/logo.js
http/1.1
5458.885
6001.1729999969
1017
505
200
text/javascript
Script
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)
2805.346
19.823
2825.481
14.23
2839.725
97.804
2941.502
11.085
2960.567
42.404
3252.026
17.115
3345.956
26.798
3430.52
52.576
3487.6
6.004
3529.053
255.329
3784.453
15.135
3805.204
9.572
3837.272
9.671
3847.311
8.314
3855.657
12.589
3868.29
21.168
3889.472
106.697
4007.33
6.581
4015.865
27.751
4044.949
16.281
4065.001
18.813
4083.897
53.73
4146.996
11.842
4159.411
7.69
4167.112
11.411
4194.317
14.721
4213.44
16.085
4247.239
57.237
4333.198
87.217
4447.908
5.649
4760.766
8.48
4884.978
18.551
5517.195
7.879
6037.116
6.939
6134.069
9.738
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

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Meetic.fr should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 31 KiB
Images can slow down the page's load time. Meetic.fr should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/couples.responsive-77ac646ec32.jpg
128008
31232
Defer offscreen images — Potential savings of 2 KiB
Time to Interactive can be slowed down by resources on the page. Meetic.fr should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
2423
2423
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Meetic.fr should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Meetic.fr should consider minifying JS files.
Reduce unused CSS — Potential savings of 42 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Meetic.fr should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
._29m-IQcQ8cHkDa9G2_USgT{flex:1 1 100%} ...
37285
28434
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} ...
16821
14094
Efficiently encode images — Potential savings of 14 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/couples.responsive-77ac646ec32.jpg
128008
14131
Serve images in next-gen formats — Potential savings of 83 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://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/couples.responsive-77ac646ec32.jpg
128008
69684.35
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/audio-bb501bbab3d.png
20760
15505.05
Enable text compression — Potential savings of 23 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.meetic.fr/iojs/general5/static_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
39996
24055
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Meetic.fr 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 6 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.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
6543
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
64
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 1,156 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
255217
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/couples.responsive-77ac646ec32.jpg
128450
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/large-a94cb755672.webp
114607
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
82075
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
78403
https://www.googletagmanager.com/gtag/destination?id=G-MM917N9JTW&l=dataLayer&cx=c
73259
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
73238
https://www.googletagmanager.com/gtm.js?id=GTM-K3V66S&l=dataLayer
49890
https://www.meetic.fr/
49105
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
43508
Avoids an excessive DOM size — 703 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
703
Maximum DOM Depth
15
Maximum Child Elements
21
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Meetic.fr 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)
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
361.431
323.739
11.564
https://www.meetic.fr/
346.791
6.859
1.23
Unattributable
204.614
69.534
0.12
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
152.509
144.025
3.659
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
102.026
61.19
6.815
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
75.122
70.665
2.898
Minimizes main-thread work — 1.4 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
773.799
Style & Layout
250.093
Other
202.053
Rendering
47.366
Script Parsing & Compilation
37.882
Garbage Collection
25.732
Parse HTML & CSS
24.29
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 42 requests • 1,156 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
42
1183956
Script
14
749132
Image
11
276770
Font
3
61052
Document
1
49105
Other
11
46135
Media
2
1762
Stylesheet
0
0
Third-party
34
1086714
Minimize third-party usage — Third-party code blocked the main thread for 180 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)
589099
122.721
318298
53.212
135120
0
22049
0
21825
0
0
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 — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.020943333004991
0.0018090113606514
0.0017138002364066
0.00086832545311269
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 — 4 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://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
1320
128
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
2206
107
Unattributable
2357
57
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
2553
54
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 meetic.fr on mobile screens.
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.

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.

Metrics

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

Other

Reduce unused JavaScript — Potential savings of 275 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://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
255217
101346
https://www.googletagmanager.com/gtag/destination?id=G-MM917N9JTW&l=dataLayer&cx=c
73259
54685
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
82075
41806
https://www.googletagmanager.com/gtm.js?id=GTM-K3V66S&l=dataLayer
49890
28439
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
73238
27812
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
78403
27654
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Meetic.fr should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://meetic.fr/
190
https://meetic.fr/
150
https://www.meetic.fr/
0

Metrics

Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.

Other

Reduce initial server response time — Root document took 1,290 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://www.meetic.fr/
1292.181
Serve static assets with an efficient cache policy — 15 resources found
Meetic.fr 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.google-analytics.com/analytics.js
7200000
20631
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
14400000
82075
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
14400000
8080
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
14400000
2423
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
1128037000
255217
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/audio-bb501bbab3d.png
1128047000
21199
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/conversational-bot-9d221733c14.png
1703480000
4031
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/couples.responsive-77ac646ec32.jpg
1954571000
128450
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-bold-latin.woff2
2393155000
20480
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-medium-latin.woff2
2394200000
20308
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/positive-75570a615a9.svg
2435497000
1206
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-semi-bold-latin.woff2
2435509000
20264
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/large-a94cb755672.webp
2566771000
114607
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/arrow-146066c1e41.svg
2566931000
705
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/pinkwhite-44d5e901294.svg
2567080000
2632
76

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of meetic.fr. 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.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

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.

Names and labels

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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 alternate 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.

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.

Audio and video

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

Names and labels

Buttons do not 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.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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 meetic.fr 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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@2.6.12
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://meetic.fr/
Allowed
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for meetic.fr. 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 meetic.fr 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.
Document has 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.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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.
Avg. (All Categories) 71
Performance 32
Accessibility 76
Best Practices 83
SEO 93
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.meetic.fr/
Updated: 4th August, 2022

1.22 seconds
First Contentful Paint (FCP)
87%
8%
5%

0.07 seconds
First Input Delay (FID)
82%
14%
4%

Simulate loading on mobile
32

Performance

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

Metrics

Cumulative Layout Shift — 0.032
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Meetic.fr should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Meetic.fr should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 2 KiB
Time to Interactive can be slowed down by resources on the page. Meetic.fr should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
2423
2423
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Meetic.fr should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Meetic.fr should consider minifying JS files.
Reduce unused CSS — Potential savings of 43 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Meetic.fr should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
._29m-IQcQ8cHkDa9G2_USgT{flex:1 1 100%} ...
37148
30527
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} ...
16821
13986
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 23 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.meetic.fr/iojs/general5/static_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
39996
24055
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Meetic.fr 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 6 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.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
6543
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
64
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 936 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
255217
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
82075
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
78321
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
73368
https://www.googletagmanager.com/gtag/destination?id=G-MM917N9JTW&l=dataLayer&cx=c
73273
https://www.meetic.fr/
48925
https://www.googletagmanager.com/gtm.js?id=GTM-WJT4W8&l=dataLayer
48918
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
43508
https://www.meetic.fr/iojs/general5/static_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
40508
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/portrait-small-964c519156d.webp
40243
Avoids an excessive DOM size — 690 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
690
Maximum DOM Depth
15
Maximum Child Elements
21
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Meetic.fr 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.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 40 requests • 936 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
40
958857
Script
14
748211
Font
3
61052
Image
9
52757
Document
1
48925
Other
11
46150
Media
2
1762
Stylesheet
0
0
Third-party
32
861776
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 — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.022112068965517
0.0090598060344828
0.00049173213480833
0.00039676667702432
0.00020708436213111
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 — 20 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://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
5220
516
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
8948
438
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
10586
258
Unattributable
9453
255
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
9708
196
https://www.meetic.fr/
2314
169
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
7160
91
https://www.meetic.fr/
2724
89
https://mpsnare.iesnare.com/general5/wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
6858
82
https://www.meetic.fr/
2505
79
https://www.google-analytics.com/analytics.js
10466
76
https://www.meetic.fr/
2584
75
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
5847
75
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
6947
70
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
5778
69
https://www.meetic.fr/
2190
65
https://www.meetic.fr/
2659
65
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
8016
60
Unattributable
630
60
https://www.meetic.fr/
2255
59
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 meetic.fr on mobile screens.
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.

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://meetic.fr/
http/1.1
0
428.69100021198
165
0
302
text/plain
https://meetic.fr/
http/1.1
428.98400034755
1020.9850003012
439
0
301
text/html
https://www.meetic.fr/
http/1.1
1021.4080000296
1765.0160002522
48925
219999
200
text/html
Document
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/positive-75570a615a9.svg
http/1.1
1781.1620002612
2082.8450000845
1206
766
200
image/svg+xml
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/pinkwhite-44d5e901294.svg
http/1.1
1781.4560001716
2106.1820001341
2632
2191
200
image/svg+xml
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/conversational-bot-9d221733c14.png
http/1.1
1799.5240003802
2268.051000312
4031
3594
200
image/png
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
http/1.1
1799.2530004121
2365.2070001699
255217
876229
200
application/javascript
Script
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/portrait-small-964c519156d.webp
http/1.1
1805.2060003392
2766.0590000451
40243
39928
200
image/webp
Image
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-semi-bold-latin.woff2
http/1.1
1808.3660001867
2087.9750000313
20264
19824
200
font/woff2
Font
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-medium-latin.woff2
http/1.1
1809.3720003963
2379.2900000699
20308
19868
200
font/woff2
Font
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-bold-latin.woff2
http/1.1
1810.3400003165
2132.6620001346
20480
20040
200
font/woff2
Font
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/arrow-146066c1e41.svg
http/1.1
1908.9570003562
2624.691999983
705
265
200
image/svg+xml
Image
https://www.meetic.fr/apida/oauth/accesstokens
http/1.1
2588.1040003151
3179.8740001395
1096
733
200
application/json
Fetch
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
h2
2687.2700001113
2700.6769999862
43508
113299
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
h2
2687.797000166
2708.2640002482
78321
249596
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-WJT4W8&l=dataLayer
h2
2688.3820001967
2701.6730001196
48918
130232
200
application/javascript
Script
data
2688.300000038
2688.4530000389
0
34
200
image/webp
Image
https://www.meetic.fr/iojs/general5/static_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
http/1.1
2707.4420000426
3517.4110000953
40508
39996
200
text/javascript
Script
https://mpsnare.iesnare.com/general5/wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
http/1.1
2707.7030004002
2813.9850003645
19352
41816
200
text/javascript
Script
https://tk.ilius.net/tr.gif?lid=www.meetic.fr/hpv&co=704209&med=1&lmc=704209&url=www.meetic.fr&e=tl&fus=&lsid=unl0.122411989319949791659613108310&ts=1659613108310&klid=0&ktid=0
http/1.1
2712.6890001819
3200.4490001127
323
43
200
image/gif
Image
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
h2
2767.2230000608
2796.7870002612
8080
21599
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
2858.3080000244
2862.7010001801
20630
50205
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
h2
2866.9850002043
2894.4050003774
73368
205098
200
application/javascript
Script
https://pagead2.googlesyndication.com/pagead/landing?gcs=G100&gcd=G100&rnd=265600585.1659613108&url=https%3A%2F%2Fwww.meetic.fr%2F&gtm=2wg830WPNZTTN
2876.7200000584
2900.7930001244
0
0
-1
Ping
https://www.googletagmanager.com/gtag/destination?id=G-MM917N9JTW&l=dataLayer&cx=c
h2
2903.9870002307
2937.8270003945
73273
205072
200
application/javascript
Script
https://cdn.cookielaw.org/consent/4b922523-c183-48b8-a64c-4273f069bbbe/4b922523-c183-48b8-a64c-4273f069bbbe.json
h2
2916.2390003912
2939.679000061
2441
3137
200
application/x-javascript
XHR
https://mpsnare.iesnare.com/5.5.0/logo.js
http/1.1
2922.3100002855
3013.4670003317
921
505
200
text/javascript
Script
https://mpsnare.iesnare.com/time.mp3?nocache=0.49016945883429375
http/1.1
2945.4250000417
3034.4310002401
881
504
206
audio/mpeg
Media
https://www.google-analytics.com/collect?v=1&_v=j96&aip=1&a=1641391184&t=pageview&_s=1&dl=https%3A%2F%2Fwww.meetic.fr%2F&dp=%2Fsignup%2Fstep-1&ul=fr&de=UTF-8&dt=Site%20de%20rencontre%20s%C3%A9rieux%20pour%20trouver%20l%E2%80%99amour%20Meetic&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YGAAgAAB~&cid=501178105.1659613109&tid=UA-126752871-2&_gid=1411488545.1659613109&gtm=2wg830WPNZTTN&cd1=Landing&cd2=meetic&cd3=mobile_web&cd4=FR&cd43=pending&cd44=pending&cd45=pending&cd46=prod&cd47=GTM-WPNZTTN-187&cd52=0&cd53=0&cd54=704209&cd55=www.meetic.fr%2Fhpv&cd59=none&cd62=no&gcs=G100&z=121177906
h2
2965.2160000987
2969.5520000532
597
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j96&aip=1&a=1641391184&t=event&ni=1&_s=1&dl=https%3A%2F%2Fwww.meetic.fr%2F&dp=%2Fsignup%2Fstep-1&ul=fr&de=UTF-8&dt=Site%20de%20rencontre%20s%C3%A9rieux%20pour%20trouver%20l%E2%80%99amour%20Meetic&sd=24-bit&sr=360x640&vp=360x640&je=0&ec=Acquisition&ea=RegFormVisit&el=AcquisitionRegFormVisit&_u=YGgAgAAB~&cid=501178105.1659613109&tid=UA-126752871-2&_gid=308134743.1659613109&gtm=2wg830WPNZTTN&cd1=Landing&cd2=meetic&cd3=mobile_web&cd4=FR&cd43=pending&cd44=pending&cd45=pending&cd46=prod&cd47=GTM-WPNZTTN-187&cd52=0&cd53=0&cd54=704209&cd55=www.meetic.fr%2Fhpv&cd59=none&gcs=G100&z=328233554
h2
2965.4230000451
2969.13400013
597
35
200
image/gif
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-MM917N9JTW&gtm=2oe811&_p=1641391184&_z=ccd.v9B&gcs=G100&cid=501178105.1659613109&ul=en-us&sr=360x640&_s=1&sid=1659613108&sct=1&seg=0&dl=https%3A%2F%2Fwww.meetic.fr%2F&dt=Site%20de%20rencontre%20s%C3%A9rieux%20pour%20trouver%20l%E2%80%99amour%20Meetic&en=page_view&_fv=1&_ss=2&ep.page=%2Fsignup%2Fstep-1&ep.langage=fr&up.page_category=Landing&up.site_country=FR&up.site_version=mobile_web&up.env=prod&up.brand_name=meetic
3028.0540003441
3057.2930001654
0
0
-1
Ping
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
h2
3036.9210001081
3080.243000295
82075
343016
200
application/javascript
Script
https://cdn.cookielaw.org/consent/4b922523-c183-48b8-a64c-4273f069bbbe/1710f851-a31d-4258-bed3-fa3f6fb0c5ed/fr.json
h2
3140.6680000946
3190.6020003371
18811
72163
200
application/x-javascript
Fetch
https://www.meetic.fr/apida/configurations
http/1.1
3182.9130002297
3855.0240001641
1908
3415
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/6.32.0/assets/otCenterRounded.json
h2
3254.6640001237
3280.6959999725
3557
9507
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/6.32.0/assets/v2/otPcCenter.json
h2
3256.0010002926
3282.4250003323
12600
48715
200
application/json
Fetch
https://cdn.cookielaw.org/scripttemplates/6.32.0/assets/otCommonStyles.css
h2
3257.7969999984
3281.6300000995
5133
21595
200
text/css
Fetch
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
h2
3383.890000172
3414.0429999679
2423
2998
200
image/svg+xml
Image
https://www.meetic.fr/iojs/5.5.0/dyn_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
http/1.1
3528.6960001104
3901.1170002632
3025
2342
200
text/javascript
Script
https://mpsnare.iesnare.com/time.mp3?nocache=0.1450839873609544
http/1.1
3636.6130001843
3725.1059999689
881
504
206
audio/mpeg
Media
https://www.meetic.fr/iojs/5.5.0/logo.js
http/1.1
3905.1610003226
4443.4620002285
1015
505
200
text/javascript
Script
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)
1798.16
16.227
1814.754
14.764
1829.529
84.722
1919.253
11.028
1935.845
39.519
2132.087
37.298
2174.951
32.345
2415.31
44.337
2459.885
258.117
2718.137
9.888
2731.055
10.511
2757.998
11.007
2769.464
8.114
2777.588
22.859
2800.509
15.024
2815.565
109.466
2938.818
6.266
2945.131
20.529
2966.11
7.789
2975.453
19.017
2994.564
64.473
3066.171
17.355
3086.606
14.232
3110.128
5.31
3118.141
11.341
3135.281
18.791
3154.519
14.581
3222.753
63.71
3314.386
97.804
3432.076
7.249
3443.655
5.163
3655.004
8.955
3669.967
5.218
3727.669
15.014
3777.567
17.582
4407.336
6.473
4477.602
8.225
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.4 s
The time taken for the first image or text on the page to be rendered.

Audits

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

Other

Serve static assets with an efficient cache policy — 13 resources found
Meetic.fr 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.google-analytics.com/analytics.js
7200000
20630
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
14400000
82075
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js
14400000
8080
https://cdn.cookielaw.org/logos/static/poweredBy_ot_logo.svg
14400000
2423
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
1127990000
255217
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/pinkwhite-44d5e901294.svg
1703298000
2632
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/conversational-bot-9d221733c14.png
1703433000
4031
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-bold-latin.woff2
2393172000
20480
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-medium-latin.woff2
2394153000
20308
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/positive-75570a615a9.svg
2435450000
1206
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/montserrat-semi-bold-latin.woff2
2435462000
20264
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/arrow-146066c1e41.svg
2566883000
705
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/portrait-small-964c519156d.webp
2592000000
40243
Reduce JavaScript execution time — 3.3 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)
https://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
1520.396
1339.376
54.24
https://www.meetic.fr/
1352.052
33.292
5.848
Unattributable
679.752
292.216
0.788
https://www.googletagmanager.com/gtm.js?id=GTM-PGVTX2R&l=dataLayer
638.968
602.364
13.864
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
450.168
281.888
27.08
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
359.904
339.232
12.976
https://mpsnare.iesnare.com/general5/wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
109.78
97.532
3.392
https://www.google-analytics.com/analytics.js
76.812
70.88
3.664
https://www.meetic.fr/iojs/general5/static_wdp.js?loaderVer=5.2.2&compat=false&tp=true&tp_split=false&fp_static=true&fp_dyn=true&flash=false
76.72
66.304
2.492
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
62.84
37.524
16.624

Metrics

Time to Interactive — 10.4 s
The time taken for the page to become fully interactive.
Speed Index — 6.7 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 1,600 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 — 11.0 s
The timing of the largest text or image that is painted.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 275 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://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/bundle-1c853a6cb1a8a79.js
255217
102775
https://www.googletagmanager.com/gtag/destination?id=G-MM917N9JTW&l=dataLayer&cx=c
73273
54696
https://cdn.cookielaw.org/scripttemplates/6.32.0/otBannerSdk.js
82075
41806
https://www.googletagmanager.com/gtag/js?id=G-MM917N9JTW&l=dataLayer&cx=c
73368
27846
https://www.googletagmanager.com/gtm.js?id=GTM-WPNZTTN&l=dataLayer
78321
27594
https://www.googletagmanager.com/gtm.js?id=GTM-WJT4W8&l=dataLayer
48918
27041
Reduce initial server response time — Root document took 740 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://www.meetic.fr/
744.601
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Meetic.fr should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://meetic.fr/
630
https://meetic.fr/
480
https://www.meetic.fr/
0
Minimize main-thread work — 5.5 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
3261.608
Style & Layout
995.204
Other
661.968
Rendering
176.196
Script Parsing & Compilation
163.32
Garbage Collection
111.856
Parse HTML & CSS
97.76
Reduce the impact of third-party code — Third-party code blocked the main thread for 1,550 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)
365086
865.384
317388
577.096
135120
66.184
22035
25.664
21824
15.424
0
0
First Contentful Paint (3G) — 4518 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
76

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of meetic.fr. 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.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

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.

Names and labels

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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 alternate 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.

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.

Audio and video

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

Names and labels

Buttons do not 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.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that meetic.fr 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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-global@2.6.12
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://meetic.fr/
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://iliusstu-a.akamaihd.net/www.meetic.fr/hpv/conversational-bot-9d221733c14.png
64 x 64
64 x 64
128 x 128
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for meetic.fr. 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 meetic.fr on mobile screens.
Document uses legible font sizes — 83.06% 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
.theme-category-core .vaDCIXBxhtpOA2_bugiTn, .theme-category-senior .vaDCIXBxhtpOA2_bugiTn
14.71%
10px
#onetrust-banner-sdk #onetrust-policy-text, #onetrust-banner-sdk .ot-b-addl-desc, #onetrust-banner-sdk .ot-gv-list-handler
2.15%
11.382px
#onetrust-banner-sdk #onetrust-accept-btn-handler, #onetrust-banner-sdk #onetrust-reject-all-handler, #onetrust-banner-sdk #onetrust-pc-btn-handler
0.03%
11.382px
#onetrust-banner-sdk.ot-close-btn-link #onetrust-close-btn-container button
0.03%
10.5px
0.03%
< 12px
83.06%
≥ 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.
Document has 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.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

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

Server Location

Server IP Address: 62.23.26.24
Continent: Europe
Country: France
France Flag
Region: Île-de-France
City: Paris
Longitude: 2.3281
Latitude: 48.8607
Currencies: EUR
Languages: French

Web Hosting Provider

Name IP Address
MEETIC CO COLT
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Meetic
Country: FR
City:
State:
Post Code:
Email: hostmaster@meetic-corp.com
Phone: +33 1 84 17 90 00
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 62/100
WOT Child Safety: 31/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: meetic.fr
Issued By: R3
Valid From: 6th July, 2022
Valid To: 4th October, 2022
Subject: CN = meetic.fr
Hash: baf9dbf3
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03B13D49696ED04A8FD622E280025783F350
Serial Number (Hex): 03B13D49696ED04A8FD622E280025783F350
Valid From: 6th July, 2024
Valid To: 4th October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Jul 6 08:17:55.900 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:12:C3:BF:85:49:3B:C4:B4:66:F2:39:0C:
57:7C:AA:42:CB:FD:A0:3A:C5:67:DD:18:8E:8B:03:6C:
77:74:EB:92:02:21:00:C0:4F:6D:FB:B5:C8:F8:90:0D:
BD:11:E0:EB:36:72:F7:6A:42:DE:00:19:63:0C:5F:2A:
F8:79:07:19:1A:74:F4
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Jul 6 08:17:56.079 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:76:B4:47:12:97:5F:54:EF:E9:CC:33:A3:
00:03:20:2A:E5:BA:7C:4D:84:61:F8:A0:17:C2:26:B1:
50:31:38:C6:02:21:00:C6:FF:DE:32:3C:60:E3:FD:42:
E7:0D:80:95:BB:B7:A7:91:74:6C:06:38:BA:44:DB:55:
12:A6:FB:73:50:4E:35
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:meetic.fr
DNS:*.meetic.fr
Technical

DNS Lookup

A Records

Host IP Address Class TTL
meetic.fr. 62.23.26.24 IN 20

NS Records

Host Nameserver Class TTL
meetic.fr. aus1.akam.net. IN 3600
meetic.fr. use1.akam.net. IN 3600
meetic.fr. asia1.akam.net. IN 3600
meetic.fr. eur4.akam.net. IN 3600
meetic.fr. eur3.akam.net. IN 3600

MX Records

Priority Host Server Class TTL
10 meetic.fr. alt3.aspmx.l.google.com. IN 600
5 meetic.fr. alt2.aspmx.l.google.com. IN 600
1 meetic.fr. aspmx.l.google.com. IN 600
10 meetic.fr. alt4.aspmx.l.google.com. IN 600
5 meetic.fr. alt1.aspmx.l.google.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
meetic.fr. eur3.akam.net. dnsmaster.meetic-corp.com. 3600

TXT Records

Host Value Class TTL
meetic.fr. google-site-verification=e4-gMVDcT2_tL0DNgleWN1i6CnSZOsTtkLS8qbMcl8Q IN 600
meetic.fr. v=spf2.0/pra IN 600
meetic.fr. apple-domain-verification=WPzRqiGOzwScTaoz IN 600
meetic.fr. v=spf1 IN 600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache, private
Date: 4th August, 2022
Connection: keep-alive
Keep-Alive: timeout=60
Vary: Accept-Encoding
Set-Cookie: *
Strict-Transport-Security: max-age=31536000

Whois Lookup

Created: 19th December, 2001
Changed: 7th September, 2021
Expires:
Registrar: NAMESHIELD
Status:
Nameservers: asia1.akam.net
aus1.akam.net
aus2.akam.net
eur3.akam.net
eur4.akam.net
ns1-111.akam.net
ns1-202.akam.net
use1.akam.net
Owner Country: FR
Owner Phone: +33 1 84 17 90 00
Owner Email: hostmaster@meetic-corp.com
Admin Country: FR
Admin Phone: +33 1 84 17 90 00
Admin Email: hostmaster@meetic-corp.com
Tech Country: FR
Tech Phone: +33.241182828
Tech Fax: +33.241182829
Tech Email: technical@nameshield.net
Full Whois: %%
%% This is the AFNIC Whois server.
%%
%% complete date format : YYYY-MM-DDThh:mm:ssZ
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See https://www.afnic.fr/en/products-and-services/services/whois/whois-special-notice/
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [67.205.137.127 REQUEST] >> meetic.fr
%%
%% RL Net [##########] - RL IP [#########.]
%%

domain: meetic.fr
status: ACTIVE
hold: NO
holder-c: M33782-FRNIC
admin-c: M33783-FRNIC
tech-c: N17024-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL367399-FRNIC
registrar: NAMESHIELD
Expiry Date: 2022-09-09T22:07:52Z
created: 2001-12-19T23:00:00Z
last-update: 2021-09-07T22:18:11Z
source: FRNIC

ns-list: NSL367399-FRNIC
nserver: asia1.akam.net
nserver: aus1.akam.net
nserver: aus2.akam.net
nserver: eur3.akam.net
nserver: eur4.akam.net
nserver: ns1-111.akam.net
nserver: ns1-202.akam.net
nserver: use1.akam.net
source: FRNIC

registrar: NAMESHIELD
type: Isp Option 1
address: 39 boulevard des Capucines
address: 75002 PARIS
country: FR
phone: +33 2 41 18 28 28
fax-no: +33 2 41 18 28 29
e-mail: registrar@nameshield.net
website: https://www.nameshield.com/contact-nameshield/
anonymous: NO
registered: 1998-01-01T12:00:00Z
source: FRNIC

nic-hdl: M33782-FRNIC
type: ORGANIZATION
contact: MEETIC
address: HOST master
address: 6, rue auber
address: 75009 Paris
address: N/C
country: FR
phone: +33 1 84 17 90 00
e-mail: hostmaster@meetic-corp.com
registrar: NAMESHIELD
changed: 2017-06-27T09:30:06Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: pending
eligsource: REGISTRY
reachstatus: pending
reachsource: REGISTRY
source: FRNIC

nic-hdl: M33783-FRNIC
type: ORGANIZATION
contact: MEETIC
address: HOST master
address: 6, rue auber
address: 75009 Paris
address: N/C
country: FR
phone: +33 1 84 17 90 00
e-mail: hostmaster@meetic-corp.com
registrar: NAMESHIELD
changed: 2017-06-27T09:30:08Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: not identified
reachstatus: not identified
source: FRNIC

nic-hdl: N17024-FRNIC
type: ORGANIZATION
contact: NAMESHIELD
address: TECHNICAL department
address: 79 rue Desjardins
address: 49100 ANGERS
address: N/C
country: FR
phone: +33.241182828
fax-no: +33.241182829
e-mail: technical@nameshield.net
registrar: NAMESHIELD
changed: 2017-11-21T09:50:30Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: not identified
reachstatus: not identified
source: FRNIC

Nameservers

Name IP Address
asia1.akam.net 95.100.175.64
aus1.akam.net 184.85.248.65
aus2.akam.net 95.101.36.65
eur3.akam.net 95.100.174.64
eur4.akam.net 84.53.139.64
ns1-111.akam.net 193.108.91.111
ns1-202.akam.net 193.108.91.202
use1.akam.net 72.246.46.64
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,484,462 USD 4/5
$2,518 USD 2/5
0/5
$10 USD 1/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$14,395 USD 3/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5
$2,336 USD 2/5