Your Website Score is

Similar Ranking

26
JUST A MOMENT...
brittanypetros.xyz
26
PORTFOLIO
mgillon.com
26
DANCE AXIOM | DANCE | COLLEYVILLE TEXAS
danceaxiom.com
26
BIENVENIDOS A TORRECIUDAD - SANTUARIO DE TORRECIUDAD
torreciudad.org
26
CASTILLOS HINCHABLES MÁLAGA Y ANIMACIONES INFANTILES MÁLAGA
telecastillo.com
26
RECIFE - CENTRO DE ABATE E PEÇAS AUTO USADAS
recife.com.pt
26
LOCALHOST - HTTP://LOCALHOST
locallhost.info

Latest Sites

9
YOUTUBE
youtube.com
99
APPLE
apple.com
2
YOUTUBE
youtu.be
16
-
midnightdev.store
99
YOUR BROWSER IS DEPRECATED. PLEASE UPGRADE.
music.youtube.com
99
YOUTUBE
studio.youtube.com
31
MINING GAME ROLLERCOIN | BITCOIN MINER SIMULATOR | PLAY NOW FOR FREE
rollercoin.com

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
jQuery
JavaScript Frameworks
CloudFlare
CDN
PHP
Programming Languages
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
WordPress
CMS

26 recife.com.pt Last Updated: 2 months

Success 70% of passed verification steps
Warning 15% of total warning
Errors 15% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 52%
Best Practices Desktop Score 83%
SEO Desktop Score 100%
PWA Desktop Score 22%
Performance Mobile Score 28%
Best Practices Mobile Score 92%
SEO Mobile Score 95%
PWA Mobile Score 20%
Page Authority Authority 15%
Domain Authority Domain Authority 22%
Moz Rank 1.5/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 44 Characters
RECIFE - CENTRO DE ABATE E PEÇAS AUTO USADAS
Meta Description 143 Characters
Centro de abate autorizado de veículos em fim de vida. Com um parque auto de mais de 3.000 carros e mais de 100 mil peças online, com garantia.
Effective URL 21 Characters
https://recife.com.pt
Excerpt Page content
Recife - Centro de Abate e Peças Auto Usadas ...
Meta Keywords 1 Detected
Centro de abate e peças usadas
Google Preview Your look like this in google search result
RECIFE - CENTRO DE ABATE E PEÇAS AUTO USADAS
https://recife.com.pt
Centro de abate autorizado de veículos em fim de vida. Com um parque auto de mais de 3.000 carros e mais de 100 mil peças online, com garantia.
Robots.txt File Detected
http://recife.com.pt/robots.txt
Sitemap.xml File Detected
http://recife.com.pt/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~2.25 MB
Code Size: ~2.1 MB
Text Size: ~152.16 KB Ratio: 6.62%

Social Data

Estimation Traffic and Earnings

81
Unique Visits
Daily
149
Pages Views
Daily
$0
Income
Daily
2,268
Unique Visits
Monthly
4,247
Pages Views
Monthly
$0
Income
Monthly
26,244
Unique Visits
Yearly
50,064
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Eliminate render-blocking resources Potential savings of 530 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce unused JavaScript Potential savings of 145 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Speed Index 3.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Properly size images Potential savings of 1,846 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid an excessive DOM size 1,906 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Serve static assets with an efficient cache policy 85 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 20 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoid serving legacy JavaScript to modern browsers Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Defer offscreen images Potential savings of 434 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 3,648 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minify JavaScript Potential savings of 68 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Minify CSS Potential savings of 12 KiB
Minifying CSS files can reduce network payload sizes
Total Blocking Time 140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Cumulative Layout Shift 0.337
Cumulative Layout Shift measures the movement of visible elements within the viewport
Keep request counts low and transfer sizes small 102 requests • 6,496 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay 310 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Time to Interactive 4.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 5.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid non-composited animations 69 animated elements found
Animations which are not composited can be janky and increase CLS
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Reduce initial server response time Root document took 1,390 ms
Keep the server response time for the main document short because all other requests depend on it
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Reduce unused CSS Potential savings of 37 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Efficiently encode images Potential savings of 158 KiB
Optimized images load faster and consume less cellular data
Avoid enormous network payloads Total size was 6,496 KiB
Large network payloads cost users real money and are highly correlated with long load times

Mobile

Mobile Screenshot
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Minimize main-thread work 4.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Potential savings of 1,730 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 158 KiB
Optimized images load faster and consume less cellular data
Speed Index 11.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify CSS Potential savings of 12 KiB
Minifying CSS files can reduce network payload sizes
Properly size images Potential savings of 1,818 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Minify JavaScript Potential savings of 68 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Tap targets are not sized appropriately 39% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Initial server response time was short Root document took 600 ms
Keep the server response time for the main document short because all other requests depend on it
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Reduce unused CSS Potential savings of 37 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Contentful Paint 3.4 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid non-composited animations 60 animated elements found
Animations which are not composited can be janky and increase CLS
Serve images in next-gen formats Potential savings of 3,648 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid an excessive DOM size 1,582 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimize third-party usage Third-party code blocked the main thread for 100 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Max Potential First Input Delay 1,030 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 980 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Serve static assets with an efficient cache policy 76 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads Total size was 6,477 KiB
Large network payloads cost users real money and are highly correlated with long load times
Time to Interactive 21.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 6990 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Keep request counts low and transfer sizes small 94 requests • 6,477 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift 0.026
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Meaningful Paint 3.4 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid serving legacy JavaScript to modern browsers Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoid chaining critical requests 20 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Defer offscreen images Potential savings of 2,216 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint 27.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Potential savings of 146 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Reduce JavaScript execution time 2.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links
First 20 Links Relationship HTTP Status
[email protected] Internal Link 200
Registo Internal Link 200
Login Internal Link 200
https://www.recife.com.pt/pt Internal Link 200
Peças Auto (current) Internal Link 200
Airbags Internal Link 200
AIRBAG DA CORTINA Internal Link 302
AIRBAG PASSAGEIRO Internal Link 302
ENCAIXE CINTO Internal Link 200
Fita de Airbag Internal Link 302
ver + Internal Link 302
Chaparia Internal Link 200
AMORTECEDOR MALA / CAPOT Internal Link 302
CAPOT Internal Link 200
Fechos / Ficheiras Internal Link 200
GUARDA LAMAS Internal Link 200
Mala Internal Link 200
PARA CHOQUES Internal Link 200
PORTAS Internal Link 200
Eletrica Internal Link 200

Alexa Rank

4,443,207

Global Rank

4,443,207

Global
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
recife.com.co Available
recife.com.us Available
recife.com.com Already Registered
recife.com.org Already Registered
recife.com.net Available
rcife.com.pt Available
cecife.com.pt Available
fecife.com.pt Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 302 Found
Server: nginx
Date: Fri, 02 May 2025 00:44:52 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Cache-Control: private, must-revalidate
pragma: no-cache
expires: -1
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 56
Content-Encoding: gzip
Vary: Accept-Encoding,User-Agent
Set-Cookie: XSRF-TOKEN=eyJpdiI6IkdhWFFSVHVGXC91XC9MUWptZmptMFQ0UT09IiwidmFsdWUiOiJnSTVDc1JMcXdHMVZVNno5c3Ixakh4RW00bDRHTVRVYzB6cmwyXC9GY2F5NGk5NlJrT3NRelU1TkZESFdkSVlKWUlVZURYQm5IR3Y5YVd3bXMwYzJEQXkzNDBzcE9LaWE0TU10YTBvOTVWSWpqWjBLUU5vUFlMaTY2Mzg1eUxEeFAiLCJtYWMiOiJjNWYyYmJmYjQ2NGJlNDQ0ZTdkNDI4OTVmNWYzYTdjYmQzZGI1OWZhMTljOGFlOWUwZTVjNjBhNzJmOTczMmNkIn0%3D; expires=Fri, 02-May-2025 02:44:52 GMT; Max-Age=7200; path=/
Set-Cookie: recife_session=eyJpdiI6IkNaZ3pTRk5kcXZpZ1JPWFE5QitWUnc9PSIsInZhbHVlIjoiSnZTRGxERzIyRUtYUzViWkRZMzVuVzRvZ3IzU050dnZVc09qcVhVaWxFdmtaeUJJZzRVYWI0SEkwWm5PYmJCVGt1SWJCMUNXWEFnb3hQU1J3T1hGV055M0xHbUxaUVRBUVNQa1FuNWJaYitGcjM0aU1Da2RpdXZIYW9GaEFITWciLCJtYWMiOiJkNzQ0ZDI1MTQ0ZWVhZmIzNzE0OTM4OGQ5OGM4OTg3MDg4NTRmZWZlZjI3MTE4NGExYjQzNjlhYmJiYjJmNmQ0In0%3D; expires=Fri, 02-May-2025 02:44:52 GMT; Max-Age=7200; path=/; httponly
Location: https://recife.com.pt/pt
X-Scale: YXBvY2FzQGdpdGh1Yg==
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A recife.com.pt 94.46.22.130 IN 14400
NS recife.com.pt ns8.mydnspt.net IN 21600
NS recife.com.pt ns7.mydnspt.net IN 21600
NS recife.com.pt ns2.mydnspt.net IN 21600
NS recife.com.pt ns1.mydnspt.net IN 21600
MX recife.com.pt aspmx.l.google.com IN 14400
MX recife.com.pt alt4.aspmx.l.google.com IN 14400
MX recife.com.pt alt1.aspmx.l.google.com IN 14400
MX recife.com.pt alt2.aspmx.l.google.com IN 14400
MX recife.com.pt alt3.aspmx.l.google.com IN 14400
TXT recife.com.pt v=spf1 +ip4:94.46.22.130 +include:_spf.google.com ~all IN 3600
TXT recife.com.pt google-site-verification=X2tNt-Pq1Yc0cZiTOAGZ6WMgSd0mA-5ZOl1fDCb7Uas IN 3600

About Us

We provide SEO metrics for your website. There are many who have trusted on us and improved their position thanks to our recommendations

Contact Info

RYIN
10407 Feeney Trafficway Apt. 577
Maryland Line
1-760-992-3170
[email protected]

Follow Us

Facebook
© Copyright 2023
Languages | English