5 sec in total
221 ms
4.1 sec
676 ms
Visit phoenixprojesi.com now to see the best up-to-date Phoenix Projesi content and also check out these interesting facts you probably never knew about phoenixprojesi.com
The Phoenix Archaeological Project (PAP) is an interdisciplinary and multinational excavation and survey project in ancient Phoenix.
Visit phoenixprojesi.comWe analyzed Phoenixprojesi.com page load time and found that the first response time was 221 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
phoenixprojesi.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value11.1 s
0/100
25%
Value11.0 s
6/100
10%
Value290 ms
80/100
30%
Value0.012
100/100
15%
Value11.2 s
20/100
10%
221 ms
995 ms
167 ms
358 ms
350 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 77% of them (89 requests) were addressed to the original Phoenixprojesi.com, 21% (24 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Phoenixprojesi.com.
Page size can be reduced by 175.3 kB (9%)
1.8 MB
1.7 MB
In fact, the total size of Phoenixprojesi.com main page is 1.8 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.1 MB which makes up the majority of the site volume.
Potential reduce by 140.2 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 140.2 kB or 87% of the original size.
Potential reduce by 30.4 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. Phoenix Projesi images are well optimized though.
Potential reduce by 2.4 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.
Potential reduce by 2.3 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. Phoenixprojesi.com has all CSS files already compressed.
Number of requests can be reduced by 61 (73%)
83
22
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phoenix Projesi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
phoenixprojesi.com
221 ms
995 ms
wp-emoji-release.min.js
167 ms
www.phoenixprojesi.com
358 ms
style.min.css
350 ms
frontend.css
265 ms
classic-themes.min.css
273 ms
depicter-pre.css
274 ms
c5ad73d.css
377 ms
all.min.css
439 ms
v4-shims.min.css
365 ms
public.css
366 ms
jet-popup-frontend.css
437 ms
themify-icons.min.css
451 ms
dflip.min.css
457 ms
6329005.css
458 ms
jet-elements.css
568 ms
jet-elements-skin.css
524 ms
elementor-icons.min.css
527 ms
custom-frontend.min.css
640 ms
swiper.min.css
548 ms
font-awesome.min.css
557 ms
frontend.min.css
613 ms
post-6.css
618 ms
jet-blog.css
645 ms
flatpickr.min.css
649 ms
global.css
664 ms
post-1730.css
701 ms
wp-featherlight.min.css
702 ms
general.min.css
735 ms
post-1964.css
733 ms
post-1979.css
740 ms
css
27 ms
fontawesome.min.css
759 ms
solid.min.css
787 ms
brands.min.css
787 ms
jquery.min.js
919 ms
jquery-migrate.min.js
826 ms
animations.min.css
765 ms
utils.min.js
692 ms
depicter.js
855 ms
underscore.min.js
609 ms
frontend.min.js
757 ms
vue.min.js
771 ms
jet-menu-public-scripts.js
671 ms
dflip.min.js
825 ms
wpFeatherlight.pkgd.min.js
659 ms
general.min.js
739 ms
jquery.parallax-scroll.min.js
684 ms
jquery.smartmenus.min.js
709 ms
url-polyfill.min.js
752 ms
webpack.runtime.min.js
745 ms
frontend-modules.min.js
749 ms
waypoints.min.js
681 ms
core.min.js
696 ms
frontend.min.js
730 ms
jet-elements.min.js
723 ms
widgets-scripts.js
719 ms
anime.min.js
680 ms
jet-popup-frontend.js
684 ms
wp-util.min.js
667 ms
frontend.min.js
720 ms
jet-blog.min.js
721 ms
flatpickr.min.js
718 ms
94387a7bca5f87f4c35a18e95.js
131 ms
phoenix-logo-eng-color.svg
525 ms
yesilgelme.jpeg
1092 ms
topography-1.svg
504 ms
village-1.svg
504 ms
museum-1.svg
505 ms
network-1.svg
522 ms
flower-1.svg
543 ms
chat-1.svg
588 ms
seismograph-2-1.svg
590 ms
bay-1.svg
614 ms
seashore.png
615 ms
map-2-1.svg
637 ms
abstract-1.svg
613 ms
KFOmCnqEu92Fr1Mu4mxM.woff
27 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
27 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
43 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
43 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
43 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
43 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjg.woff
44 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjg.woff
44 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjg.woff
45 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjg.woff
45 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjg.woff
45 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjg.woff
46 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjg.woff
46 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjg.woff
47 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjg.woff
47 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbfOLjOWw.woff
48 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8cTfOLjOWw.woff
47 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8ajfOLjOWw.woff
48 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8XbfOLjOWw.woff
48 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8fbeOLjOWw.woff
95 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8SjYOLjOWw.woff
49 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8RHYOLjOWw.woff
48 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8XbYOLjOWw.woff
93 ms
raxhHiqOu8IVPmnRc6SY1KXhnF_Y8V_YOLjOWw.woff
186 ms
fa-solid-900.woff
781 ms
fa-solid-900.woff
910 ms
fa-regular-400.woff
625 ms
fa-brands-400.woff
756 ms
fa-brands-400.woff
779 ms
jupiterx.woff
626 ms
hieroglyph-1.svg
701 ms
ekoloji.png
744 ms
toplum.png
753 ms
image.png
767 ms
phoenix.jpg
866 ms
donate-image.png
1298 ms
proxy-removebg-preview-e1680761008413.png
910 ms
phoenixprojesi.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
phoenixprojesi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
phoenixprojesi.com SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoenixprojesi.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Phoenixprojesi.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.
phoenixprojesi.com
Open Graph data is detected on the main page of Phoenix Projesi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: