Tools & Wizards About Us
geodar.org screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

geodar.org

Начало :: Geodar

Page Load Speed

3.9 sec in total

First Response

563 ms

Resources Loaded

3.2 sec

Page Rendered

114 ms

geodar.org screenshot

About Website

Click here to check amazing Geodar content for Bulgaria. Otherwise, check out these important facts you probably never knew about geodar.org

Geodar Магазин - за оръжие и аксесоари. Стрелбище Диана - стрелкови комплекс

Visit geodar.org

Key Findings

We analyzed Geodar.org page load time and found that the first response time was 563 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

geodar.org performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.47

18/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

home.php

563 ms

PaginatorComponent.css

116 ms

ItemView.css

232 ms

ProductListItem.css

334 ms

MessageDialog.css

336 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 98% of them (79 requests) were addressed to the original Geodar.org, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (988 ms) belongs to the original domain Geodar.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.4 kB (36%)

Content Size

155.5 kB

After Optimization

100.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geodar.org main page is 155.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 58.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 50.7 kB

  • Original 58.7 kB
  • After minification 57.1 kB
  • After compression 7.9 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 50.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 34.1 kB

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.

JavaScript Optimization

-3%

Potential reduce by 1.5 kB

  • Original 47.5 kB
  • After minification 47.4 kB
  • After compression 45.9 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

-21%

Potential reduce by 3.2 kB

  • Original 15.4 kB
  • After minification 15.3 kB
  • After compression 12.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. Geodar.org needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (58%)

Requests Now

79

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

home.php

home.php

563 ms

PaginatorComponent.css

PaginatorComponent.css

116 ms

ItemView.css

ItemView.css

232 ms

ProductListItem.css

ProductListItem.css

334 ms

MessageDialog.css

MessageDialog.css

336 ms

FormRenderer.css

FormRenderer.css

334 ms

Container.css

Container.css

334 ms

InputField.css

InputField.css

335 ms

KeywordSearch.css

KeywordSearch.css

345 ms

MenuBarComponent.css

MenuBarComponent.css

445 ms

ColorButton.css

ColorButton.css

444 ms

ModalPane.css

ModalPane.css

445 ms

ImagePopup.css

ImagePopup.css

452 ms

SparkPage.css

SparkPage.css

447 ms

store.css

store.css

462 ms

store.css

store.css

554 ms

utils.js

utils.js

554 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

665 ms

js.cookie.min.js

js.cookie.min.js

558 ms

CallStack.js

CallStack.js

561 ms

SparkObject.js

SparkObject.js

574 ms

SparkEvent.js

SparkEvent.js

664 ms

Component.js

Component.js

665 ms

JSONRequest.js

JSONRequest.js

674 ms

ModalPopup.js

ModalPopup.js

671 ms

Tooltip.js

Tooltip.js

686 ms

ImagePopup.js

ImagePopup.js

774 ms

MessageDialog.js

MessageDialog.js

775 ms

SparkPage.js

SparkPage.js

775 ms

StoreCookies.js

StoreCookies.js

782 ms

JSONDialog.js

JSONDialog.js

785 ms

MenuBarComponent.js

MenuBarComponent.js

799 ms

ConfirmMessageDialog.js

ConfirmMessageDialog.js

884 ms

JSONFormDialog.js

JSONFormDialog.js

884 ms

ProductListItem_base.css

ProductListItem_base.css

557 ms

ProductListItem_mobile.css

ProductListItem_mobile.css

563 ms

FormRendererHBox.css

FormRendererHBox.css

568 ms

FormRendererVBox.css

FormRendererVBox.css

581 ms

css2

css2

30 ms

store_base.css

store_base.css

538 ms

store_menu.css

store_menu.css

540 ms

store_mobile.css

store_mobile.css

539 ms

MenuBarComponent.css

MenuBarComponent.css

114 ms

logo_header.svg

logo_header.svg

116 ms

storage.php

storage.php

233 ms

storage.php

storage.php

319 ms

storage.php

storage.php

176 ms

storage.php

storage.php

150 ms

storage.php

storage.php

373 ms

storage.php

storage.php

294 ms

storage.php

storage.php

313 ms

storage.php

storage.php

343 ms

storage.php

storage.php

376 ms

storage.php

storage.php

441 ms

storage.php

storage.php

471 ms

storage.php

storage.php

491 ms

storage.php

storage.php

518 ms

storage.php

storage.php

571 ms

storage.php

storage.php

542 ms

storage.php

storage.php

595 ms

storage.php

storage.php

625 ms

storage.php

storage.php

645 ms

storage.php

storage.php

667 ms

storage.php

storage.php

689 ms

storage.php

storage.php

718 ms

storage.php

storage.php

759 ms

storage.php

storage.php

781 ms

storage.php

storage.php

811 ms

storage.php

storage.php

840 ms

storage.php

storage.php

858 ms

search_icon.svg

search_icon.svg

811 ms

Phone_Icon.png

Phone_Icon.png

855 ms

Letter_Icon.png

Letter_Icon.png

876 ms

Location_Icon.png

Location_Icon.png

905 ms

Clock_Icon.png

Clock_Icon.png

921 ms

facebook_icon.svg

facebook_icon.svg

934 ms

instagram_icon.svg

instagram_icon.svg

951 ms

youtube_icon.svg

youtube_icon.svg

970 ms

mail_icon.svg

mail_icon.svg

988 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

32 ms

phone_icon.svg

phone_icon.svg

919 ms

Accessibility Review

geodar.org accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

geodar.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

geodar.org SEO score

92

Search Engine Optimization Advices

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

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 Geodar.org 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 Geodar.org 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

geodar.org

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