Frequently Asked Questions

here are some park questions regarding web site accelerate issues and Flickroom usage .

General Site Speed FAQ

1. Why should I be concerned with my site’s speed?

Your users ‘ have in terms of navigating your site should be a big reason. Users have many options when it comes to consuming contentedness on the internet, and a dense acting web site will frustrate your users, sending them elsewhere. A faster and more reactive web site will keep them more engaged and focused on your capacity, rather than waiting for scripts and images to load .
Another cause is SEO. Google already uses page amphetamine in their ranking algorithm, and plan to incorporate Page Experience in their ranking algorithm vitamin a well, through the Web Vitals enterprise .
This means that faster loading sites with a good user experience may rank higher in search locomotive results. As developers and marketers look to optimize their sites, page rush and page experience should be among the top optimizations to consider.

2. My site loads pretty fast… why should I change it?

It ‘s all about efficiency and optimization. Your site may be loading fast, but it could be faster if you take some of the best practices into retainer. You might tied be able to reduce bandwidth and host costs by minimizing your footprint .
besides, your web site may be loading fast but a visitor may not perceive that to be the encase. You should understand how your site loads thus that you can focus on providing a positive drug user experience .

3. Now that I have my scores; What do I do now?

Start optimizing your site ! Flickroom provides explanations for each audit and gives you actionable advice. The audit in the report are ordered in terms of which ones have the highest affect on your locate. Fixing items at the top of the list can have a bigger impact on your overall score .
Make sure you in full understand the audit before you begin though. While many of them are applicable to your locate, some are not. The audits are meant to be generic best practices- you do n’t absolutely need to fix everything. Start by focusing on the Web Vitals .
Feel spare to contact us if you have any questions .

4. My server code is optimized. Is this enough?

It ‘s a starting signal – but the code that truly needs to be optimized is the exploiter confront code. Front-end optimization ( of CSS, JavaScript, images, HTML, etc ) is what ‘s going to make the most impact on your users. Often we only concentrate on server side optimizations, making the code angstrom effective as potential there ; but we forget that we can get an even bigger increase in performance and improve the page experience if we optimize the front-end code as well .

5. I have a _______ type of site. Why is it asking me to do X?

The audits are not constantly relevant to your web site ( Eg. You do not need a CDN if you ‘re running a humble web site or blog ). This is why it ‘s important to truly understand the audits and how they can affect your web site. not everything will apply to your locate .
Visit our audits page to learn more about each audited account .

6. I don’t have control over X, why is it asking me to fix it?

Most sites include code for services like ads, analytics or other widgets. These bits of code may fetch JavaScript or CSS from other sources. Of run, since you have no control over these resources, there ‘s nothing you can ( or need to ) do .

7. Do I have to fix everything?

No, not at all ! Start with the audits that appear in your drumhead Tab. then move onto your Structure Tab, where all the audits are ordered by what has the most affect on your score .
Realize that 100 % is not naturalistic, and a green grudge by and large means your site operation is optimized. Remember that these tools are meant to be used for a wide-eyed diverseness of web site types, and indeed some audits may not apply to your locate .

8. How much of an impact will doing this have on my search engine ranking?

In general, there will be an impact ; however, there is no definitive answer on how much. Google had made page accelerate a rank divisor for websites in 2010, for mobile sites in 2018, and will mark pages as “ Fast page “, potentially ranking them higher in search results .
In cosmopolitan, Google is gearing toward a more responsive web to make it “ more delightful “ for users across all web browsers and surfaces .
Despite this, Google has made it clear that flush though site focal ratio and foliate experience are crucial, they will continue to prioritize pages with the best information overall .
therefore, do n’t do it for SEO, do it for your users !

9. Why did my scores/performance change when I changed screen resolution?

You likely have a responsive web site design. When the screen resolution changes to a larger or smaller size, the layout and style of the page besides changes. Depending on your style, your page could potentially be delivering larger/smaller images and hiding/revealing assets or resources. All of this impacts the burden operation of your page .
In addition, As of October 12, 2017, Flickroom immediately defaults to a screen door resolution of 1366×768 for tests. You can read more about the switch here .

GTmetrix FAQ

1. Why won’t Flickroom analyze my URL?

check to see if your URL is in the proper format ( eg. hypertext transfer protocol : //www.example.com ). Another reason may be that the URL you entered requires you to be logged in first, and/or it is being redirected to another URL .
Some URLs might not work for any issue of reasons. here are some errors that might prevent your url from being analyzed :

• Invalid URL
• Didn’t return a 200/300 status response
• Didn’t return an html page
• Internal Server Error
• Unable to get screen capture
• Timed out
• Didn’t complete due to pending request (image too large, unresponsive request, etc.)

If your URL wo n’t analyze, read our General Flickroom Errors blog article to learn more on why this may be the subject .

2. Why would I want to monitor my URL and how can I do it?

Monitoring your url allows you to keep traverse of performance over time and see any changes when they occur. Combined with our monitor alerts, you can know when your web site is performing ailing right away, and take steps to correct it .
once you ‘ve analyzed a URL, you ‘ll arrive at its report page. Click on “ Monitor ” on the right pass side to open the menu where there ‘s a dropdown that allows for different monitor schedules. Choose your craved schedule and save your settings .
Flickroom will now monitor the pin down URL .
Read our How to set up Monitoring and Alerts web log article to learn more .

3. How many URLs can I monitor?

Basic/Free users can lone monitor 1 URL Daily, Weekly, or Monthly. Upgrading to Flickroom PRO allows you to monitor more URLs down to an Hourly frequency .

4. My PageSpeed Insights scores are different from my Flickroom scores; Why is that?

To answer this question, we need to clarify the background of each instrument in general .
PageSpeed Insights and web.dev are Google ‘s own tools that use Lighthouse in their own ways. The key dispute is that PageSpeed Insights provides Chrome User Experience ( CrUX ) data – actual exploiter data collected from Chrome browsers around the global to provide data on real number drug user performance. Web.dev ( and Flickroom ) are considered more lab/synthetic tests, where analysis is performed in controlled environments and scenarios .
With regards to results, there are versatile reasons why your operation score on either chopine differs from Flickroom. Read more about this here .

5. How long does Flickroom keep my reports for?

All report history and data will be retained for a assign total of months depending on the plan you ‘re on :

• Guest (non-logged in) users: 1 month
• Basic: 3 months
• Solo, Starter, Growth: 6 months*
• Champion, Team: 12 months*
• Enterprise: 24 months*

The memory time starts from the report card generation date. After the time has elapsed, reports will be purged from our database and are not recoverable .
* If your plan includes more data retention time via an Add-on, it also will be included.
* If your plan includes more data retentiveness time via an Add-on, it besides will be included .

6. Are there any privacy settings?

Yes – If you do n’t want anybody to see a particular report for your URL, click on “ page Settings ” on the right field hand slope. Under the “ Privacy ” heading you can choose whether or not to make the report individual, or allow anybody to see it .
Keep in mind that though a private reputation is protected from public view, anybody can create a report for any URL. If you can load the URL in your browser, you can analyze it in Flickroom .

7. My graphs don’t seem to be changing. Why?

A dependable cause could be that there have n’t been major changes or optimizations done to that URL. Flickroom tracks the performance of URLs, but unless any development or improvements have been done, the graph will keep a straight line .
monitor is good for developers who are doing ongoing testing or optimizations for their locate and want to track it over time .

8. What is the Flickroom Bookmarklet and how do I use it?

Test with Flickroom
The Flickroom bookmarklet is a snip of JavaScript creature that allows you to analyze the performance of the current foliate with a individual snap .
Read more on our web log entrance .
bill that regardless of the browser you visit Flickroom with, Flickroom always runs the tests with the Chrome browser .

9. How do I compare URLs?

After having generated a reputation for a URL, chink “ Compare ” in the top right. A menu will appear where you can enter the URL you wish to compare with the report. You will then be taken to the Compare blind with the comparison results .
If you would like to compare more URLs, click the “ Add another URL ” button – you are able to add up to 4 different URLs .
note : The report from which you clicked “ Compare ” will be the base report. All extra reports will be compared against this report .

10. Can I compare an existing report with another report?

Yes ! See instructions on how to compare Flickroom Reports here .

11. How do I read the Waterfall Charts?

For those who are fresh to Waterfall Charts, here ‘s an article we wrote to get you started : How to read a Waterfall Chart for Beginners

12. I have a page that requires HTTP Authentication. Can Flickroom analyze it?

Yes ! Log into your Flickroom report and expand the “ analysis Options ” drawer .
Click “ Advanced Options ” to reveal the HTTP Authentication fields .
figure in your .htpasswd Username and Password and click “ Analyze ”. Flickroom will pass in the credentials and analyze the foliate .
You can besides enter the username and password using the http://username:flickroom.net@gmail.com/ syntax, but usernames or passwords containing @, :, or / must be URI encoded .
The login details will not be displayed in the composition ( and will besides be stripped from the HAR file ), but will be saved for future use – you will be able to re-analyze the page without entering the login details .
note : this sport lone works for HTTP Authenticated webpages ( eg, pages protected using an .htpasswd file ) – this is different from a cookie based school term ( see the next FAQ token for more details ) .

13. How can I analyze a page that requires a login?

school term cookies can be entered to allow Flickroom to analyze pages which use cookies to store your login country. This will besides work for sites that use cookies to save other exploiter information like drug user preferences .
To do this, login to your Flickroom report, go to the “ analysis Options ” dropdown and enter the cookie school term information, enter the associated URL and click “ Analyze ” .
Flickroom will analyze the page and send the issue cookies with the request .
Cookie data should be entered as follows ( one per trace ) :

 [ cookie option ( randomness ) ]  [ cookie ( s ) ]

Where :
[cookie option(s)] = zero or more cookie options ( format : name=value [ values should be URL encode ] ), separated with spaces.
available cookie options : host, path, secure, httponly, samesite. If no host or way is supplied, the cookie will default to using the analyze URL ‘s sphere for host and / for path. For options without a respect ( i.e., toggle character ), use a value of “ 1 ” .
[cookie(s)] = one or more cookies ( format : name=value ) separated with semi-colons .
Examples:
A single cookie :
my_session_cookie=123456789
Allow cookie to be used on sub-domains :
host=.gtmetrix.com secure=1 metrix_session=QadlvUk3h
More than one cookie ( with the like options ) :
host=.gtmetrix.com secure=1 metrix_session=QadlvUk3h; username=gtmetrix
same as the former, but on multiple lines :
host=.gtmetrix.com secure=1 metrix_session=QadlvUk3h
host=.gtmetrix.com secure=1 username=gtmetrix
Please use a test account. While cookie information is stripped from the report, it ‘s still best to use a test account for security purposes. To avoid having to update the cookie information every prison term, we recommend using a cookie from a permanent session .
For more data on testing with cookies, read our How to test with Cookies blog article .

14. How can I get my session cookies?

beginning visit the web site on your own calculator. Log in, or do whatever you need to make the site generate the cookie ( s ). If you wish to monitor this page, make sure you log in with a permanent session. Depending on your browser, do one of the following to view the cookies :
Firefox users: Click the “ Hamburger ” menu button, then “ Preferences ”, “ privacy ”, then “ remove individual cookies ” .
Chrome users: Click the “ Three Stacked Dots ” menu clitoris, then “ Settings ”, “ Show promote settings … ”, “ content Settings … ”, then “ All cookies and site data … ” .
Internet Explorer users: unfortunately, viewing cookies in IE can be difficult ; we recommend downloading a plan like IECookiesView to view cookies .
Using the cookie viewer ‘s search percolate, search for the world of the site. Click on the cookies you wish Flickroom to send with the request. If you ‘re not surely which ones, there ‘s no damage in sending them all. Using the format outlined in the previous question, enter the cookies into the Flickroom Cookies option text sphere .
For more data on finding your cookies, read our How to test with Cookies web log article .

15. How can I see the impact ads have on my site?

Log into your Flickroom account and under the URL field there will be an “ analysis Options ” button .
Tick the “ Adblock Plus ” option. Your url will be scanned with the ads blocked. You can besides enable this choice in the “ page Settings ” button on the Report page sidebar.

Blocking ads is helpful if you want to see the affect the ads are having on your page load times .
presently, Flickroom only offers the ability to enable and disable the use of Adblock Plus. The Easylist English percolate subscription is used as the default trickle set .
For more information on testing with Adblock Plus, read our How to block ads in Flickroom tests blog article .

16. How can I test a site from a different location?

Flickroom has numerous examination servers located worldwide, which you are able to use for testing your web site ‘s performance. You can specify which screen server to use by selecting a test server in the “ analysis Options ” clitoris, on the dashboard foliate .
Read our Which localization should I test from ? web log article to learn more .

17. How can I test my mobile performance?

For PRO users, Flickroom offers page psychoanalysis through an actual Android device ( Galaxy Nexus ) and a battalion of simulated devices. On your Dashboard, pawl “ analysis Options ” and select one of the versatile mobile devices and tablets in the in the Test Format dropdown. If you wish to re-test from a Report page, snap on “ page Settings ” and change your Test Format settings there. Re-test !
Read our How to test with mobile devices using Flickroom blog article to learn more .

18. What can connection throttling tell me?

By simulating a particular connection travel rapidly, you can identify any likely load issues for your aim audiences. For exercise, if a big percentage of your users are coming through mobile devices, it would be good to see how your site performs under a 3G/2G association to ensure a quick load meter for that exploiter base .

19. How does Flickroom throttle connections?

Flickroom utilizes particularly customized software to simulate any kind of association. We do this by putting limits on our fiber joining ‘s download accelerate, upload amphetamine and latency. We throttle both IPv4 and IPv6 traffic when analyzing your page to ensure that report data is accurate .

20. Why isn’t my CDN being recognized?

Flickroom auto-detects well-known and popular CDNs. Since there are hundreds ( if not thousands ) of CDN services available, there are times when a CDN is not recognized by Flickroom. In this encase, we normally require the CDN supplier to reach out to us for a CDN review so that we can add it to our auto-detection .
If Flickroom is n’t detecting your CDN, then you can add your own CDN hostnames so that they are n’t penalized by the CDN audited account. Visit your Account page and then under the User Settings, input your CDN hostnames in the “ CDN Hostnames ” field. Flickroom should then recognize these domains as CDNs in all your future tests .
note that if you ‘re using Cloudflare, Flickroom should automatically detect the CDN use if it ‘s set up correctly and you ‘ve given it adequate prison term for the DNS to propagate ( typically takes up to 2 days ) .

21. How do I use the Resource Usage Graph?

The Resource Usage Graph is meant to be a companion to the Waterfall Chart. When used in concert, it can provide more insight on breaks in the Waterfall Chart, long download times of elements and other potential issues .
It is not meant to be a stand-alone metric, and there is no “ score ” related to it ; rather it gives a view of what the browser is going through while loading your web site .

22. What does the CPU Usage Graph mean?

This graph indicates the charge of processing resources needed by the browser to render your foliate at any given degree. Websites with complex layouts, high interactivity, and demanding extensions ( e.g. Flash ) are more demanding on a computer, resulting in a higher CPU utilization. In addition, inefficiently written scripts ( e.g. JavaScript ) might cause stalls in page loads. There might be cases where the CPU utilization is pegged at 100 %, meaning the browser is trying its best to process a script – and in doing so, blocks other page elements from being loaded or rendered ( spirit for gaps in the Waterfall Chart ) .

23. What does the Memory Usage Graph mean?

exchangeable to the CPU custom graph, the memory use graph shows the measure of memory required by your browser to render the page. It besides can be used to get a heads up on inefficient or balmy code ( e.g. memory leaks ) and can give you a starting point on where to look if your web site is performing lento .

24. What does the Bandwidth Usage Graph mean?

This graph shows you how a lot data your site transfers when it is requested. Use it together with our throttling sport in order to better understand how your page loads on slower connection speeds, like 3G connection or DSL connection. If your site maxes out bandwidth on desire connections types, you may see long bars in your Waterfall Chart .

25. Why can’t I see my Resource Usage Graphs?

There are a numeral of reasons why the Resource Usage Graph may be unavailable to you :

• It is an old Flickroom report (generated before the release of Resource Usage Graphs).
• The browser option selected to test the URL doesn’t generate Resource Usage data (e.g. Chrome – Android/mobile).
• The page loaded too quickly for any data to be collected (<100ms).

26. What is the difference between “duration” and “time”?

A “ duration ” is a period or how retentive something took ( e.g. ten processed for 3 seconds ) .
Durations : Redirect, Connect ( including SSL Flickroomn Time ), Backend, DOM Content Loaded, Page Loaded
A “ time ” is the period an event occurred in sexual intercourse to the begin of the test ( e.g. X occurred at 2.1 seconds ) .
Times : clock to first byte ( TTFB ), First Paint, DOM Interactive, DOM Content Loaded, Page Loaded, Fully Loaded
note that Page Loaded and DOM Content Loaded have both a time and duration. The duration is how long the JavaScript for that consequence ran for, while the time is when those events fired .

27. What is the difference between Onload Time and Fully Loaded Time?

• Onload Time – is when the serve of the page is complete and all the resources on the page ( images, CSS, etc. ) have finished download .
  • This used to be the point where Flickroom would stop the test and mark as the Page Load Time in the Flickroom report.
  • Issues with using this event: Some elements of the page load may not make it in before this event fires – like JavaScript based image carousels – causing inconsistent page load times and inaccurate screenshots.
  • When should I use Onload Time? In general, there’s no real definitive case to prefer Onload Time (which is why we defaulted to Fully Loaded Time), though certain specialized cases might call for it.
     
• Fully Loaded Time is the period after all of the following have occurred :
  • First wait for these conditions to be met :
    • First Contentful Paint has fired
    • Onload has fired
    • Network is idle (5.25s of 2 or fewer in-flight requests after DOM Content Loaded has fired
       
  • then delay for :
    • CPU is idle (5.25s of no long tasks)
    • Hard time out of 30s after Onload has fired
       
  • ultimately, when the above conditions are met, we then take the maximal timing of :
    • First Paint
    • First Contentful Paint
    • Onload Time
    • Largest Contentful Paint
    • Time to Interactive
    • Last request captured
       
  • basically, Flickroom is now waiting until your page stops transferring data before completing a trial, resulting in more consistent Page Load Times.
  • Possible issues with using this event:
    • This event fires only when a page completely stops loading content, including ads and below-the-fold elements.
    • Fully Loaded Time waits for a page to finish executing JavaScript (measured from First Contentful Paint (FCP) to the last long task; also known as Time to Interactive).

    Your site might have loaded flying above-the-fold and be useable, however since the analysis is immediately waiting for the entire site to stop loading data, your reported Page Load Time might be longer .

28. How do I change the time to stop test?

You can change your time to stop test to Onload Time by enabling the “ Stop test onload ” option in the analysis Options ( logarithm in required ) or changing the setting on an existing report in the Page Settings. You can besides change your default in User Settings from the Account page .
however, we do recommend sticking with using Fully Loaded Time unless you have a particular consumption case for it .
“ Stop test onload ” option is only available for Firefox and Chrome ( Android ) tests, which generate Legacy Reports ( i.e., PageSpeed/YSlow ) .

29. When I compare my Simulate Device page performance to the actual device, why are they different?

Our Simulate Device feature works by telling our browser to identify itself as the selected device through the User Agent string. We then change the Screen Resolution and set the appropriate Device Pixel Ratio for the device to match a well. We have combinations of these options for many of the popular devices used today .
Hardware operation is not simulated however. The performance differences probably root from the fact that Flickroom uses server-grade hardware to launch a browser and lode pages, which differs significantly from the actual device ‘s hardware performance ( fluid CPUs, GPUs, memory, etc ) .

30. How accurate is the Simulate Device feature?

Simulate Device can give you a great theme of whether or not your site adheres to mobile recommendations and may help optimization with layout pendent on User Agent specific style. Combined with Screen Resolution changes, you can actually get a general feel of your page display and performance in terms of total page size .
however, actual burden time is less representative, due to the hardware caution mentioned above, which is why you should silent test your page on the actual device in order to get real global performance benchmarks. In addition, rendering engines on respective devices may differ ( e.g. if the user is using Firefox mobile as their chief browser ), resulting in different real world performance .
Our fake Device feature gives you a good start benchmark to gauge your performance with on these devices, but they should not be regarded as 1:1 comparisons .

31. What happens to my report data after I downgrade?

here ‘s what will happen to monitored pages and their comparable data :

• If you currently have more monitored pages than alloted for in your new plan, Flickroom will disable monitoring on a number of them to align with your new Monitored Slot limit.
• All report history and data will be retained for a stipulate number of months depending on the plan you downgraded to :
  • Basic: 3 months
  • Solo, Starter, Growth: 6 months*
  • Champion, Team: 12 months*

The retention time starts from the report genesis date. After the time has elapsed, reports will be purged from our database and are not recoverable .
As a courtesy, we delay the purge of your report data for 2 weeks after you ‘ve downgraded so you can get things sorted .
* If your plan includes more data memory time via an Add-on, it besides will be included .

GTmetrix Analysis Errors

1. Network connectivity errors

There may be a connectivity consequence between your server and the Flickroom quiz server if you get errors like “ Read timeout ”, “ Write failed ”, “ Broken pipe ” or “ Flickroomn reset by peer ” .
You can try again by and by, or try testing from another one of our trial locations ( requires log in ). If it fails from multiple locations, it normally means that it ‘s a trouble on your end and your users are experiencing alike issues. Contact your hosting supplier to get the offspring resolved .

2. Server status errors

Flickroom entirely analyzes pages that return a successful HTTP condition code. If you get this error, your foliate has returned an error HTTP status code .
The most common reasons for this include :

• Your web application generating the page is incorrectly returning an error HTTP status code, but is returning page content that does not indicate an error.
• Your web application is blocking Flickroom from accessing the page. With WordPress, it could be due to plugins like Bad Behaviour or Wordfence. With e-commerce software, it’s common that the access is blocked based on the IP.
• You are using a reverse proxy (eg. CloudFlare) and it’s blocking Flickroom from accessing the page.

In all these cases, you ‘ll need to fix or configure your world wide web application to return a successful HTTP condition code or allow Flickroom access to your page. Your web waiter ‘s error log may provide penetration into why it ‘s returning an error .

3. SSL certificate errors

Flickroom only analyzes HTTPS sites that have a valid, trusted SSL security ( internet explorer. not self-signed, non-expired, match coarse name ) .
A common problem with HTTPS sites is that the intermediate/chain certificates are n’t installed correctly. If you do n’t have the intermediate certificates installed by rights, some users ( including Flickroom ) will get an SSL security error while viewing your foliate. For instructions on how to properly install your SSL certificate and to test your SSL certificate visit SSLShopper .

4. DNS errors

If Flickroom has problems resolving your web site ‘s knowledge domain, then you may have DNS shape issues. You can get a report on your DNS configuration at intoDNS – be sure to look into the items that are marked as bolshevik .
however, if your web site has recently changed name servers or changed its DNS shape ( eg. moved servers ), then the issue might be that your DNS records have been cached. Depending on your configuration, this may take up to 24 hours ( at most 48 hours ) to propagate. Try re-testing your page at a later time .

5. Your page took too long to load

The utmost meter Flickroom will wait for a page to load ( clock time it takes for the window.onload event to arouse ) is 2 minutes .
The most common reasons for this error are :

• An extremely slow loading page or resource or lots of slow loading resources.
• JavaScript that’s preventing the window.onload event from firing.

For dense load pages or resources, testing from a closer trial placement ( requires logarithm in ) may help speed things up .

6. The URL did not appear to be an HTML page

Flickroom only analyzes HTML pages. To ensure that your foliate is an HTML page, Flickroom checks the Content-Type header for text/html .
You besides may get this mistake if the Content-Type header is missing or the value is evacuate. The problem is likely an issue with the web application and not the web server .

7. JavaScript redirect or meta refresh

unfortunately, Flickroom presently does not handle pages that perform meta refreshes or use JavaScript to redirect the page. however, you can work around this issue by visiting the page in your own browser to find the concluding redirected URL – this is the URL to use with Flickroom .
You besides may mistakenly get this message if your page opens a popup that evades the browser ‘s popup blocker. unfortunately, there is presently no situate for this early than to ensure that your page does not open the popup ( the Block URL choice may besides help work around this exit ) .

GTmetrix Payment & Billing

1. My credit card keeps getting declined, but it’s worked for other purchases – Why?

There are many reasons why a transaction can be declined ( even with a valid credit card ). Some common reasons include :

• Your credit card is declining online or international transactions (GTmetrix is located in Canada).
• Your credit card has reached its credit limit.
• The transaction triggered your credit card’s anti-fraud system.

We realize it ‘s a frustrating situation and apologize for any troublesomeness. Read on for more details on refuse transactions .

2. What can I do if my payment keeps getting declined?

here are a few things you can do :

• Re-enter your credit card number and security code.
• Contact your credit card company to add Flickroom as an approved and legitimate charge.
• Try a different credit card.

If your requital inactive keeps getting declined, contact us and we ‘ll work with you towards another solution .

3. I’ve been successfully subscribed with my card for a while, but now it’s getting declined suddenly. Why?

This is unmanageable to answer as the erroneousness code reaction we get is quite obscure. sometimes credit card companies have a change in security / imposter procedures or algorithms. early times it ‘s our payment gateway deciding to trigger an anti-fraud sag abruptly .
It ‘s unfortunate in any shell, but we ‘re fix and will to explore solutions with you to get things working again .

4. What payment options does Flickroom accept?

We accept Visa, Mastercard, American Express, Discover, Diners Club and JCB .
We can besides accept Purchase Orders ( PO ), PayPal, Cheques and Bank Transfers, but these methods need to be processed manually and require a Champion plan or higher on a annual terminus. Contact us to get this set up .

5. I require a PO / manual invoicing for my Flickroom PRO subscription

We can help you out ! Let our team know using our contact mannequin and we can set things up for you. Note that we only provide this military service to users on Champion or higher plans on a annual term .

6. I’m having trouble signing up for a PRO subscription!

We ‘ll help you resolve your topic. Reach out to our team using our contact kind and we ‘ll work towards a solution .

8. How do I view my past invoices?

You can find all of your Flickroom invoices by going to your Account page – then on the right menu parry, suction stop on “ Past Invoices “

A sidebar will slide out and reveal a dropdown choice of all available invoices :

precisely select your desire bill and click “ Download Invoice ” to get a PDF version.

9. How do I cancel my PRO subscription?

Sorry to hear you did n’t find Flickroom PRO a good fit = (
You can cancel your subscription from the Account page by clicking on “ Cancel Plan “

Follow the instructions and upon cancellation, you should receive an e-mail confirming your cancellation .

Source : https://flickroom.net
Category : Web Browsers