Your Website Score is

Similar Ranking

19
F.A.C.E. THE AGENCY: TRAINING & BUSINESS DEVELOPMENT FIRM
face-theagency.com
19
HEALTH, FITNESS, AND TRAINING EQUIPMENT | HUNGRY4FITNESS
hungry4fitness.co.uk
19
微赞 - 企业直播营销平台,为企业提供专业微信直播方案(广州赞赏信息科技有限公司)
vzan.com
19
DIGITBINARY.COM - TECHNOLOGY EDUCATION - DIGITAL TRANSFORMATION
digitbinary.com
19
SECOND EARTH FOUNDATION SOUND HEALING THERAPY & RAISE VIBES
secondearthfoundation.com
19
GÖÇÜK AKADEMISI BOYASIZ GÖÇÜK DÜZELTME DOLU HASARI ONARIMI
gocukakademisi.com
19
THE PREMIUM MILITARY GEAR COMPANY IN --- - OLIVE PLANET
oliveplanet.in

Latest Sites

2
YOUTUBE
youtu.be
19
MEMPHIS MANSION | EN HYLDEST TIL ELVIS - KONGEN AF ROCK'N'ROLL
memphismansion.com
19
TROUVEZ UN SPÉCIALISTE EN MÉDECINE ALTERNATIVE DANS VOTRE RÉGION
medicalt.fr
19
WEBDESIGNER ET GRAPHISTE WORDPRESS FREELANCE
webdesigner-freelance.fr
31
DEL ANDUJAR | PRIVACY ADVOCATE & DIGITAL FREEDOM BUILDER
delandujar.com

Top Technologies

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

19 americanfireplace.net Last Updated: 2 weeks

Success 47% of passed verification steps
Warning 30% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 70%
Best Practices Desktop Score 96%
SEO Desktop Score 100%
Performance Mobile Score 60%
Best Practices Mobile Score 93%
SEO Mobile Score 100%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 63 Characters
AMERICAN FIREPLACE SHOWROOM, FIREPLACE & BARBEQUES MICHIGAN
Meta Description 174 Characters
American Fireplace Showroom, visit the largest Fireplace Showroom in Michigan! American Fireplace & Barbeque Distributors, a new level of fireplace & barbeque designs
Effective URL 29 Characters
https://americanfireplace.net
Excerpt Page content
American Fireplace Showroom, Fireplace & Barbeques Michigan Skip to content ...
Keywords Cloud Density
fireplaces60 astria34 fireplace33 screens22 vent17 free17 outdoor16 wood16 lighting14 ironstrike12
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
fireplaces 60
astria 34
fireplace 33
screens 22
vent 17
free 17
outdoor 16
wood 16
lighting 14
ironstrike 12
Google Preview Your look like this in google search result
AMERICAN FIREPLACE SHOWROOM, FIREPLACE & BARBEQUES MICHI
https://americanfireplace.net
American Fireplace Showroom, visit the largest Fireplace Showroom in Michigan! American Fireplace & Barbeque Distributors, a new level of fireplac
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~153.82 KB
Code Size: ~120.82 KB
Text Size: ~33.01 KB Ratio: 21.46%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Properly size images Est savings of 349 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Server Backend Latencies 10 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
Eliminate render-blocking resources Est savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid an excessive DOM size 1,160 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)
Font display Est savings of 60 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Cumulative Layout Shift 0.393
Cumulative Layout Shift measures the movement of visible elements within the viewport
Time to Interactive 1.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoid serving legacy JavaScript to modern browsers Est savings of 19 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Avoids enormous network payloads Total size was 1,260 KiB
Large network payloads cost users real money and are highly correlated with long load times
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Use efficient cache lifetimes Est savings of 16 KiB
A long cache lifetime can speed up repeat visits to your page
Legacy JavaScript Est savings of 20 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Initial server response time was short Root document took 580 ms
Keep the server response time for the main document short because all other requests depend on it
Render blocking requests Est savings of 530 ms
Requests are blocking the page's initial render, which may delay LCP
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 1 resource found
A long cache lifetime can speed up repeat visits to your page
Improve image delivery Est savings of 362 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Document request latency Est savings of 750 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Avoid chaining critical requests 44 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
Reduce unused CSS Est savings of 119 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Reduce unused JavaScript Est savings of 226 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Serve images in next-gen formats Est savings of 140 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 0.7 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
Minify CSS Est savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Largest Contentful Paint element 1,880 ms
This is the largest contentful element painted within the viewport

Mobile

Mobile Screenshot
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
Serve images in next-gen formats Est savings of 116 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Document request latency Est savings of 690 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Avoid chaining critical requests 44 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
Reduce unused CSS Est savings of 119 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Minify CSS Est savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Time to Interactive 9.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Defer offscreen images Est savings of 123 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Avoids enormous network payloads Total size was 1,269 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 5.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size 1,160 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)
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
JavaScript execution time 0.6 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 Est savings of 2,270 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Legacy JavaScript Est savings of 20 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Avoid serving legacy JavaScript to modern browsers Est savings of 19 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Render blocking requests Est savings of 2,630 ms
Requests are blocking the page's initial render, which may delay LCP
Server Backend Latencies 40 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
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Font display Est savings of 120 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
First Contentful Paint 3.3 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 80 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
Reduce initial server response time Root document took 620 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused JavaScript Est savings of 226 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Improve image delivery Est savings of 245 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Serve static assets with an efficient cache policy 1 resource found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 5,260 ms
This is the largest contentful element painted within the viewport
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
Use efficient cache lifetimes Est savings of 16 KiB
A long cache lifetime can speed up repeat visits to your page
Speed Index 4.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Cumulative Layout Shift 0.233
Cumulative Layout Shift measures the movement of visible elements within the viewport

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
Warning! Your title is not optimized
Description Website
Warning! Your description is not 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
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
americanfireplace.co Available
americanfireplace.us Available
americanfireplace.com Already Registered
americanfireplace.org Available
americanfireplace.net Already Registered
aericanfireplace.net Available
qmericanfireplace.net Available
zmericanfireplace.net Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 12 Aug 2025 12:19:42 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Link: ; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Set-Cookie: PHPSESSID=e94246569644006eb6392a86c47259e1; path=/
X-Httpd: 1
Host-Header: 8441280b0c35cbc1147f8ba998a563a7
X-Proxy-Cache-Info: DT:1
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records