Your Website Score is
SEO Rank : 19 Website URL: afera.bg Last Updated: 8 months
Success
55% of passed verification steps
Warning
15% of total warning
Errors
30% of total errors, require fast action
Share
Estimation Traffic and Earnings
3,015
Unique Visits
Daily
5,577
Pages Views
Daily
$12
Income
Daily
84,420
Unique Visits
Monthly
158,945
Pages Views
Monthly
$300
Income
Monthly
976,860
Unique Visits
Yearly
1,873,872
Pages Views
Yearly
$3,168
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
39 Characters
АФЕРА.БГ | ЖУРНАЛИСТИЧЕСКИ РАЗСЛЕДВАНИЯ
Meta Description
39 Characters
АФЕРА.БГ | Журналистически разследвания
Effective URL
15 Characters
http://afera.bg
Excerpt
Page content
АФЕРА.БГ | Журналистически разследвания
този живот е за смелите
Начало
Скандално
Разследвания
Мишена
Интервю
Репортер
Позиция
Топ в afera.bgПЪРВИТЕ ХИЛЯДА БРОЯ ОТ НОВАТА КОНСТИТУЦИЯ ЩЕ...
Google Preview
Your look like this in google search result
АФЕРА.БГ | ЖУРНАЛИСТИЧЕСКИ РАЗСЛЕДВАНИЯ
http://afera.bg
АФЕРА.БГ | Журналистически разследвания
Robots.txt
File Detected
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~78.46 KB
Code Size: ~63.17 KB
Text Size: ~15.3 KB Ratio: 19.50%
Social Data
Desktop
Efficiently encode images
Potential savings of 54 KiB
Optimized images load faster and consume less cellular data
Initial server response time was short
Root document took 540 ms
Keep the server response time for the main document short because all other requests depend on it
Remove unused CSS
Potential savings of 76 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Cumulative Layout Shift
0.029
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid long main-thread tasks
4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Properly size images
Potential savings of 123 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Time to Interactive
4.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Remove unused JavaScript
Potential savings of 373 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Contentful Paint
0.6 s
First Contentful Paint marks the time at which the first text or image is painted
User Timing marks and measures
4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Does not use HTTPS
96 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Defer offscreen images
Potential savings of 117 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index
1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimizes main-thread work
1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small
121 requests • 1,837 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve images in next-gen formats
Potential savings of 240 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoids an excessive DOM size
734 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Uses efficient cache policy on static assets
3 resources found
A long cache lifetime can speed up repeat visits to your page
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Avoid chaining critical requests
21 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Total Blocking Time
80 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 15.1 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
First Meaningful Paint
0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint
3.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources
Potential savings of 230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids enormous network payloads
Total size was 1,837 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay
130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
JavaScript execution time
0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimize third-party usage
Third-party code blocked the main thread for 120 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
First CPU Idle
2.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Estimated Input Latency
10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Mobile
Properly size images
Potential savings of 4 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Document uses legible font sizes
99.54% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Serve images in next-gen formats
Potential savings of 266 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Largest Contentful Paint
11.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Uses efficient cache policy on static assets
3 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index
5.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time
2.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short
Root document took 540 ms
Keep the server response time for the main document short because all other requests depend on it
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Time to Interactive
15.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small
116 requests • 1,852 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
User Timing marks and measures
4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Max Potential First Input Delay
770 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint (3G)
4174 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Meaningful Paint
2.1 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint
2.1 s
First Contentful Paint marks the time at which the first text or image is painted
Defer offscreen images
Potential savings of 321 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid chaining critical requests
18 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Minimize main-thread work
4.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids an excessive DOM size
698 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks
Interactive at 15.0 s
A fast page load over a cellular network ensures a good mobile user experience
Reduce the impact of third-party code
Third-party code blocked the main thread for 920 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoid long main-thread tasks
13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Total Blocking Time
980 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused CSS
Potential savings of 76 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
First CPU Idle
9.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Estimated Input Latency
310 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Tap targets are not sized appropriately
90% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Eliminate render-blocking resources
Potential savings of 710 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Does not use HTTPS
93 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Efficiently encode images
Potential savings of 54 KiB
Optimized images load faster and consume less cellular data
Avoids enormous network payloads
Total size was 1,852 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused JavaScript
Potential savings of 392 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
Alexa Rank
30
Local Rank: BG / Users: 91.1% / PageViews: 92.4%32,102
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| afera.co | Already Registered |
| afera.us | Available Buy Now! |
| afera.com | Already Registered |
| afera.org | Already Registered |
| afera.net | Already Registered |
| aera.bg | Available Buy Now! |
| qfera.bg | Available Buy Now! |
| zfera.bg | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Fri, 14 Aug 2020 11:07:28 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=dfebb355dcedb0fb97180f9b8613295cf1597403248; expires=Sun, 13-Sep-20 11:07:28 GMT; path=/; domain=.afera.bg; HttpOnly; SameSite=Lax
Vary: User-Agent,Accept-Encoding
Last-Modified: Fri, 14 Aug 2020 11:05:19 GMT
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Mon, 29 Oct 1923 20:30:00 GMT
CF-Cache-Status: DYNAMIC
cf-request-id: 048e404ed100000585e22b5200000001
Server: cloudflare
CF-RAY: 5c2a365e1cd80585-LAX
Content-Encoding: gzip
Click to Add/Show Comments