Tools & Wizards About Us
epezeshk.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

epezeshk.com

بانک اطلاعات پزشکی

Page Load Speed

5.1 sec in total

First Response

559 ms

Resources Loaded

4.1 sec

Page Rendered

407 ms

epezeshk.com screenshot

About Website

Welcome to epezeshk.com homepage info - get ready to check Epezeshk best content for Iran right away, or after learning these important things about epezeshk.com

بانک اطلاعات پزشکی مرجع پزشکان داروخانه ها بیمارستان ها آزمایشگاه ها و دانشنامه سلامت

Visit epezeshk.com

Key Findings

We analyzed Epezeshk.com page load time and found that the first response time was 559 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

epezeshk.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

epezeshk.com

559 ms

epezeshk.com

1251 ms

atrk.js

3 ms

theme-red2

859 ms

modernizr

671 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 97% of them (58 requests) were addressed to the original Epezeshk.com, 2% (1 request) were made to Certify-js.alexametrics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Epezeshk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.6 kB (8%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Epezeshk.com main page is 2.0 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 135.8 kB

  • Original 210.8 kB
  • After minification 174.4 kB
  • After compression 75.0 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. This page needs HTML code to be minified as it can gain 36.4 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 135.8 kB or 64% of the original size.

Image Optimization

-2%

Potential reduce by 30.8 kB

  • Original 1.7 MB
  • After minification 1.7 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. Epezeshk images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 2.1 kB

  • Original 41.6 kB
  • After minification 41.6 kB
  • After compression 39.5 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.

Requests Breakdown

Number of requests can be reduced by 6 (12%)

Requests Now

52

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epezeshk.com

epezeshk.com

559 ms

epezeshk.com

epezeshk.com

1251 ms

atrk.js

atrk.js

3 ms

theme-red2

theme-red2

859 ms

modernizr

modernizr

671 ms

jquery

jquery

841 ms

js

js

61 ms

WebResource.axd

WebResource.axd

340 ms

ScriptResource.axd

ScriptResource.axd

665 ms

ScriptResource.axd

ScriptResource.axd

504 ms

Site

Site

1153 ms

logo.jpg

logo.jpg

197 ms

search_90.png

search_90.png

196 ms

doctor_90.png

doctor_90.png

197 ms

answer_90.png

answer_90.png

197 ms

info_90.png

info_90.png

303 ms

233.jpg

233.jpg

499 ms

686.jpg

686.jpg

503 ms

2082.jpg

2082.jpg

513 ms

2213.jpg

2213.jpg

512 ms

137.jpg

137.jpg

605 ms

1431.jpg

1431.jpg

848 ms

1006.jpg

1006.jpg

848 ms

967.jpg

967.jpg

850 ms

1274.jpg

1274.jpg

685 ms

1178.jpg

1178.jpg

936 ms

208.jpg

208.jpg

858 ms

1892.jpg

1892.jpg

927 ms

4173.jpg

4173.jpg

997 ms

914.jpg

914.jpg

1165 ms

191.jpg

191.jpg

1021 ms

1135.jpg

1135.jpg

1031 ms

187.jpg

187.jpg

1093 ms

519.jpg

519.jpg

1103 ms

full.png

full.png

1164 ms

art_list_706.jpg

art_list_706.jpg

1193 ms

art_list_690.jpg

art_list_690.jpg

1203 ms

art_list_693.jpg

art_list_693.jpg

1258 ms

art_list_695.jpg

art_list_695.jpg

1268 ms

art_list_696.jpg

art_list_696.jpg

1331 ms

art_list_671.jpg

art_list_671.jpg

1331 ms

art_list_672.jpg

art_list_672.jpg

1367 ms

art_list_675.jpg

art_list_675.jpg

1375 ms

art_list_678.jpg

art_list_678.jpg

1423 ms

art_list_680.jpg

art_list_680.jpg

1422 ms

art_list_684.jpg

art_list_684.jpg

1347 ms

IRANSansWeb.woff

IRANSansWeb.woff

1306 ms

fa-solid-900.woff

fa-solid-900.woff

1384 ms

fa-regular-400.woff

fa-regular-400.woff

1383 ms

art_list_667.jpg

art_list_667.jpg

1436 ms

yd.ttf

yd.ttf

1333 ms

fa-brands-400.woff

fa-brands-400.woff

1176 ms

art_list_668.jpg

art_list_668.jpg

1174 ms

art_list_650.jpg

art_list_650.jpg

1204 ms

art_list_651.jpg

art_list_651.jpg

1214 ms

art_list_656.jpg

art_list_656.jpg

1154 ms

art_list_659.jpg

art_list_659.jpg

1089 ms

art_list_662.jpg

art_list_662.jpg

990 ms

search-cover-2.jpg

search-cover-2.jpg

992 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

1036 ms

Accessibility Review

epezeshk.com accessibility score

94

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

epezeshk.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

epezeshk.com SEO score

97

Search Engine Optimization Advices

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

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epezeshk.com can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Epezeshk.com 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

epezeshk.com

Open Graph description is not detected on the main page of Epezeshk. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: