Health report : http://Flamingchocolates.ca

Follow recommendations of this health report to keep your site healthy

Examined at : 2021-06-16 16:28:17

Vancouver SEO found 13 major issues

Score

page title

page title : Flaming Chocolates - Bean to Bar, Chocolate, Chocolatier


Your page title does not exceed 60 characters. It's fine.

Knowledge Base
Title is the heading of the webpage. The sentence or string enclosed between html title tag () is the title of your website. Search engines searches for the title of your website and displays title along with your website address on search result. Title is the most important element for both SEO and social sharing. Title should be less than 50 to 60 characters because search engine typically displays this length of string or sentence on search result. A good title can consist the primary keyword, secondary keyword and brand name. For example a fictitious gaming information providing sites title may be like "the future of gaming information is here". A webpage title should contain a proper glimpse of the website. title is important element as an identification of your website for user experience, SEO and social sharing. So have a nice and catching title.
Learn more

Meta Description

Meta Description : Sustainable small batch bean to bar chocolate locally made in North Vancouver, BC


Your meta description does not exceed 150 characters. It's fine.

Knowledge Base
Description is the full interpretation of your website content and features. Most often it is a short paragraph that describe what are features and information provided by the website to its visitors. You may consider it a advertising of your website. Although not important for search engine ranking but very important for hits or visits through search engine results. Description should be less than 150 character because search engine shows this length of paragraph on search result. And every page of website should contain an unique description to avoid description duplication. Description is the definition of your website for user experience so form it as complete but short and precise illustration of your website.

Meta Keyword

Meta Keyword :


Your site do not have any meta keyword.

Knowledge Base
Meta keywords are keywords inside Meta tags. Meta keywords are not likely to be used for search engine ranking. the words of title and description can be used as meta keywords. it is a good idea for SEO other than search engine ranking.

Single Keywords

Keyword Occurrence Density Possible Spam
Chocolates 8 3.042 % No
Orders 8 3.042 % No
Account 6 2.281 % No
Fire? 6 2.281 % No
Sign 4 1.521 % No
EAT 4 1.521 % No
Flaming 4 1.521 % No
EXPERIENCE 4 1.521 % No
CHOCOLATE 4 1.521 % No
chocolate 4 1.521 % No
Store 4 1.521 % No
Custom 4 1.521 % No
beans 3 1.141 % No
cocoa 3 1.141 % No
Home 3 1.141 % Yes
website 3 1.141 % No
cookies 3 1.141 % No
Bean 3 1.141 % No
Bar 3 1.141 % No
ITDON’T 2 0.76 % No

Two Word Keywords

Keyword Occurrence Density Possible Spam
the Chocolates 6 2.281 % No
on Fire? 6 2.281 % No
Are the 6 2.281 % No
Chocolates on 6 2.281 % No
Custom Orders 4 1.521 % No
About Store 4 1.521 % No
JUST EAT 4 1.521 % No
My Account 4 1.521 % No
Orders My 4 1.521 % No
CHOCOLATE EXPERIENCE 4 1.521 % No
EAT CHOCOLATE 4 1.521 % No
Fire? Are 3 1.141 % No
to Bar 3 1.141 % No
cocoa beans 3 1.141 % No
Bar About 3 1.141 % No
Home Custom 3 1.141 % No
Orders Bean 3 1.141 % No
Bean to 3 1.141 % No
Sign In 2 0.76 % No
EXPERIENCE ITDON’T 2 0.76 % No

Three Word Keywords

Keyword Occurrence Density Possible Spam
Are the Chocolates 6 2.281 % No
the Chocolates on 6 2.281 % No
Chocolates on Fire? 6 2.281 % No
EAT CHOCOLATE EXPERIENCE 4 1.521 % No
JUST EAT CHOCOLATE 4 1.521 % No
Orders My Account 4 1.521 % No
on Fire? Are 3 1.141 % No
to Bar About 3 1.141 % No
Bean to Bar 3 1.141 % No
Orders Bean to 3 1.141 % No
Custom Orders Bean 3 1.141 % No
Home Custom Orders 3 1.141 % No
Bar About Store 3 1.141 % No
Fire? Are the 3 1.141 % No
Account Sign out 2 0.76 % No
CHOCOLATE EXPERIENCE IT 2 0.76 % No
Account Orders My 2 0.76 % No
DON’T JUST EAT 2 0.76 % No
ITDON’T JUST EAT 2 0.76 % No
EXPERIENCE ITDON’T JUST 2 0.76 % No

Four Word Keywords

Keyword Occurrence Density Possible Spam
the Chocolates on Fire? 6 2.281 % No
Are the Chocolates on 6 2.281 % No
JUST EAT CHOCOLATE EXPERIENCE 4 1.521 % No
on Fire? Are the 3 1.141 % No
Home Custom Orders Bean 3 1.141 % No
Fire? Are the Chocolates 3 1.141 % No
to Bar About Store 3 1.141 % No
Orders Bean to Bar 3 1.141 % No
Custom Orders Bean to 3 1.141 % No
Bean to Bar About 3 1.141 % No
Chocolates on Fire? Are 3 1.141 % No
ITDON’T JUST EAT CHOCOLATE 2 0.76 % No
My Account Sign out 2 0.76 % No
DON’T JUST EAT CHOCOLATE 2 0.76 % No
Account Orders My Account 2 0.76 % No
EAT CHOCOLATE EXPERIENCE IT 2 0.76 % No
Signed in as fillergodaddycom 2 0.76 % No
EAT CHOCOLATE EXPERIENCE ITDON’T 2 0.76 % No
CHOCOLATE EXPERIENCE ITDON’T JUST 2 0.76 % No
EXPERIENCE ITDON’T JUST EAT 2 0.76 % No

Keyword Usage

The most using keywords do not match with meta keywords.

Knowledge Base
Keyword usage is the using of your keywords inside Meta tags and contents of your website. Use keywords that describes your site properly for precise search engine result of your website.

Total Words

Total Words : 263

Knowledge Base
Unique words are uncommon words that reflects your site features and informations. Search engine metrics are not intended to use unique words as ranking factor but it is still useful to get a proper picture of your site contents. Using positive unique words like complete, perfect, shiny, is a good idea user experience.

Stop words are common words like all the preposition, some generic words like download, click me, offer, win etc. since most used keyword may be a slight factor for visitors you are encouraged to use more unique words and less stop words.

Text/HTML Ratio Test

Site failed text/HTML ratio test.

Text/HTML Ratio Test : 2%

Knowledge Base
The ideal page's ratio of text to HTML code must be lie between 20 to 60%. Because if it is come less than 20% it means you need to write more text in your web page while in case of more than 60% your page might be considered as spam.

HTML Headings

H1(0)

H2(0)

H3(0)

H4(0)

H5(0)

H6(0)

Knowledge Base
h1 status is the existence of any content inside h1 tag. Although not important like Meta titles and descriptions for search engine ranking but still a good way to describe your contents in search engine result.

h2 status less important but should be used for proper understanding of your website for visitor.

Robot.txt

Your site have robot.txt

Robot.txt

> User-agent: *




Knowledge Base
robots.txt is text file that reside on website root directory and contains the instruction for various robots (mainly search engine robots) for how to crawl and indexing your website for their webpage. robots.txt contains the search bots or others bots name, directory list allowed or disallowed to be indexing and crawling for bots, time delay for bots to crawl and indexing and even the sitemap url. A full access or a full restriction or customized access or restriction can be imposed through robots.txt.

robots.txt is very important for SEO. Your website directories will be crawled and indexed on search engine according to robots.txt instructions. So add a robots.txt file in your website root directory. Write it properly including your content enriched pages and other public pages and exclude any pages which contain sensitive information. Remember robots.txt instruction to restrict access to your sensitive information of your page is not formidable on web page security ground. So do not use it on security purpose.
Learn more

Sitemap

Your site have sitemap
Location: http://Flamingchocolates.ca/sitemap.xml

Knowledge Base
Sitemap is a xml file which contain full list of your website urls. It is used to include directories of your websites for crawling and indexing for search engine and access for users. it can help search engine robots for indexing your website more fast and deeply. It is roughly an opposite of robots.txt You can create a sitemap.xml by various free and paid service or you can write it with proper way (read about how write a sitemap).

Also keep these things in mind:
1) Sitemap must be less than 10 MB (10,485,760 bytes) and can contain maximum 50,000 urls. if you have more uls than this create multiple sitemap files and use a sitemap index file.
2) Put your sitemap in website root directory and add the url of your sitemap in robots.txt.
3) sitemap.xml can be compressed using grip for faster loading.

Broken link: a broken link is an inaccessible link or url of a website. a higher rate of broken links have a negative effect on search engine ranking due to reduced link equity. it also has a bad impact on user experience. There are several reasons for broken link. All are listed below.
1) An incorrect link entered by you.
2) The destination website removed the linked web page given by you. (A common 404 error).
3) The destination website is irreversibly moved or not exists anymore. (Changing domain or site blocked or dysfunctional).
4) User may behind some firewall or alike software or security mechanism that is blocking the access to the destination website.
5) You have provided a link to a site that is blocked by firewall or alike software for outside access.
Learn more or Learn more

Internal Vs. External Links

Total Internal Links? 33
Total External Links? 9

Internal Links

  • /
  • /m/account
  • /m/create-account
  • /m/orders
  • /m/account
  • /m/orders
  • /m/account
  • /
  • /custom-orders
  • /bean-to-bar
  • /about
  • /store
  • /
  • /custom-orders
  • /bean-to-bar
  • /about
  • /store
  • /
  • /
  • /custom-orders
  • /bean-to-bar
  • /about
  • /store
  • /m/orders
  • /m/account
  • /m/account
  • /m/orders
  • /m/account
  • /store/ols/all?sortOption=descend_by_created_at
  • /custom-orders
  • /privacy-policy
  • /about
  • /store

External Links

  • https://www.facebook.com/292614011437851
  • https://www.instagram.com/flamingchocolates
  • https://flamingchocolates.ca/store?olsPage=cart
  • https://flamingchocolates.ca/store?olsPage=cart
  • https://www.facebook.com/292614011437851
  • https://www.instagram.com/flamingchocolates
  • https://www.facebook.com/292614011437851
  • https://www.instagram.com/flamingchocolates
  • https://www.godaddy.com/websites/website-builder?isc=pwugc&utm_source=wsb&utm_medium=applications&utm_campaign=en-ca_corp_applications_base

Alexa Rank

>
Traffic Rank no data
Reach Rank no data
Top Country
Top Country Rank

Domain IP Information

ISP GoDaddy.com, LLC
IP 72.167.191.69
Organization GoDaddy.com, LLC
City
Country United States
Time Zone
Longitude -97.822000
Latitude 37.751000

NoIndex , NoFollow, DoDollow Links

Total NoIndex Links 0
Total NoFollow Links 1
Total DoFollow Links 41
NoIndex Enabled By Meta Robot? No
NoFollow Enabled By Meta Robot? No

NoIndex Links

NoFollow Links



Knowledge Base

NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.

By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" /> directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).

DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.

By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a> if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.

Learn more

SEO Friendly Links

Some links of your site are not SEO friendly.

Not SEO Friendly Links

  • /store/ols/all?sortOption=descend_by_created_at


Knowledge Base
An SEO friendly link is roughly follows these rules. The url should contain dash as a separator, not to contain parameters and numbers and should be static urls.

To resolve this use these techniques.
1) Replace underscore or other separator by dash, clean url by deleting or replaceing number and parameters.
2) Marge your www and non www urls.
3) Do not use dynamic and related urls. Create an xml sitemap for proper indexing of search engine.
4) Block unfriendly and irrelevant links through robots.txt.
5) Endorse your canonical urls in canonical tag.
Learn more

Favicon

Your site does not have favicon.

Learn more

Image 'alt' Test

Your site have 1 images without alt text.

Images Without alt

  • data:image/gif;base64,R0lGODlhAQABAAD/ACwAAAAAAQABAAACADs=


Knowledge Base
An alternate title for image. Alt attribute content to describe an image. It is necessary for notifying search engine spider and improve actability to your website. So put a suitable title for your image at least those are your website content not including the images for designing your website. To resolve this put a suitable title in your alt attributes.
Learn more

DOC Type

DOC Type :


Page do not have doc type

Knowledge Base
doc type is not SEO factor but it is checked for validating your web page. So set a doctype at your html page.
Learn more

Depreciated HTML Tag

Your site does not have any depreciated HTML tag.

Knowledge Base
Older HTML tags and attributes that have been superseded by other more functional or flexible alternatives (whether as HTML or as CSS ) are declared as deprecated in HTML4 by the W3C - the consortium that sets the HTML standards. Browsers should continue to support deprecated tags and attributes, but eventually these tags are likely to become obsolete and so future support cannot be guaranteed.

HTML Page Size

HTML Page Size : 121 KB


HTML page size is > 100KB

Knowledge Base
HTML page size is the one of the main factors of webpage loading time. It should be less than 100 KB according to google recommendation. Note that, this size not including external css, js or images files. So small page size less loading time.

To reduce your page size do this steps
1) Move all your css and js code to external file.
2) make sure your text content be on top of the page so that it can displayed before full page loading.
3) Reduce or compress all the image, flash media file etc. will be better if these files are less than 100 KB
Learn more

GZIP Compression

GZIP compression is disabled.

Knowledge Base
GZIP is a generic compressor that can be applied to any stream of bytes: under the hood it remembers some of the previously seen content and attempts to find and replace duplicate data fragments in an efficient way - for the curious, great low-level explanation of GZIP. However, in practice, GZIP performs best on text-based content, often achieving compression rates of as high as 70-90% for larger files, whereas running GZIP on assets that are already compressed via alternative algorithms (e.g. most image formats) yields little to no improvement. It is also recommended that, GZIP compressed size should be <=33 KB

Inline CSS

Your site does not have any inline css.

Knowledge Base
Inline css is the css code reside in html page under html tags not in external .css file. Inline css increases the loading time of your webpage which is an important search engine ranking factor. So try not to use inline css.

Internal CSS

Your site does not have any internal css.

Knowledge Base
Internal css is the css codes which resides on html page inside style tag. Internal css is increases loading time since no page caching is possible for internal css. Try to put your css code in external file.

Micro Data Schema Test

Site failed micro data schema test.

Knowledge Base
Micro data is the information underlying a html string or paragraph. Consider a string “Avatar”, it could refer a profile picture on forum, blog or social networking site or may it refer to a highly successful 3D movie. Microdot is used to specify the reference or underlying information about an html string. Microdata gives chances to search engine and other application for better understanding of your content and better display significantly on search result.
Learn more

IP & DNS Report

IPv4 72.167.191.69
IPv6 Not Compatiable
DNS Report
SLHostClassTTLTypePRITargetIP
1Flamingchocolates.caIN3600A72.167.191.69
2Flamingchocolates.caIN3600NSns76.domaincontrol.com
3Flamingchocolates.caIN3600NSns75.domaincontrol.com
4Flamingchocolates.caIN3600MX20mx2.zoho.com
5Flamingchocolates.caIN3600MX10mx.zoho.com
6Flamingchocolates.caIN3600MX30mx3.zoho.com

IP Canonicalization Test

Site failed IP canonicalization test.

Knowledge Base
If multiple domain name is registered under single ip address the search bots can label other sites as duplicates of one sites. This is ip canonicalization. Little bit like url canonicalizaion. To solve this use redirects.
Learn more

URL Canonicalization Test

Site failed URL canonicalization test.

Knowledge Base
Canonical tags make your all urls those lead to a single address or webpage into a single url. Like :
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
Both refer to the link mywebsite.com/home. So all the different url with same content or page now comes under the link or url mywebsite.com/home. Which will boost up your search engine ranking by eliminating content duplication. Use canonical tag for all the same urls.
Learn more

Plain Text Email Test

Site failed plain text email test. 2 plain text email found.

Plain Text Email List



Knowledge Base
Plain text email address is vulnerable to email scrapping agents. An email scrapping agent crawls your website and collects every Email address which written in plain text. So existence of plain text email address in your website can help spammers in email Harvesting. This could be a bad sign for search engine.

To fight this you can obfuscate your email addresses in several ways:
1) CSS pseudo classes.
2) Writing backward your email address.
3) Turn of display using css.
4) Obfuscate your email address using javascript.
5) Using wordpress and php (wordpress site only).
Learn more

CURL Response

urlhttps://flamingchocolates.ca/content typetext/html;charset=utf-8
http code200header size2451
request size310filetime-1
ssl verify result0redirect count1
total time0.34879namelookup time0.122402
connect time0.154785pretransfer time0.20008
size upload0size download124354
speed download357339speed upload0
download content length-1upload content length-1
starttransfer time0.304765redirect time0.112312
redirect urlprimary ip72.167.191.69
certinfoprimary port443
local ip68.65.123.107local port53306
http version3protocol2
ssl verifyresult0schemeHTTPS
appconnect time us126081connect time us154785
namelookup time us122402pretransfer time us200080
redirect time us112312starttransfer time us304765
total time us348790

PageSpeed Insights (Mobile)

Performance

  • Emulated Form Factor Mobile
  • Locale En-US
  • Category Performance
  • Field Data
  • First Contentful Paint (FCP)
  • FCP Metric Category
  • First Input Delay (FID)
  • FID Metric Category
  • Overall Category
  • Origin Summary
  • First Contentful Paint (FCP)
  • FCP Metric Category
  • First Input Delay (FID)
  • FID Metric Category
  • Overall Category
  • Lab Data
  • First Contentful Paint 1.4 s
  • First Meaningful Paint 1.4 s
  • Speed Index 2.2 s
  • First CPU Idle
  • Time To Interactive 5.3 s
  • Max Potential First Input Delay 290 ms

Audit Data

Keep request counts low and transfer sizes small

48 requests • 649 KiB

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

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 More

Efficiently encode images

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

Enable text compression

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

Uses efficient cache policy on static assets

0 resources found

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

Reduce the impact of third-party code

Third-party code blocked the main thread for 330 ms

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

First Contentful Paint (3G)

2583 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More

Total Blocking Time

430 ms

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

JavaScript execution time

1.0 s

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

Defer offscreen images

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

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. Learn More

Properly size images

Potential savings of 179 KiB

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

Reduce unused CSS

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

Avoids enormous network payloads

Total size was 649 KiB

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

Minimize main-thread work

2.1 s

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

Avoid chaining critical requests

2 chains found

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

Avoids an excessive DOM size

352 elements

A large DOM will increase memory usage, cause longer Learn More

Avoid multiple page redirects

Potential savings of 630 ms

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

Minify JavaScript

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

User Timing marks and measures

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

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. Learn More

PageSpeed Insights (Desktop)

Performance

  • Emulated Form Factor Desktop
  • Locale En-US
  • Category Performance
  • Field Data
  • First Contentful Paint (FCP)
  • FCP Metric Category
  • First Input Delay (FID)
  • FID Metric Category
  • Overall Category
  • Origin Summary
  • First Contentful Paint (FCP)
  • FCP Metric Category
  • First Input Delay (FID)
  • FID Metric Category
  • Overall Category
  • Lab Data
  • First Contentful Paint 0.4 s
  • First Meaningful Paint 0.4 s
  • Speed Index 0.8 s
  • First CPU Idle
  • Time To Interactive 1.1 s
  • Max Potential First Input Delay 70 ms

Audit Data

Keep request counts low and transfer sizes small

50 requests • 562 KiB

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

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 More

Efficiently encode images

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

Enable text compression

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

Uses efficient cache policy on static assets

0 resources found

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

Minimize third-party usage

Third-party code blocked the main thread for 20 ms

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

Total Blocking Time

10 ms

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

JavaScript execution time

0.1 s

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

Defer offscreen images

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

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. Learn More

Properly size images

Potential savings of 87 KiB

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

Reduce unused CSS

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

Avoids enormous network payloads

Total size was 562 KiB

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

Minimizes main-thread work

0.5 s

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

Avoid chaining critical requests

2 chains found

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

Avoids an excessive DOM size

354 elements

A large DOM will increase memory usage, cause longer Learn More

Avoid multiple page redirects

Potential savings of 190 ms

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

Minify JavaScript

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

User Timing marks and measures

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

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. Learn More