Tools & Wizards About Us
pharos.bg screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

pharos.bg

Училища Фарос - Езикови курсове за деца и възрастни

Page Load Speed

3.8 sec in total

First Response

471 ms

Resources Loaded

2.9 sec

Page Rendered

432 ms

pharos.bg screenshot

About Website

Click here to check amazing Pharos content for Bulgaria. Otherwise, check out these important facts you probably never knew about pharos.bg

Чуждоезиково училище Фарос - Предлагаме присъствени и онлайн курсове по английски език за деца и възрастни. Подготовка за изпити на Cambridge

Visit pharos.bg

Key Findings

We analyzed Pharos.bg page load time and found that the first response time was 471 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

pharos.bg performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.24

52/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

pharos.bg

471 ms

pharos.bg

586 ms

8ajj5.css

231 ms

84lez.css

450 ms

hu6n7.css

565 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 69% of them (45 requests) were addressed to the original Pharos.bg, 14% (9 requests) were made to Fonts.gstatic.com and 9% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (861 ms) belongs to the original domain Pharos.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.9 kB (6%)

Content Size

2.6 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pharos.bg main page is 2.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 128.8 kB

  • Original 155.4 kB
  • After minification 147.0 kB
  • After compression 26.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 128.8 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 22.7 kB

  • Original 1.9 MB
  • After minification 1.9 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Pharos images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.4 kB

  • Original 287.7 kB
  • After minification 287.7 kB
  • After compression 283.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 5.0 kB

  • Original 202.2 kB
  • After minification 202.2 kB
  • After compression 197.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Pharos.bg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (63%)

Requests Now

52

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pharos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pharos.bg

pharos.bg

471 ms

pharos.bg

pharos.bg

586 ms

8ajj5.css

8ajj5.css

231 ms

84lez.css

84lez.css

450 ms

hu6n7.css

hu6n7.css

565 ms

css

css

40 ms

css

css

56 ms

hmh5t.css

hmh5t.css

341 ms

8hs35.css

8hs35.css

346 ms

css

css

63 ms

hmh5v.css

hmh5v.css

607 ms

css

css

63 ms

84lez.js

84lez.js

840 ms

js

js

69 ms

hmh5v.css

hmh5v.css

349 ms

css

css

18 ms

hmh5v.css

hmh5v.css

351 ms

css

css

18 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

475 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

475 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

474 ms

wp-polyfill.min.js

wp-polyfill.min.js

569 ms

index.js

index.js

567 ms

slick.js

slick.js

582 ms

wbg-front.js

wbg-front.js

580 ms

comment-reply.min.js

comment-reply.min.js

616 ms

api.js

api.js

94 ms

index.js

index.js

678 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

680 ms

js_composer_front.min.js

js_composer_front.min.js

693 ms

skrollr.min.js

skrollr.min.js

693 ms

vc-waypoints.min.js

vc-waypoints.min.js

796 ms

counter.js

counter.js

860 ms

imagesloaded.min.js

imagesloaded.min.js

860 ms

masonry.min.js

masonry.min.js

861 ms

fbevents.js

fbevents.js

116 ms

top-view-disorganized-letters-scaled.jpg

top-view-disorganized-letters-scaled.jpg

560 ms

youthful-student-kid-schoolboy-raising-scaled.jpg

youthful-student-kid-schoolboy-raising-scaled.jpg

706 ms

analytics.js

analytics.js

106 ms

collect

collect

15 ms

two-students-class-1024x683.jpg

two-students-class-1024x683.jpg

258 ms

content-teenagers-posing-together-1024x683.jpg

content-teenagers-posing-together-1024x683.jpg

373 ms

handsome-young-businessman-is-using-tablet-1024x683.jpg

handsome-young-businessman-is-using-tablet-1024x683.jpg

258 ms

student-taking-written-test-1024x683.jpg

student-taking-written-test-1024x683.jpg

238 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

54 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

54 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

143 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

154 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

154 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

356 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

479 ms

jizaRExUiTo99u79P0Y.woff

jizaRExUiTo99u79P0Y.woff

179 ms

jizfRExUiTo99u79B_mh4Oo.woff

jizfRExUiTo99u79B_mh4Oo.woff

177 ms

top-view-disorganized-letters-scaled.jpg

top-view-disorganized-letters-scaled.jpg

797 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLDrMfJg.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4bbLDrMfJg.woff

51 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDrMfJg.woff

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4Y_LDrMfJg.woff

74 ms

world-white.svg

world-white.svg

311 ms

share-white.svg

share-white.svg

342 ms

facebook-white.svg

facebook-white.svg

371 ms

Faros_logo_side2.png

Faros_logo_side2.png

425 ms

icon-search-grey.png

icon-search-grey.png

461 ms

champion.gif

champion.gif

464 ms

books.gif

books.gif

679 ms

computer.gif

computer.gif

463 ms

icon-close-white.svg

icon-close-white.svg

114 ms

Accessibility Review

pharos.bg accessibility score

88

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pharos.bg best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pharos.bg SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pharos.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Pharos.bg main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

pharos.bg

Open Graph data is detected on the main page of Pharos. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: