Public review for: "roastme.xyz"

This is a public partial review example, the complete professional review convines automatic review, first-class tools & manual review with the subjective prespective of the experts. The complete review offers solutions to the detected problems either in the automatic & manual review.

Disclaimer: This review uses among others, external tools, to analyze some aspects of the product, like the privacity, security, usability, etc. It convines a wide range of tools, software & manual review to provide a full documentation of your product.

37
roastme.xyz Screenshot

roastme.xyz

September 21, 2018 3:37 PM
Passed
0%
To Improve
0%
Errors
0%

Stats

40
Requests

5
Ad-blocked

0
Malicious

100%
HTTPS

83%
IPv6

6
Domains

6
Subdomains

6
IPs

3
Countries

1,991kB
Transfer

2,180kB
Size

2
Cookies

Privacy

The server roastme.xyz (217.160.0.242) appears to have been located in Germany during our test.

Please note that some sites use CDNs – content delivery networks – in which case the server location might vary depending on the location of the visitor. This tool, Webbkoll, is currently on a server in France.

Insecure connection

roastme.xyz does not use HTTPS by default.

HTTPS encrypts nearly all information sent between a client and a web service. Properly configured, it guarantees three things:

  • Confidentiality. The visitor's connection is encrypted, obscuring URLs, cookies, and other sensitive metadata.
  • Authenticity. The visitor is talking to the "real" website, and not to an impersonator or through a "man-in-the-middle".
  • Integrity. The data sent between the visitor and the website has not been tampered with or modified.

A plain HTTP connection can be easily monitored, modified, and impersonated. Every unencrypted HTTP request reveals information about a user’s behavior, and the interception and tracking of unencrypted browsing has become commonplace.

The goal of the Internet community is to establish encryption as the norm, and to phase out unencrypted connections. See W3C, IETF, IAB. Also:

  • Browsers support HTTP/2 β€” which improves page loading speeds β€” only over encrypted connections.
  • Google Chrome (1, 2) and Mozilla Firefox (1) will mark plain HTTP as affirmatively non-secure and make powerful features impossible to use on non-secure sites.
  • Google has begun to favor HTTPS websites in search rankings.

To enable HTTPS on a website, a certificate for the domain needs to be installed on the web server. To get a certificate that browsers will trust, you need one issued by a trusted certificate authority (otherwise a visitor's browser will show a warning).

Let's Encrypt is a non-profit certificate authority (sponsored by Mozilla, EFF, Cisco, Facebook and others) providing free domain-validated (DV) certificates through an easy, automated process.

To get a DV certificate, you only need to prove that you control the domain. To get an Extended Validation (EV) certificate, you must pass a more thorough identity verification process.

There is no difference in encryption between DV and EV certificates, but they are typically displayed differently in browsers. EV certificates generally result in the domain owner's name appearing in the browser URL bar that visitors see.

DV certificates are the most common. Let's Encrypt only issues DV certificates.

Referrers leaked

When you click a link, your browser will typically send the HTTP referer [sic] header to the webserver where the destination webpage is at. The header contains the full URL of the page you came from. This lets sites see where traffic comes from. The header is also sent when external resources (such as images, fonts, JS and CSS) are loaded.

The referrer header is privacy nightmare as it allows websites and services to track you across the web and learn about your browsing habits (and thus possibly private, sensitive information), particularly when combined with cookies.

Let's say you're logged in on Facebook. You visit a page with the URL http://www.some-hospital.com/some-medical-condition. On that page, you click a link to their Facebook page. Your browser then sends Referer: http://www.some-hospital.com/some-medical-condition to facebook.com, along with your Facebook cookies, allowing Facebook to associate your identity with that particular page.

The problem is made worse by the fact that many websites load resources like images and scripts from dozens of third-parties, sending referrer information to all of them, with the typical visitor having no idea that this is happening.

Thanks to a fairly recent development, Referrer Policy, it's finally possible for websites to tell browsers to not leak referrers. It lets you specify a policy that's applied to all links clicked, as well as all other requests generated by the page (images, JS, etc.).

A few different policies are offered, such as origin (strips everything except the origin) and origin-when-cross-origin (sends full URL with same-origin requests, otherwise stripped). We recommend no-referrer, which kills the referrer header entirely for all requests, no matter the destination; or same-origin, which kills the referrer for third-party requests but not for requests to the same origin.

A referrer policy can easily be set with a <meta> element in your HTML. Simply include this inside the <head> section:

<meta name="referrer" content="no-referrer">

While still a work in progress, Referrer Policy is now supported by all major browsers (except Internet Explorer, although it is supported by Edge, the new browser in Windows 10).

Third-party services

The site is using Google Analytics. While this is a powerful tool, we think you should respect your users' privacy and not tell Google about them β€” at least not without your users' consent.

Matomo (formerly Piwik) is an excellent alternative. It's free software (PHP & MySQL) and you run it on your own server, meaning you are in control of the data. It offers various privacy settings and, unlike Google Analytics, it can be used without cookies. (While analytics might be considered essential by some websites, another alternative is don't track people just because you can. Visitors do not, in fact, have an implicit obligation to help you optimize things.)

First-party cookies

9 first-party cookies.

Domain Name Value Expires on
.roastme.xyz _gat_gtag_UA_125015920_1 1 2018-09-27 11:31:10Z
.roastme.xyz _ga GA1.2.262052316.1538... 2020-09-26 11:30:10Z
.roastme.xyz __stripe_sid f924fa22-005b-41ca-9... 2018-09-27 12:00:10Z
.roastme.xyz _gid GA1.2.886018293.1538... 2018-09-28 11:30:10Z
.roastme.xyz __stripe_mid 972a1065-09a9-4674-b... 2019-09-27 11:30:10Z
roastme.xyz XSRF-TOKEN eyJpdiI6ImVhT3FjRlQ3... 2018-09-27 13:30:12Z
roastme.xyz roastme_session eyJpdiI6IitDUWZSUFpn... 2018-09-27 13:30:12Z
roastme.xyz PHPSESSID 6549b7767b1b31578f15... session
roastme.xyz please_change_this_cookie_name eyJpdiI6Ik8yYng2aUMw... session

Third-party cookies

2 third-party cookies.

Domain Name Value Expires on
.m.stripe.com m cd025fbd-8bf9-41fe-8... 2028-09-24 11:30:13Z
m.stripe.network nsr 1 session

Third-party requests

30 requests (30 secure, 0 insecure) to 9 unique hosts.

A third-party request is a request to a domain that's not roastme.xyz or one of its subdomains.

Host Classification
fonts.gstatic.com Content (Google)
js.stripe.com
m.stripe.com
m.stripe.network
pbs.twimg.com Disconnect (Twitter)
q.stripe.com
stripensrq.global.ssl.fastly.net
www.google-analytics.com Disconnect (Google)
www.googletagmanager.com Disconnect (Google)

We use Disconnect's open source list of trackers to classify hosts.

Full list of third-party requests:

Content-Security-Policy not enabled

Content Security Policy is an effective measure to protect your site from XSS attacks. By whitelisting sources of approved content, you can prevent the browser from loading malicious assets. It can also help prevent information leakage.

report-uri.io has excellent (free) tools with which you can build or analyze a Content Security Policy.

HTTP headers

Header
Set?
Referrer-Policy
NO

Referrer-Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document (or when loading external resources) and should be set by all sites. (It can also be set using a meta element; see above.)

Strict-Transport-Security
NO

HTTP Strict Transport Security is an excellent feature to support on your site and strengthens your implementation of TLS by getting the User Agent to enforce the use of HTTPS.

X-Content-Type-Options
NO

X-Content-Type-Options stops a browser from trying to MIME-sniff the content type and forces it to stick with the declared content-type. This helps to reduce the danger of drive-by downloads. The only valid value for this header is "X-Content-Type-Options: nosniff".

X-Frame-Options
NO

X-Frame-Options tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking.

X-Xss-Protection
NO

X-XSS-Protection sets the configuration for the cross-site scripting filters built into most browsers. The best configuration is "X-XSS-Protection: 1; mode=block".

Marketing Checklist

Configure your domain redirects from non-original pages versions Top Priority

High impact Easy to solve for Developer

Why it's important

Search engines do not like pages which duplicate large amounts of content on the same website, which can happen when the same page, due to Web configuration or CMS issues, is shown in different URLs.

A common scenario for this issue is found when the non-www and the www version of your site both feature your content. For example, when www.domain.com and domain.com show the home page information.

You should pick either version to show your site content and use 301 redirects to refer from the non-original page versions to the original ones, making show you only show each page through one URL.

Getting it done

A 301 Redirect should be used to refer from the non-original URLs to the original ones.

If you are creating other subdomains, use relevant keywords and avoid duplicate content.
Check if your homepage is correctly redirecting to the original URL version with the WWW Resolve criteria under the SEO section in your WooRank Reviews.

Optimize images for your website

Medium impact Easy to solve for Marketer

Why it's important

An accurate text description of an image is valuable to search engines, and visually-impaired or blind website visitors. It’s also valuable to websites in potentially generating traffic from image searches as well as avoiding losing potential customers.

This text is contained in the Alternative Text or β€˜Alt’ attribute, which is seen by search engines, various social image sharing sites (e.g Pinterest), and is converted to speech by software for the visually impaired. This makes an accurate description of the content of the image highly important.

Getting it done

Ensure your descriptions are accurate for the content of the image.

Avoid Alt Text longer than seven words. The absolute maximum would be 150 characters including spaces.

Use the most relevant descriptive keyword, and avoid repetitive keyword stuffing.

Consider how users performing an image search may look for different attributes than a web search.

File names and captions should also be logical. Images should also be optimised for load times, but larger and higher quality pictures will perform better in image search results.
Check for Alt Attributes in your WooRank Review under SEO > Images.

Develop frequent shareworthy content in your site blog

High impact Hard to solve for Marketer

Why it's important

Blogs are a great way to publish fresh content on a regular basis to your site, attracting visitors and helping it to rank for your desired keywords.

Given the huge rise in business blogging, it’s important to make sure you are publishing content that your audience will find useful, attractive and therefore recommend and share. Balance self-promotion with valuable resources for your industry and customers, insights into your business, and content which helps to build the community in your industry.

Getting it done

Ensure your blog is set up on your domain, e.g. http://blog.example.com, or http://www.example.com/blog/ rather than using an external platform, such as Blogger, Tumblr, etc. Optimize the design, and avoid slowing page loads by adding sidebar widgets that won’t be useful for your readers.

Plan an Editorial Calendar to set out the keywords and subjects you will target, and supplement this with monitoring news and trending keywords relevant to your business.

Register your blog with directories such as Technorati, Google+ Publisher and the Authorship markup.

Optimize each post for SEO, and promote each one on Social Media. While SEO titles should be factual for the keywords to target, social media promotion should be rewritten to be more enticing.

Monitor and respond to comments promptly. Services such as Akismet and Disqus can help to tackle and reduce spam comments.
Check if your blog is being found in your WooRank Review by visiting the SEO section.
Optimize

SEO

Title Tag

RoastMe - Give & receive reviews from users and experts

Length: 55 character(s)

Your HTML title tag appears in browser tabs, bookmarks and in search result pages.

Make your title tags clear, concise (50-60 characters) and include your most important keywords.

Check the title of your website

Meta Description

Get real feedback πŸ”₯ and critics 🎯 from expert users for your product / design / idea!

Length: 87 character(s)

Great, your meta description contains between 70 and 320 characters (spaces included).

A good meta description acts as an organic advertisement, so use enticing messaging with a clear call to action to maximize click-through rate. They allow you to influence how your web pages are described and displayed in search results.

Ensure that all of your web pages have a unique meta description that is explicit and contains your most important keywords (these appear in bold when they match part or all of the user’s search query).

Check your Google Search Console account (Click 'Search Appearance', then 'HTML Improvements') to identify any issues with your meta descriptions, for example, they are too short/long, or duplicated across more than one page.

Improve the Meta Description

Google Preview

RoastMe - Give & receive reviews from users and experts

roastme.xyz/

Get real feedback πŸ”₯ and critics 🎯 from expert users for your product / design / idea!

This is a representation of what your Title Tag and Meta Description will look like in Google search results.

Search engines may create their own titles and descriptions if they are missing, poorly written and/or not relevant to the content on the page and cut short if they go over the character limit. So it’s important to be clear, concise and within the suggested character limit.

Headings

<H1> <H2> <H3> <H4> <H5>
5 10 22 0 1
<H1> Roast my design idea web app product
<H1> FibreTiger | Compare ISPs
<H1> Reakit
<H1> BitBulb
<H1> roastme
<H2> Get real feedback πŸ”₯ and critics 🎯 from expert users for your product / design / idea! Give your expert review and get $
<H2> Your feedback marketplace Buy/Sell expertise
<H2> Frequently Ask Question
<H2> More Benefits
<H2> Top Roasts
<H2> Top Roasters
<H2> Sign up
<H2> Log in
<H2> Create a Roast
<H2> How it Works?:
<H3> Product / Website
<H3> Design
<H3> Idea / Business Plan
<H3> Free Roast
<H3> Pro Roast Most popular
<H3> Premium Roast -40%
<H3> Platinium Roast -50%
<H3> What is a roast ?
<H3> I have to pay to participate?
<H3> I want to contribute as an expert
<H3> I want to contribute as a user
<H3> I can do it for free at X (twitter, indie hacker, etc.)
<H3> I will get paid for being an expert?
<H3> We bring emotion
<H3> We increment visibility
<H3> We empower you
<H3> About
<H3> Free
<H3> Pro User
<H3> Pro
<H3> Premium
<H3> Platinium
<H5> Social
and 35 more.

Great, your website is structured using HTML headings (<H1> to <H6>).

Use your keywords in the headings and make sure the first level (<H1>) includes your most important keywords. Never duplicate your title tag content in your header tag.

While it is important to ensure every page has an <H1> tag, only include more than one per page if you're using HTML5. Instead, use multiple <H2> - <H6> tags.

Add the important keywords in <H> headings

Keyword Cloud

  • fibretiger compare isps 2
  • getting real feedback 2
  • expert complete feedback 2
  • real feedback 4
  • forgot password 2
  • business plan 2
  • linear gradient 2
  • rights reserved 2
  • expert feedback 2
  • idea generator 2
  • product owners 2
  • premium roast 2
  • pro roast 2
  • free roast 3
  • expert users 3
  • app 2
  • let 2
  • complete 5
  • fibretiger 3
  • plus 3

The Keyword Cloud provides an insight into how relevant a topic or keyword is to the content on your page.

It's important to do keyword research to get an understanding of the keywords that your audience is using. There are a number of keyword research tools available online to help you choose which keywords to target.

Alt Attribute

We found 17 images on this web page.

17 ALT attributes are empty or missing.

https://roastme.xyz/img/roastme.png
https://roastme.xyz/img/team_feedback_red.png
https://roastme.xyz/img/landing_img3.png
https://roastme.xyz/img/landing_img2.png
https://roastme.xyz/img/product4_draw_red.png
https://roastme.xyz/img/user_avatars/default.png
https://roastme.xyz/storage/vqGR5wcQGQ1tBHVyL0FXaTfwGn43pLqEsQZMyxt7.png
https://roastme.xyz/storage/FYmGk9f05Fco7sdzsgCLsc6olMUWKhBfUdfYkUUG.png
https://pbs.twimg.com/profile_images/651353874586955776/Mn4iHpgJ_400x400.jpg
https://roastme.xyz/storage/1wVUSSkqTuv9LzvyjfFHOr2qi5Yt1FMu4APKyhox.png
https://roastme.xyz/storage/doPpxb69VO0oFCCExYZUmsckcR1ZSjciAGnG5ViW.png
https://roastme.xyz/storage/xJewOQaRj0zccWTYkGbwZQzfgLkSDiyqDKJRM7qP.png
https://roastme.xyz/storage/litFHS9NwjoU52TOxjB3bn44dfwWPtk5nOhkF0vK.png
https://roastme.xyz/img/step5min.png
https://roastme.xyz/img/step2min.png
https://roastme.xyz/img/step3min.png
https://roastme.xyz/img/step6min.png
and 12 more.

Alternative text allows you to add a description to an image. Since search engine crawlers cannot see images, they rely on alternative text attributes to determine relevance to a search query. Alternative text also helps makes an image more likely to appear in a Google image search and is used by screen readers to provide context for visually impaired users.

It looks like you're missing alternative text for 17 images on roastme.xyz. Check the images on your website to make sure accurate and relevant alternative text is specified for each image on the page.

Try to minimize the number of alt text characters to 150 or less (including spaces!) to optimize page load times.

Set a name for all your images

Discovered Pages

35    35

We've discovered 35 pages in Google's index for roastme.xyz.

A low number can indicate that bots are unable to discover your pages, which is commonly caused by bad site architecture & internal linking, or you're unknowingly preventing bots and search engines from crawling & indexing your pages. An unusually high number could be an indication of duplicate content due to URL parameters.

Make sure your website's XML sitemap is present and that you've submitted it to the major search engines. Building backlinks to your website's internal pages will also help bots to discover, crawl and index them, while building authority to help them rank in search results at the same time.

Check Index Status and Crawl Errors in Google Search Console to track the status of your crawled/indexed pages.

If you use parameters in your URL like session IDs or sorting and filtering, use the rel="canonical" tag to tell search engines which version of those pages is the original.

Write more content

WWW Resolve

Warning, no 301 redirects are in place to redirect traffic to your preferred domain. Pages that load successfully both with and without www. are treated as duplicate content!

Right now either www.roastme.xyz or roastme.xyz is failing to resolve properly or returns a 404 error. You should set a preferred domain in Google Search Console and use a 301 redirect to divert traffic from your secondary domain.

Redirect non-www to www

Robots.txt

A robots.txt file allows you to restrict the access of search engine crawlers to prevent them from accessing specific pages or directories. They also point the web crawler to your page’s XML sitemap file.

Your site currently has a robots.txt file. You can use Google Search Console's Robots.txt Tester to submit and test your robots.txt file and to make sure Googlebot isn't crawling any restricted files.

Add a robots.txt file

XML Sitemap

No sitemap found in your robots.txt.

We checked the robots.txt file for roastme.xyz but couldn't find an XML sitemap. Specifying your XML sitemaps in your robots.txt file ensures that search engines and other crawlers find and access it easily each time they access your website.

Learn more about adding your XML sitemap to your robots.txt file here.

If you haven't created a sitemap yet, we recommend you generate one for your site and submit it through both Google Search Console and Bing Webmaster Tools. Usually, your XML sitemap would be found at roastme.xyz/sitemap.

Make sure to only include the pages you want search engines to crawl, so leave out any that have been blocked in a robots.txt file. Avoid using any URLs that cause redirects or error codes and be consistent in using your preferred URLs (with or without www.), correct protocols (http vs. https) and trailing slashes.
Add and Optimize your XML sitemap

URL Parameters

Perfect, your URLs look clean.

URL parameters are used to track user behaviors on site (session IDs), traffic sources (referrer IDs) or to give users control over the content on the page (sorting and filtering). The issue with URL parameters is that Google sees each unique parameter value as a new URL hosting the same thing - meaning you could have a duplicate content problem. Sometimes, it’s able to recognize these URLs and group them together. It then algorithmically decides which URL is the best representation of the group and uses it to consolidate ranking signals and display in search results. You can help Google recognize the best URL by using the rel="canonical" tag.

Use the URL Parameters Tool in Google Search Console to tell Google how your URL parameters affect page content and how to to crawl URLs with parameters. Use this tool very carefully - you can easily prevent Google from crawling pages you want indexed through overly restrictive crawling settings, especially if you have URLs with multiple parameters.
Rewrite your URLs and clean them up.

Underscores in the URLs

Great, you are not using β€ͺunderscores (these_are_underscores) in your URLs.

Great, you aren't using β€ͺunderscores (these_are_underscores) in your URLs.

Google sees hyphens as word separators while underscores aren't recognized. So the search engine sees www.example.com/green_dress as www.example.com/greendress. The bots will have a hard time determining this URL's relevance to a keyword.

Blocking Factors

Flash: No

Frames: No

Great, you aren't using Flash or frames on your site.

While it often looks nicer, Flash content can't be properly indexed by search engines. Maximize your SEO efforts by avoiding Flash.

Search engines also have problems with frames because they can't crawl or index the content within them. Avoid them if you can and use a NoFrames tag when you can't.

Blog

We have not found a Blog on this website.

In a crowded digital marketing world, content is king. Publishing your content on other sites is beneficial, but publishing it on your own site is much more effective. One of the best ways to do this is through a blog.

We recommend you start a blog on roastme.xyz to engage with your audience and improve your online visibility to attract qualified traffic from a variety of new sources. Use our tips to get the most out of your blog.

If you don't think a blog would work for your site or business, consider publishing other forms of evergreen content such as guides or whitepapers.

Consider starting a blog

Mobile

Mobile visits

Upgrade to see the number of monthly visits from mobile users.

Mobile Friendliness

Very Good    Very Good

This web page is super optimized for Mobile Visitors

Mobile friendly pages make it easy for users to complete objectives and common tasks and use a design or template that is consistent across all devices (uses responsive web design).

Your site is well configured for mobile users.

Mobile Rendering

roastme.xyz on an iPhone
roastme.xyz on an iPad

80% of adult Internet users now have a smartphone. You should definitely be optimizing your website to render on the most popular mobile devices.

Touchscreen Readiness

Perfect, the most important buttons/links are large enough to be tapped easily.

Great, your User Interface allows for visitors to easily tap targets on their touchscreen. To go even further into improving your User Interface, use size and density buckets to accommodate varying device sizes and screen densities.

Mobile Compatibility

Perfect, no embedded objects detected.

Great, your website does not embed any special types of web content, such as Flash, Silverlight or Java, so your content can be accessed on all devices.

Font Size Legibility

Perfect, this web page’s text is legible on mobile devices.

You can find additional font recommendations for mobile devices in Google’s typography guidelines for Android.

Mobile Viewport

Great, a configured viewport is present.

The content does not fit within the specified viewport size.

The viewport is an element of a page’s responsive design. It’s the area of a webpage visible to the user and varies between devices.

It looks like your page could be missing a meta viewport.

Use the meta viewport tag in the <head> to set the viewport to the device’s screen size. It should look like this: <meta name="viewport" content="width=device-width, initial-scale=1.0">.

Mobile Speed

Slow    Slow

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Enable compression

Optimize images

Leverage browser caching

Prioritize visible content

Like with desktop, the time it takes a mobile page to load is an important part of mobile search engine results page ranks. Your mobile/responsive website must deliver and render the β€œabove the fold" content in under one second.

Unfortunately, the mobile page speed for roastme.xyz is Slow.

Since mobile device CPUs are less powerful than desktop CPUs, speed tips that reduce CPU consumption (for instance JavaScript Parse time) need to be addressed first.

See Google's PageSpeed Insights Rules for more information on how to improve each of the elements in this section.

Mobile Frameworks

No mobile frameworks have been detected.

Mobile or responsive frameworks are an important part of website optimization as they assist developers in creating applications which are applicable to multiple devices.

AMP

We didn't find AMP on your page.

AMP is an open-source library that provides a straightforward way to create web pages that are compelling, smooth, and load near instantaneously for users.

Check your AMP markup with the AMP validator.

Usability

URL

roastme.xyz

Length: 7 character(s)

Keep your URLs short and clean and avoid long domain names when possible.

A descriptive URL is better recognized by search engines. A user should be able to look at the address bar and make an accurate guess about the content of the page before reaching it (e.g., http://www.mysite.com/en/products).

Keep in mind that URLs are also an important part of a comprehensive SEO strategy. Use clean URLs to make your site more "crawlable" by Google.

Resource: Search for a good domain name. If no good names are available, consider a second hand domain. To prevent brand theft, you might consider trademarking your domain name.

Favicon

Great, your website has a favicon.

Favicons are the small icons that appear next to your site’s name or URL in a browser. They can be displayed in the address bar, a browser tab title or bookmarks. Make sure it is consistent with your brand.

Here is a way one company used a special favicon to improve user experience.

Add a Favicon

Custom 404 Page

Your website does not have a custom 404 Error Page.

Your server responded with the HTTP status code: 404

404 error pages are displayed when the page you are trying to open can't be found on the site's server for a variety of reasons.

It looks like roastme.xyz doesn't have a 404 error page. This damages your site's usability. Generic 404 error pages strand users on a page with no links or suggestions of what to do next.

Use a custom 404 page to reduce customer frustration and link to other pages on your site. Make sure it returns the 404 http status code.

Customize the 404 error page

Asset Minification

64%    64%

You could reduce 36% (21.4 KiB) by minifying the asset(s) listed below.

URL Reduction size
/css/app.css 16.7 KiB (35%)
/js/custom.js 3.3 KiB (40%)
/css/googleFonts.css 1.4 KiB (35%)
Fast websites make happy visitors. Enabling minification on assets like HTML, JavaScript and CSS files will reduce their transfer size. Every time a page is requested from your website less bytes and lighter assets are sent over the network resulting in faster delivery which loads your website faster for your customers.

To learn more on how to enable minification for your assets you can check out these 10 tips to improve page load time or consult Google's PageSpeed Insights guide on minification.

Asset Compression

24%    24%

You could reduce 76% (504.0 KiB) by compressing the asset(s) listed below.

URL Reduction size
/css/styles-merged.min.css 200.2 KiB (85%)
/js/scripts.min.js 170.9 KiB (70%)
/js/jquery-1.12.4.min.js 61.9 KiB (65%)
/css/app.css 39.0 KiB (82%)
/js/cookieconsent.min.js 13.6 KiB (67%)
/js/custom.js 5.8 KiB (70%)
/js/main.min.js 3.6 KiB (68%)
/css/googleFonts.css 3.5 KiB (87%)
/js/jquery.vticker.min.js 2.8 KiB (64%)
/css/cookieconsent.min.css 2.8 KiB (70%)
and 7 more.
Fast websites make happy visitors. It is very important to lower the load time of your web pages as much as possible for a better user experience. Compressing assets like images, javascript and CSS files will save bandwidth which results in a better page load time.

To learn more on how to enable compression for your assets you can check out these 10 tips to improve page load time or consult Google's PageSpeed Insights guide on compression.

Asset Cacheability

We found a total of 1 uncached asset(s) listed below.

URL Freshness lifetime
/fonts/icomoon/icomoon.ttf?1z9v6x a few seconds
Fast websites make happy visitors. Caching assets such as images, javascript and CSS files allows a browser to keep these files in local storage so it doesn't have to download them every time it requests a page on your website. This will lower the bandwidth used and improve the page load time.

To learn more on how to enable caching for your assets you can check out these 10 tips to improve page load time or consult Google's PageSpeed Insights guide on browser caching.

Language

Declared: English

Detected: English

Great, your declared language matches the language detected on the page.

Make sure your declared language is the same as the language detected by Google.

Tips for multilingual websites:

  • Define the language of the content in each page's HTML code.
  • Specify the language code in the URL as well (e.g., "mywebsite.com/fr/mycontent.html").
  • Use hreflang tags to specify language and country for Google, and the "content-language" meta tag to specify the language and country for Bing.

Declare the language used

Structured Data Markup

No Structured Data Markup has been detected

Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them to understand your content and create well-presented search results.

Get the most out of Google's rich snippets for content types such as: Reviews, People, Products, Businesses and Organizations, Recipes, Events, Videos and Music. If your website covers one of these topics, then we suggest that you annotate it with Schema.org using microdata.

Domain Availability

Domains Status
roastme.com Expires in 3 years
roastme.net Available. Register it now!
roastme.org Available. Register it now!
roastme.info Available. Register it now!
roastme.biz Available. Register it now!
roastme.eu This domain is booked

Register the various extensions of your domain to protect your brand from cybersquatters.

Typo Availability

Domains Status
roasyme.xyz Available. Register it now!
5oastme.xyz Available. Register it now!
roaetme.xyz Available. Register it now!
roastke.xyz Available. Register it now!
r9astme.xyz Available. Register it now!
r0astme.xyz Available. Register it now!
rozstme.xyz Available. Register it now!
and 1 more.

Register the various typos of your domain to protect your brand from cybersquatters.

Email Privacy

Warning! At least one email address has been found in plain text.

We don’t recommend adding plain text/linked email addresses to your webpages, as malicious bots scrape the web in search of email addresses to spam. Instead, consider using a contact form.

Hide email addresses to avoid being spammed

Technologies

Server IP

217.160.0.242

Server location: Berlin

Your server's IP address has little impact on your SEO. Nevertheless, try to host your website on a server which is geographically close to your visitors. Search engines take the geolocation of a server into account as well as the server speed.

Use DNSstuff for comprehensive reports on your server.

Technologies

Apache Web server
Google Tag Manager Tag Manager
jQuery JavaScript framework
PHP Programming language
Stripe Payment Processors

Get to know the technologies used for your website. Some codes might slow down your website. Ask your webmaster to take a look at this.

Speed Tips

Warning: your website’s speed could be slightly improved.

Perfect, your website doesn't use nested tables.

Too bad, your website is using inline styles.

Too bad, your website has too many CSS files (more than 4).

Perfect, your website has few JavaScript files.

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 your pages higher in the SERPs.

Conversion rates are far higher for websites that load faster than their slower competitors.

See Google's PageSpeed Insights Rules for more information on how to improve each of the elements in this section.

Analytics

Google Analytics

Web analytics let you measure visitor activity on your website. You should have at least one analytics tool installed, but It can also be good to install a second in order to cross-check the data.

Popular Analytics Tools Include: Google Analytics, Quantcastβ„’, AdobeAnalyticsβ„’, Piwikβ„’, chartbeatβ„’, Clickyβ„’, ClickTaleβ„’, etc.

Doctype

HTML5

The Doctype is used to instruct web browsers about the document type being used. For example, what version of HTML the page is written in.

Declaring a doctype helps web browsers to render content correctly.

Encoding

Great, language/character encoding is specified: utf8

Specifying language/character encoding can prevent problems with the rendering of special characters.

SSL Secure

Great, your website is SSL secured (HTTPS).

Your website's URLs redirect to HTTPS pages.

Your headers are not properly set up to use HSTS.

The SSL certificate expires in a year.

The certificate issuer is DigiCert Inc.

Modern websites tend to be SSL secured (HTTPS) as it provides an extra security layer while logging in to your Web Service. In 2014, Google announced that an HTTPS (vs HTTP) website would receive an extra boost in their ranking.

While switching to HTTPS, make sure your site remains optimized and see to it that your website will still run quickly. Follow these best practices for a smooth transition:
  • Use a serious issuer to purchase your SSL certificate
  • Redirect all of your HTTP pages to the HTTPS version of your website
  • Use HTTP Strict Transport Security (HSTS) in your headers
  • Renew your SSL certificate every year, before it expires
  • Make sure that all of your content (CSS, etc.) is linked to HTTPS
  • Update your XML sitemap to ensure the URLs include HTTPS and update the robots.txt file to reference this version
  • Register the HTTPS website in Google & Bing Search Console/Webmaster Tools
Promote

Social

Social Media Engagement

Your homepage has not been widely shared on social networks.

Facebook Shares0

Facebook Comments0

Facebook Likes0

Pinterest Shares0

The impact of social media is huge for certain industries, take advantage of this digital version of word-of-mouth marketing. However, it looks like roastme.xyz has not been widely shared on social media.

Create‬‬ social media profiles associated with roastme.xyz on Facebook, Pinterest, LinkedIn, Google+ and other sites that are of interest to your customers.

Learn how to engage your social media audiences and create a consistent fan base. You can also use your website to increase your popularity on social platforms.

Check these helpful tools for managing your social media campaign.

Note: This data is based on engagements from like and share buttons on your site, or people copying and pasting your URLs directly into Facebook. It does not include people who like or share your branded social media pages.

Facebook Views

Upgrade to connect your Facebook Page and get in-depth insights about:
  • Views
  • Activity
  • Demographics and more!

Facebook Page

Not found

Add your Facebook Page or create one

We were unable to find a Facebook page for roastme.xyz.

Facebook is a vital channel for any business' digital marketing. 72% of consumers and almost every Millennial expects your to have a presence on Facebook.

Use Facebook Insights to measure and track your audience's engagement with your posts to get the most out of your social media efforts. Link your Facebook profile with roastme.xyz and add a CTA to really maximize your social media marketing efforts.

Twitter Account

@jp_aulet

The Twitterβ„’ Account @jp_aulet is booked but it is not linked to your website!
Tip: Include your URL in your Twitter profile's website field.

Name
Followers
1,293
Tweets
3,370
Bio
FullStack Web & App Developer specialist - Future nomad and maker πŸŒπŸš€
Location
Barcelona, Spain
Created
8 years ago

Add your Twitter account or create one

We found a Twitter profile for your brand, but it's not linked to roastme.xyz. Linking your Twitter account to your website helps prevent brandjacking and can help make your social media marketing more effective. Use Twitter Dashboard and Analytics to track and optimize your Twitter feed.
Book your brand on Twitter

Google+ Page

This is the Google+ page for roastme.xyz. Being active in this social network is important for claiming your brand, influencing your search engine rankings and interacting with your network. You might also consider managing your profile with Google My Business (formerly Google Places).

Crunchbase Entry

Not found

Crunchbase is a platform used by millions, offering public information about businesses and individuals. While roastme.xyz does not appear to be listed on crunchbase.com, you can add it by creating a profile at crunchbase.com.

Visitors

Traffic Estimations

Very Low    Very Low

This shows your estimated traffic for roastme.xyz compared to any competitors you have chosen. We use Alexa for this information.

Sessions

Upgrade to sync your Google Analytics account and find significant metrics like:
  • Traffic Source
  • Source Domains
  • Pageviews and more!

Traffic Rank

8,012,350th most visited website in the World

A low rank means that your website gets a lot of visitors.

Your Alexa Rank is a good estimate of the worldwide traffic to roastme.xyz, although it is not 100 percent accurate.

Reviewing the most visited websites by country can give you valuable insights.

SEMRush provides similar services.

JavaScript Timeline

This graph gives a quick view of when the JavaScript interactions with the DOM occur during the loading of the page.

Timestamp: 0 ms
Timestamp: 21 ms
Timestamp: 43 ms
Timestamp: 64 ms
Timestamp: 85 ms
Timestamp: 106 ms
Timestamp: 128 ms
Timestamp: 149 ms
Timestamp: 170 ms
Timestamp: 191 ms
Timestamp: 213 ms
Timestamp: 234 ms
Timestamp: 255 ms
Timestamp: 277 ms
Timestamp: 298 ms
Timestamp: 319 ms
Timestamp: 340 ms
Timestamp: 362 ms
Timestamp: 383 ms
Timestamp: 404 ms
Timestamp: 425 ms
Timestamp: 447 ms
Timestamp: 468 ms
Timestamp: 489 ms
Timestamp: 511 ms
Timestamp: 532 ms
Timestamp: 553 ms
Timestamp: 574 ms
Timestamp: 596 ms
Timestamp: 617 ms
Timestamp: 638 ms
Timestamp: 659 ms
Timestamp: 681 ms
Timestamp: 702 ms
Timestamp: 723 ms
Timestamp: 744 ms
Timestamp: 766 ms
Timestamp: 787 ms
Timestamp: 808 ms
Timestamp: 830 ms
Timestamp: 851 ms
Timestamp: 872 ms
Timestamp: 893 ms
Timestamp: 915 ms
Timestamp: 936 ms
Timestamp: 957 ms
Timestamp: 978 ms
Timestamp: 1,000 ms
Timestamp: 1,021 ms
Timestamp: 1,042 ms
Timestamp: 1,064 ms
Timestamp: 1,085 ms
Timestamp: 1,106 ms
Timestamp: 1,127 ms
Timestamp: 1,149 ms
Timestamp: 1,170 ms
Timestamp: 1,191 ms
Timestamp: 1,212 ms
Timestamp: 1,234 ms
Timestamp: 1,255 ms
Timestamp: 1,276 ms
Timestamp: 1,298 ms
Timestamp: 1,319 ms
Timestamp: 1,340 ms
Timestamp: 1,361 ms
Timestamp: 1,383 ms
Timestamp: 1,404 ms
Timestamp: 1,425 ms
Timestamp: 1,446 ms
Timestamp: 1,468 ms
Timestamp: 1,489 ms
Timestamp: 1,510 ms
Timestamp: 1,532 ms
Timestamp: 1,553 ms
Timestamp: 1,574 ms
Timestamp: 1,595 ms
Timestamp: 1,617 ms
Timestamp: 1,638 ms
Timestamp: 1,659 ms
Timestamp: 1,680 ms
Timestamp: 1,702 ms
Timestamp: 1,723 ms
Timestamp: 1,744 ms
Timestamp: 1,766 ms
Timestamp: 1,787 ms
Timestamp: 1,808 ms
Timestamp: 1,829 ms
Timestamp: 1,851 ms
Timestamp: 1,872 ms
Timestamp: 1,893 ms
Timestamp: 1,914 ms
Timestamp: 1,936 ms
Timestamp: 1,957 ms
Timestamp: 1,978 ms
Timestamp: 2,000 ms
Timestamp: 2,021 ms
Timestamp: 2,042 ms
Timestamp: 2,063 ms
Timestamp: 2,085 ms
Timestamp: 2,106 ms
Timestamp: 2,127 ms
Timestamp: 2,148 ms
Timestamp: 2,170 ms
Timestamp: 2,191 ms
Timestamp: 2,212 ms
Timestamp: 2,233 ms
Timestamp: 2,255 ms
Timestamp: 2,276 ms
Timestamp: 2,297 ms
Timestamp: 2,319 ms
Timestamp: 2,340 ms
Timestamp: 2,361 ms
Timestamp: 2,382 ms
Timestamp: 2,404 ms
Timestamp: 2,425 ms
Timestamp: 2,446 ms
Timestamp: 2,467 ms
Timestamp: 2,489 ms
Timestamp: 2,510 ms
Timestamp: 2,531 ms
Timestamp: 2,553 ms
Timestamp: 2,574 ms
Timestamp: 2,595 ms
Timestamp: 2,616 ms
Timestamp: 2,638 ms
Timestamp: 2,659 ms
Timestamp: 2,680 ms
Timestamp: 2,701 ms
Timestamp: 2,723 ms
Timestamp: 2,744 ms
Timestamp: 2,765 ms
Timestamp: 2,787 ms
Timestamp: 2,808 ms
Timestamp: 2,829 ms
Timestamp: 2,850 ms
Timestamp: 2,872 ms
Timestamp: 2,893 ms
Timestamp: 2,914 ms
Timestamp: 2,935 ms
Timestamp: 2,957 ms
Timestamp: 2,978 ms
Timestamp: 2,999 ms
Timestamp: 3,021 ms
Timestamp: 3,042 ms
Timestamp: 3,063 ms
Timestamp: 3,084 ms
Timestamp: 3,106 ms
Timestamp: 3,127 ms
Timestamp: 3,148 ms
Timestamp: 3,169 ms
Timestamp: 3,191 ms
Timestamp: 3,212 ms
Timestamp: 3,233 ms
Timestamp: 3,255 ms
Timestamp: 3,276 ms
Timestamp: 3,297 ms
Timestamp: 3,318 ms
Timestamp: 3,340 ms
Timestamp: 3,361 ms
Timestamp: 3,382 ms
Timestamp: 3,403 ms
Timestamp: 3,425 ms
Timestamp: 3,446 ms
Timestamp: 3,467 ms
Timestamp: 3,489 ms
Timestamp: 3,510 ms
Timestamp: 3,531 ms
Timestamp: 3,552 ms
Timestamp: 3,574 ms
Timestamp: 3,595 ms
Timestamp: 3,616 ms
Timestamp: 3,637 ms
Timestamp: 3,659 ms
Timestamp: 3,680 ms
Timestamp: 3,701 ms
Timestamp: 3,722 ms
Timestamp: 3,744 ms
Timestamp: 3,765 ms
Timestamp: 3,786 ms
Timestamp: 3,808 ms
Timestamp: 3,829 ms
Timestamp: 3,850 ms
Timestamp: 3,871 ms
Timestamp: 3,893 ms
Timestamp: 3,914 ms
Timestamp: 3,935 ms
Timestamp: 3,956 ms
Timestamp: 3,978 ms
Timestamp: 3,999 ms
Timestamp: 4,020 ms
Timestamp: 4,042 ms
Timestamp: 4,063 ms
Timestamp: 4,084 ms
Timestamp: 4,105 ms
Timestamp: 4,127 ms
Timestamp: 4,148 ms
Timestamp: 4,169 ms
Timestamp: 4,190 ms
Timestamp: 4,212 ms
Timestamp: 4,233 ms
0 ms
4,233 ms
DOM creation
DOM interactive
DOM content loaded event
Page completion
Page is complete
Executing JavaScript and DOM queries here is a bad practice and slows down the DOM construction.
Some frameworks do things here, but it's not reliable and should be avoided.
Also known as "document ready". This is where you should execute top-priority scripts, like binding action buttons or launch a video player.
Here you can execute mid-priority tasks. Loading a script with createElement('script') is one way to do so.
The page is considered loaded, it's time for low priority things : trackers, social plugins, easter egg...

JavaScript Profiler

The table below shows the interactions between the JavaScript and the DOM. It is useful to understand what happens while the page loads.

Type
Params
Timestamp
1
createElement
div
βœ–

Backtrace

(anonymous function)
2:22515
(anonymous function)
2:22970
(anonymous function)
2:208
189 ms
2
createElement
div
βœ–

Backtrace

(anonymous function)
2:22515
(anonymous function)
2:22970
(anonymous function)
2:208
189 ms
3
appendChild
append
Created element #comment
to
Created element div
βœ–

Backtrace

(anonymous function)
2:22515
(anonymous function)
2:22970
(anonymous function)
2:208
189 ms
4
getElementsByTagName
* on
Created element div
βœ–

The query returned 0 results. Could it be unused or dead code?

Backtrace

(anonymous function)
2:22515
(anonymous function)
2:22970
(anonymous function)
2:208
190 ms
5
createElement
div
βœ–

Backtrace

(anonymous function)
2:22515
(anonymous function)
2:22970
(anonymous function)
2:208
190 ms
6
appendChild
append
Created element div
to
html
βœ–

Backtrace

(anonymous function)
2:22515
(anonymous function)
2:22970
(anonymous function)
2:208
190 ms
7
createElement
div
βœ–

Backtrace

(anonymous function)
2:22515
(anonymous function)
2:22970
(anonymous function)
2:208
191 ms
8
createElement
div
βœ–

Backtrace

(anonymous function)
2:22970
(anonymous function)
2:208
191 ms
9
createElement
div
βœ–

Backtrace

(anonymous function)
2:22535
(anonymous function)
2:22970
(anonymous function)
2:208
191 ms
10
createElement
div
βœ–

Backtrace

(anonymous function)
2:22970
(anonymous function)
2:208
191 ms
11
createElement
div
βœ–

Backtrace

(anonymous function)
2:22970
(anonymous function)
2:208
191 ms
12
createElement
div
βœ–

Backtrace

(anonymous function)
2:22970
(anonymous function)
2:208
191 ms
13
addEventListener
bind DOMContentLoaded to
document
βœ–

Backtrace

197 ms
14
addEventListener
bind load to
window
βœ–

Backtrace

197 ms
15
createElement
div
βœ–

Backtrace

197 ms
16
createElement
div
βœ–

Backtrace

197 ms
17
createDocumentFragment
βœ–

Backtrace

197 ms
18
createElement
input
βœ–

Backtrace

197 ms
19
getElementsByTagName
tbody on
Created element div
βœ–

The query returned 0 results. Could it be unused or dead code?

Backtrace

198 ms
20
getElementsByTagName
link on
Created element div
βœ–

The query returned 1 result.

Backtrace

201 ms
21
createElement
nav
βœ–

Backtrace

201 ms
22
appendChild
append
Created element input
to
fragment
βœ–

Backtrace

201 ms
23
appendChild
append
Created element div
to
fragment
βœ–

Backtrace

201 ms
24
createElement
input
βœ–

Backtrace

201 ms
25
appendChild
append
Created element input
to
Fragment element div[1]
DocumentFragment
div[1]
βœ–

Backtrace

201 ms
26
createElement
div
βœ–

Backtrace

201 ms
27
createDocumentFragment
βœ–

Backtrace

202 ms
28
createElement
div
βœ–

Backtrace

202 ms
29
appendChild
append
Created element div
to
fragment
βœ–

Backtrace

202 ms
30
createElement
div
βœ–

Backtrace

202 ms
31
createElement
div
βœ–

Backtrace

202 ms
32
createElement
div
βœ–

Backtrace

202 ms
33
appendChild
append
Created element div
to
Created element div
βœ–

Backtrace

202 ms
34
createElement
div
βœ–

Backtrace

202 ms
35
createElement
input
βœ–

Backtrace

203 ms
36
createElement
div
βœ–

Backtrace

203 ms
37
createElement
select
βœ–

Backtrace

203 ms
38
createElement
option
βœ–

Backtrace

203 ms
39
appendChild
append
Created element option
to
Created element select
βœ–

Backtrace

203 ms
40
createElement
div
βœ–

Backtrace

203 ms
41
getElementsByTagName
a on
Created element div
βœ–

The query returned 1 result.

Backtrace

203 ms
42
appendChild
append
Created element input
to
Created element div
βœ–

Backtrace

208 ms
43
getElementsByTagName
a on
Created element div
βœ–

The query returned 1 result.

Backtrace

208 ms
44
createElement
form
βœ–

Backtrace

209 ms
45
createElement
input
βœ–

Backtrace

209 ms
46
jQuery loaded
version 1.12.4
211 ms
47
querySelectorAll
:root on
document
βœ–

The query returned 1 result.

261 ms
48
addEventListener
bind DOMContentLoaded to
document
βœ–

Backtrace

270 ms
49
addEventListener
bind readystatechange to
document
βœ–

Backtrace

270 ms
50
addEventListener
bind load to
window
βœ–

Backtrace

270 ms
51
addEventListener
bind load to
window
βœ–

Backtrace

271 ms
53
querySelector
script[nonce] on
document
βœ–

The query returned 0 results. Could it be unused or dead code?

Backtrace

304 ms
54
getElementsByTagName
script on
document
305 ms
55
insertBefore
insert
Created element script
into
head
before
head
305 ms
56
createElement
div
βœ–

Backtrace

413 ms
57
addEventListener
bind load to
window
βœ–
413 ms
58
createElement
a
βœ–

Backtrace

(anonymous function)
1:489
(anonymous function)
1:452
global code
1:460
422 ms
59
createElement
a
βœ–

Backtrace

(anonymous function)
1:104947
(anonymous function)
1:489
(anonymous function)
1:452
global code
1:460
425 ms
60
createElement
a
βœ–

Backtrace

(anonymous function)
1:105435
(anonymous function)
1:104947
(anonymous function)
1:489
(anonymous function)
1:452
global code
1:460
425 ms
61
createElement
a
βœ–

Backtrace

(anonymous function)
1:105435
(anonymous function)
1:104947
(anonymous function)
1:489
(anonymous function)
1:452
global code
1:460
425 ms
62
createElement
div
βœ–

Backtrace

(anonymous function)
1:35161
(anonymous function)
1:35606
(anonymous function)
1:210
434 ms
63
createElement
div
βœ–

Backtrace

(anonymous function)
1:35161
(anonymous function)
1:35606
(anonymous function)
1:210
434 ms
64
appendChild
append
Created element #comment
to
Created element div
βœ–

Backtrace

(anonymous function)
1:35161
(anonymous function)
1:35606
(anonymous function)
1:210
434 ms
65
getElementsByTagName
* on
Created element div
βœ–

The query returned 0 results. Could it be unused or dead code?

Backtrace

(anonymous function)
1:35161
(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
66
createElement
div
βœ–

Backtrace

(anonymous function)
1:35161
(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
67
appendChild
append
Created element div
to
html
βœ–

Backtrace

(anonymous function)
1:35161
(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
68
createElement
div
βœ–

Backtrace

(anonymous function)
1:35161
(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
69
createElement
div
βœ–

Backtrace

(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
70
createElement
div
βœ–

Backtrace

(anonymous function)
1:35180
(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
71
createElement
div
βœ–

Backtrace

(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
72
createElement
div
βœ–

Backtrace

(anonymous function)
1:35606
(anonymous function)
1:210
435 ms
73
createElement
div
βœ–

Backtrace

(anonymous function)
1:35606
(anonymous function)
1:210
436 ms
74
addEventListener
bind DOMContentLoaded to
document
βœ–

Backtrace

437 ms
75
addEventListener
bind load to
window
βœ–

Backtrace

437 ms
76
createElement
div
βœ–

Backtrace

437 ms
77
createElement
div
βœ–

Backtrace

437 ms
78
createDocumentFragment
βœ–

Backtrace

437 ms
79
createElement
input
βœ–

Backtrace

437 ms
80
getElementsByTagName
tbody on
Created element div
βœ–

The query returned 0 results. Could it be unused or dead code?

Backtrace

438 ms
81
getElementsByTagName
link on
Created element div
βœ–

The query returned 1 result.

Backtrace

438 ms
82
createElement
nav
βœ–

Backtrace

438 ms
83
appendChild
append
Created element input
to
fragment
βœ–

Backtrace

438 ms
84
appendChild
append
Created element div
to
fragment
βœ–

Backtrace

438 ms
85
createElement
input
βœ–

Backtrace

438 ms
86
appendChild
append
Created element input
to
Fragment element div[1]
DocumentFragment
div[1]
βœ–

Backtrace

438 ms
87
createElement
div
βœ–

Backtrace

438 ms
88
createDocumentFragment
βœ–

Backtrace

439 ms
89
createElement
div
βœ–

Backtrace

439 ms
90
appendChild
append
Created element div
to
fragment
βœ–

Backtrace

439 ms
91
createElement
div
βœ–

Backtrace

439 ms
92
createElement
div
βœ–

Backtrace

439 ms
93
createElement
div
βœ–

Backtrace

439 ms
94
appendChild
append
Created element div
to
Created element div
βœ–

Backtrace

439 ms
95
createElement
div
βœ–

Backtrace

439 ms
96
createElement
input
βœ–

Backtrace

439 ms
97
createElement
div
βœ–

Backtrace

439 ms
98
createElement
select
βœ–

Backtrace

439 ms
99
createElement
option
βœ–

Backtrace

439 ms
100
appendChild
append
Created element option
to
Created element select
βœ–

Backtrace

439 ms
101
createElement
div
βœ–

Backtrace

439 ms
102
getElementsByTagName
a on
Created element div
βœ–

The query returned 1 result.

Backtrace

440 ms
103
appendChild
append
Created element input
to
Created element div
βœ–

Backtrace

440 ms
104
getElementsByTagName
a on
Created element div
βœ–

The query returned 1 result.

Backtrace

440 ms
105
createElement
form
βœ–

Backtrace

440 ms
106
createElement
input
βœ–

Backtrace

440 ms
107
jQuery version change
version 1.12.4
441 ms
108
jQuery - find
jQuery - Sizzle call
script on
document
getElementsByTagName
script on
document
script
βœ–

The query returned 8 results.

Backtrace

(anonymous function)
1:203065
(anonymous function)
1:102417
445 ms
109
createElement
div
βœ–

Backtrace

447 ms
110
jQuery - attr
set style : background:#fff on
Created element div
βœ–

Backtrace

(anonymous function)
1:102436
447 ms
111
jQuery - css
getComputedStyle
Created element div
appendChild
append
Created element div
to
html
getComputedStyle
html
createElement
div
appendChild
append
Created element div
to
html
getComputedStyle
html
getElementsByTagName
td on
html
get background-position-x from
Created element div
βœ–
447 ms
112
jQuery - blur
jQuery - on
bind blur on
window
's children filtered by null
addEventListener
bind blur to
window
bind on
window
βœ–
450 ms
113
jQuery - focus
jQuery - on
bind focus on
window
's children filtered by null
addEventListener
bind focus to
window
bind on
window
βœ–
451 ms
114
createElement
p
βœ–

Backtrace

452 ms
115
jQuery - onDOMReady
(function)
βœ–

Backtrace

454 ms
116
jQuery - on
addEventListener
bind click to
document
bind click.bs.alert.data-api on
document
's children filtered by [data-dismiss="alert"]
βœ–
454 ms
117
jQuery - on
bind click.bs.button.data-api on
document
's children filtered by [data-toggle^="button"]
βœ–
455 ms
118
jQuery - on
addEventListener
bind blur to
document
addEventListener
bind focus to
document
bind focus.bs.button.data-api blur.bs.button.data-api on
document
's children filtered by [data-toggle^="button"]
βœ–
455 ms
119
jQuery - on
bind click.bs.carousel.data-api on
document
's children filtered by [data-slide]
βœ–
455 ms
120
jQuery - on
bind click.bs.carousel.data-api on
document
's children filtered by [data-slide-to]
βœ–
455 ms
121
jQuery - on
addEventListener
bind load to
window
bind load on
window
βœ–
456 ms
122
jQuery - on
bind click.bs.collapse.data-api on
document
's children filtered by [data-toggle="collapse"]
βœ–
456 ms
123
jQuery - on
bind click.bs.dropdown.data-api on
document
βœ–
456 ms
124
jQuery - on
bind click.bs.dropdown.data-api on
document
's children filtered by .dropdown form
βœ–
456 ms
125
jQuery - on
bind click.bs.dropdown.data-api on
document
's children filtered by [data-toggle="dropdown"]
βœ–
456 ms
126
jQuery - on
addEventListener
bind keydown to
document
bind keydown.bs.dropdown.data-api on
document
's children filtered by [data-toggle="dropdown"]
βœ–
457 ms
127
jQuery - on
bind keydown.bs.dropdown.data-api on
document
's children filtered by .dropdown-menu
βœ–
457 ms
128
jQuery - on
bind click.bs.modal.data-api on
document
's children filtered by [data-toggle="modal"]
βœ–
457 ms
129
jQuery - on
bind load.bs.scrollspy.data-api on
window
βœ–
457 ms
130
jQuery - on
bind click.bs.tab.data-api on
document
's children filtered by [data-toggle="tab"]
βœ–
457 ms
131
jQuery - on
bind click.bs.tab.data-api on
document
's children filtered by [data-toggle="pill"]
βœ–
457 ms
132
jQuery - on
bind load on
window
βœ–
458 ms
133
jQuery - onDOMReady
(function)
βœ–

Backtrace

472 ms
134
jQuery - load
jQuery - on
bind load on
window
's children filtered by null
bind on
window
βœ–
472 ms
135
jQuery - onDOMReady
(function)
βœ–
472 ms
136
domInteractive
474 ms
137
domContentLoaded
474 ms
138
getElementsByTagName
body on
document
βœ–

The query returned 1 result.

Backtrace

474 ms
139
createElement
div
475 ms
140
createElement
div
475 ms
141
appendChild
append
Created element div
to
body
475 ms
142
appendChild
append
Created element div
to
DOM element div[10]
body
div[10]
475 ms
143
jQuery - off
unbind ready from
document
βœ–
476 ms
144
getElementsByTagName
body on
document
βœ–

The query returned 1 result.

Backtrace

476 ms
145
createElement
div
477 ms
146
createElement
div
477 ms
147
appendChild
append
Created element div
to
body
477 ms
148
appendChild
append
Created element div
to
DOM element div[10]
body
div[10]
477 ms
149
createElement
bootstrap
478 ms
150
jQuery - find
jQuery - Sizzle call
.probootstrap-navbar .navbar-nav li.dropdown on
document
getElementsByTagName
li on
document
.probootstrap-navbar .navbar-nav li.dropdown
βœ–

The query returned 0 results. Could it be unused or dead code?

Backtrace

478 ms
151
jQuery - hover
jQuery - mouseenter
bind on Empty jQuery object
jQuery - on
bind mouseenter on Empty jQuery object's children filtered by null
jQuery - mouseleave
bind on Empty jQuery object
jQuery - on
bind mouseleave on Empty jQuery object's children filtered by null
bind on Empty jQuery object
βœ–

Called on 0 jQuery element

Useless function call, as the jQuery object is empty.

Backtrace

480 ms
152
jQuery - find
getElementById
#probootstrap-counter
#probootstrap-counter
βœ–

The query returned 0 results. Could it be unused or dead code?

Backtrace

480 ms
153
jQuery - find
jQuery - Sizzle call
.probootstrap-animate on
document
getElementsByTagName
* on
document
.probootstrap-animate
480 ms
154
jQuery - scrollLeft
get from
window
482 ms
156
jQuery - on
addEventListener
bind scroll to
window
bind scroll.waypoints on
window
483 ms
157
jQuery - on
addEventListener
bind resize to
window
bind resize.waypoints on
window
483 ms
158
jQuery - scrollLeft
get from
window