Werepair.fr
Pièces détachées électroménager | WeREPAIR
Domain Summary
What is the traffic rank for Werepair.fr?
• Werepair.fr ranks #582,167 globally on HypeStat.
What percent of global Internet users visit Werepair.fr?
• 3.63E-5% of global Internet users visit Werepair.fr
How many people visit Werepair.fr each day?
• Werepair.fr receives approximately 1.8K visitors and 4,407 page impressions per day.
Which countries does Werepair.fr receive most of its visitors from?
• Werepair.fr is mostly visited by people located in France,Switzerland,United States.
How much Werepair.fr can earn?
• Werepair.fr should earn about $4.00/day from advertising revenue.
What is Werepair.fr estimated value?
• Estimated value of Werepair.fr is $3,665.85.
What IP addresses does Werepair.fr resolve to?
• Werepair.fr resolves to the IP addresses 185.111.59.90.
Where are Werepair.fr servers located in?
• Werepair.fr has servers located in France.
werepair.fr Profile

What technologies does werepair.fr use?
These are the technologies used at werepair.fr. werepair.fr has a total of 5 technologies installed in 5 different categories.werepair.fr Traffic Analysis
Werepair.fr is ranked #582,167 in the world. This website is viewed by an estimated 1.8K visitors daily, generating a total of 4.4K pageviews. This equates to about 54.2K monthly visitors. Werepair.fr traffic has increased by 1.71% compared to last month.Daily Visitors1.8K
12.98%
Monthly Visits54.2K
1.71%
Pages per Visit2.46
13.42%
Visit duration02:05
38.47%
Bounce Rate50.86%
44.77%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 1,788
- Monthly Visits:
- 54,176
- Pages per Visit:
- 2.46
- Daily Pageviews:
- 4,407
- Avg. visit duration:
- 02:05
- Bounce rate:
- 50.86%
- Global Reach:
- 3.63E-5%
- Monthly Visits (SEMrush):
- 60,681
- Monthly Unique Visitors (SEMrush):
- 48,586
- Monthly Visits (SimilarWeb):
- 52,593
- HypeRank:
- 582,167
- SEMrush Rank:
- 9,228,130
- SimilarWeb Rank:
- 582,167
Traffic sources
- Direct:
- 30.07%
- Referral:
- 2.01%
- Search:
- 63.53%
- Social:
- 0%
- Paid:
- 4.39%
Desktop vs Mobile
- Desktop:
- 66.96%
- Mobile:
- 33.04%
Total Visits Last 3 Months
65.7K
DEC
53.3K
JAN
54.2K
FEB
Visitors by country
- Country
- Users%
- France 88.90%
- Switzerland 2.93%
- United States 2.31%
- Belgium 2.12%
- Germany 1.76%
Backlinks Report ▼
Werepair.fr has a total of 94,780 backlinks from 293 referring domains and most of them comes from France.- Total Backlinks:
- 94,780
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 293
- Referring IPs:
- 303
- Authority Domain Score:
- 31
Backlinks by country
- Country
- Domains
- France 106
- United States 57
- Germany 12
- Russian Federation 10
- Turkey 7
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 122
- .fr
- 81
- .org
- 11
- .edu
- 0
- .gov
- 0
Which sites are competitors to werepair.fr?
Websites similar to werepair.fr are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.- Domain
- CompareDaily Visitors
- equipementpro.fr
- Compare >3K
- espares.fr
- Compare >2.8K
- pcdt.fr
- Compare >2.7K
- lagrange.fr
- Compare >2.2K
- fixpart.ch
- Compare >2.1K
Last update was 75 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with werepair.fr in any way. Only publicly available statistics data are displayed.
▼
SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.- Domain:
- werepair.fr
- Rank:
(Rank based on keywords, cost and organic traffic) - 9,228,130
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 88
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 4
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $0.00
Revenue report ▼
Google.com would generate approximately $4 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $120 and annual gross revenue of approximately $1.5K. Based on these figures, the site's net worth is estimated at around $3.7K.How much would werepair.fr make?
- Daily Revenue:
- $4.00
- Monthly Revenue:
- $120.00
- Yearly Revenue:
- $1,460.00
Daily earning by country
- CountryPageviewsEarning
- France 3,918$2.27
- Switzerland 129$0.72
- United States 102$0.49
- Germany 77$0.11
- Belgium 94$0.05
Loss of money due to Adblock?
- Daily Revenue Loss:
- $0.51
- Monthly Revenue Loss:
- $15.15
- Yearly Revenue Loss:
- $184.34
- Daily Pageviews Blocked:
- 506
- Monthly Pageviews Blocked:
- 15,187
- Yearly Pageviews Blocked:
- 184,770
Daily revenue loss by country
- CountryBlockedLost Money
- France 431$0.25
- Switzerland 23$0.13
- United States 18$0.09
- Germany 22$0.03
- Belgium 11$0.01
How much is werepair.fr worth?
- Website Value:
- $3.7K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- werepair.fr
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Desktop summary
- Root domain:
- werepair.fr
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Abusive Experience Report ▼
Summary of the abusive experience rating of a website.- Root domain:
- werepair.fr
- Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.) - Off
- Status:
(The status of the site reviewed for the abusive experiences.) - Not reviewed
Where is werepair.fr hosted? ▼
Werepair.fr may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 185.111.59.90
- ASN:
- AS20986
- ISP:
- HISI SAS
- Server Location:
France, FR
Other sites hosted on 185.111.59.90
How fast does werepair.fr load? ▼
The average loading time of werepair.fr is 2037 ms. The Desktop speed index is 0 and mobile speed index is 93.- Average Load Time:
- 2037 ms
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)1ms
Time To First Byte (TTFB)3.0s
First Contentful Paint (FCP)3.5s
First Input Delay (FID)0
Interactive To Next Paint (INP)228ms
Largest Contentful Paint (LCP)3.9s
Origin Data
All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)2.5s
First Contentful Paint (FCP)3.0s
First Input Delay (FID)0
Interactive To Next Paint (INP)145ms
Largest Contentful Paint (LCP)3.1s
Lab Data
Long critical network tree
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
CSS Selector costs
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources
First Contentful Paint 2.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Time to Interactive 2.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Third parties
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Font display
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Largest Contentful Paint element
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Reduce unused CSS
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images
Avoids an excessive DOM size
A large DOM will increase memory usage, cause longer , and produce costly . style calculations layout reflows
A large DOM will increase memory usage, cause longer , and produce costly . style calculations layout reflows
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Does werepair.fr use compression? ▼
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on werepair.fr are reduced by 84%.
werepair.fr use gzip compression.
Original size: 173.39 KB
Compressed size: 27.72 KB
File reduced by: 145.67 KB (84%)
Compressed size: 27.72 KB
File reduced by: 145.67 KB (84%)
Google Safe Browsing ▼
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.SSL Checker - SSL Certificate Verify ▼
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. werepair.fr supports HTTPS. werepair.fr supports HTTPS
Verifying SSL Support. Please wait...
Common Name: werepair.fr
Organization:
Location:
Issuer: R11
Valid from: Mar 3 23:02:47 2025 GMT
Valid until: Jun 1 23:02:46 2025 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Organization:
Location:
Issuer: R11
Valid from: Mar 3 23:02:47 2025 GMT
Valid until: Jun 1 23:02:46 2025 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Common Name: R11
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Verify HTTP/2 Support ▼
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. werepair.fr supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Http Header ▼
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.access-control-allow-origin: *
cache-control: no-store, no-cache, must-revalidate
content-encoding: gzip
content-length: 28388
content-security-policy:
content-type: text/html; charset=utf-8
date: Wed, 02 Apr 2025 04:15:03 GMT
expires: Thu, 19 Nov 1981 08:52:00 GMT
permissions-policy: midi=(), notifications=(), push=(), microphone=(), camera=(), magnetometer=(), gyroscope=(), speaker=(self), vibrate=(), fullscreen=(self), payment=()
pragma: no-cache
server: dis-waf
set-cookie: PHPSESSID=egau89lf8bp48chom8jibam66r; path=/; secure
set-cookie: PrestaShop-063aa4cc76382e6ad53c21e7725cdcfb=def50200cb23a462bb5e65f7f223832e86b8f1ab811f5c927aa72f29f59d109c0e7200d1dd890674c9fca124f802e555634b6a05bdbb75c6e8eb306cef63cdb89cf4acf9d1c635a7b845f30fefc8b342715c11e875688ae1e07002ad5ce79e4b8247006be07a8342e8b56c358a4eeb40046b762a2785e0a1d2554ba98ea4b0377f9b22b6c7fed9060381e2526e96394130699745c5ef77483e0286398a6fa9250492f26a46e216614b89b540e3df52c39e1b5fcc973104c6e4f314a92a9b9dc6a8ec37bad79916812ae29f9c8921ab8888ce81ea49; expires=Tue, 22-Apr-2025 04:15:03 GMT; Max-Age=1727999; path=/; domain=werepair.fr; secure; HttpOnly
set-cookie: PrestaShop-063aa4cc76382e6ad53c21e7725cdcfb=def50200991aab4eed5d5ee3229778a7c6950b86a895a8396eccc865bf7066a2aef5d134f7f4c5dca73bfe00b6bccd2e89b7362d863837fcac15b34eb404e51ca58df6c984607cec9ceffcd719098cffd8cda1ff6c27a062c17238a3c1622f047b4aef0b92db3e275bb89386bb2216b5a03b4b46a299813f3293a5139d0a3a2530630cce04b7400578ae3478d7e619e2976c825d7182a9b44629a84027e431cb0a24168bd3073d0a9536d1c493b96d1fc1283b8fa667e75dad1f8b3ce3635f5bd0c71bba53e1b806e024ec6be634ffce3d7725875336cf2b3baaeab349072be9080d9d1e66d53705a0d1; expires=Tue, 22-Apr-2025 04:15:03 GMT; Max-Age=1727999; path=/; domain=werepair.fr; secure; HttpOnly
vary: Accept-Encoding
x-content-type-options: nosniff
x-dis-country: US
x-dis-id: dd110593757f362cc29bc32e2c756fd6377f8161
x-dis-ts: 1743567303
x-dis-waf: 1
Whois Lookup ▼
Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on December 5, 2018 and will expire on December 5, 2025 if not renewed. This website is now assigned through the registrar OVH. The WHOIS data for this website's domain was last updated on January 31, 2025.- Domain Created:
- 2018-12-05
- Domain Expires:
- 2025-12-05
- Domain Updated:
- 2025-01-31
- Domain Age:
- 6 years 6 months 11 days
- Domain Registrar:
- OVH
- Domain Owner:
- DPDO DISTRIBUTION
- WhoIs:
%% %% This is the AFNIC Whois server. %% %% complete date format: YYYY-MM-DDThh:mm:ssZ %% %% Rights restricted by copyright. %% See https://www.afnic.fr/en/domain-names-and-support/everything-there-is-to-know-about-domain-names/find-a-domain-name-or-a-holder-using-whois/ %% %% domain: werepair.fr status: ACTIVE eppstatus: active hold: NO holder-c: DD20073-FRNIC admin-c: DD20080-FRNIC tech-c: OVH5-FRNIC registrar: OVH Expiry Date: 2025-12-05T15:49:02Z created: 2018-12-05T15:49:02Z last-update: 2025-01-31T23:12:16.373673Z source: FRNIC nserver: dns113.ovh.net nserver: ns113.ovh.net source: FRNIC registrar: OVH address: 2 Rue Kellermann address: 59100 ROUBAIX country: FR phone: +33.899701761 fax-no: +33.320200958 e-mail:website: http://www.ovh.com anonymous: No registered: 1999-10-18T00:00:00Z source: FRNIC nic-hdl: DD20080-FRNIC type: ORGANIZATION contact: DPDO DISTRIBUTION address: DPDO DISTRIBUTION address: 6 Rue de l'Epau address: 59230 SARS ET ROSIERES country: FR phone: +33.327096969 e-mail:
registrar: OVH anonymous: NO obsoleted: NO eppstatus: associated eppstatus: active eligstatus: not identified reachstatus: not identified source: FRNIC nic-hdl: OVH5-FRNIC type: ORGANIZATION contact: OVH NET address: OVH address: 140, quai du Sartel address: 59100 Roubaix country: FR phone: +33.899701761 e-mail:
registrar: OVH changed: 2025-04-02T04:03:01.414578Z anonymous: NO obsoleted: NO eppstatus: associated eppstatus: active eligstatus: not identified reachstatus: not identified source: FRNIC nic-hdl: DD20073-FRNIC type: ORGANIZATION contact: DPDO DISTRIBUTION address: DPDO DISTRIBUTION address: 6 Rue de l'Epau address: 59230 SARS ET ROSIERES country: FR phone: +33.327096969 e-mail:
registrar: OVH changed: 2018-12-05T16:38:39Z anonymous: NO obsoleted: NO eppstatus: associated eppstatus: active eligstatus: not identified reachstatus: not identified source: FRNIC >>> Last update of WHOIS database: 2025-04-02T04:16:22.330382Z