Tools & Wizards About Us
phpmag.de screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

phpmag.de

PHP Magazin - PHP, Datenbanken, Open Web Technologies

Page Load Speed

10.1 sec in total

First Response

384 ms

Resources Loaded

9.2 sec

Page Rendered

555 ms

phpmag.de screenshot

About Website

Visit phpmag.de now to see the best up-to-date PHP Mag content and also check out these interesting facts you probably never knew about phpmag.de

Das PHP Magazin ist die zentrale Informationsplattform rund um PHP-Technologien im deutschsprachigen Raum. Mit seinem bekannten Autorenteam gehört das PHP Magazin zur Pflichtlektüre aller PHP Professi...

Visit phpmag.de

Key Findings

We analyzed Phpmag.de page load time and found that the first response time was 384 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

phpmag.de performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value2,130 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

phpmag.de

384 ms

php

765 ms

gpt.js

40 ms

wp-emoji-release.min.js

104 ms

bwp-recent-comments.css

206 ms

Our browser made a total of 173 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Phpmag.de, 82% (142 requests) were made to Entwickler.de and 3% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Entwickler.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.7 MB (73%)

Content Size

3.7 MB

After Optimization

998.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phpmag.de main page is 3.7 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. CSS take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 119.5 kB

  • Original 144.7 kB
  • After minification 129.0 kB
  • After compression 25.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. This page needs HTML code to be minified as it can gain 15.7 kB, which is 11% 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 119.5 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 7.9 kB

  • Original 275.5 kB
  • After minification 267.6 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. PHP Mag images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 1.0 MB

  • Original 1.5 MB
  • After minification 1.4 MB
  • After compression 473.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.0 MB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 1.5 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 232.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. Phpmag.de needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 131 (83%)

Requests Now

157

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phpmag.de

phpmag.de

384 ms

php

php

765 ms

gpt.js

gpt.js

40 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

104 ms

bwp-recent-comments.css

bwp-recent-comments.css

206 ms

style.css

style.css

309 ms

font-awesome.min.css

font-awesome.min.css

310 ms

dashicons.min.css

dashicons.min.css

416 ms

style.css

style.css

312 ms

gmw-cl-style-dep.css

gmw-cl-style-dep.css

318 ms

jobspot.css

jobspot.css

314 ms

pac.css

pac.css

410 ms

layout.css

layout.css

411 ms

woocommerce-layout.css

woocommerce-layout.css

412 ms

woocommerce.css

woocommerce.css

417 ms

polls-css.css

polls-css.css

423 ms

wpfront-scroll-top.css

wpfront-scroll-top.css

511 ms

wbounce.min.css

wbounce.min.css

512 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

514 ms

wp-mediaelement.css

wp-mediaelement.css

517 ms

style.css

style.css

623 ms

font-awesome.min.css

font-awesome.min.css

523 ms

chosen.css

chosen.css

613 ms

responsive.css

responsive.css

615 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

617 ms

magnific-popup.css

magnific-popup.css

619 ms

owl.carousel.css

owl.carousel.css

630 ms

woocommerce.css

woocommerce.css

715 ms

style-midnightblue.css

style-midnightblue.css

717 ms

jkreativ-icon.min.css

jkreativ-icon.min.css

718 ms

css

css

78 ms

font-awesome.css

font-awesome.css

718 ms

bootstrap.css

bootstrap.css

722 ms

layouts.css

layouts.css

725 ms

responsive.css

responsive.css

815 ms

lightbox.css

lightbox.css

817 ms

mixed.css

mixed.css

816 ms

wpp.css

wpp.css

818 ms

ultimate.min.css

ultimate.min.css

1031 ms

js

js

65 ms

cookieconsent.min.js

cookieconsent.min.js

39 ms

Defaults.css

Defaults.css

827 ms

pubads_impl_82.js

pubads_impl_82.js

26 ms

container.html

container.html

22 ms

woocommerce-twitterboostrap.css

woocommerce-twitterboostrap.css

822 ms

main.min.css

main.min.css

722 ms

font-awesome.min.css

font-awesome.min.css

626 ms

main.min.css

main.min.css

622 ms

sands-style.css

sands-style.css

632 ms

kiosk-style.css

kiosk-style.css

713 ms

js_composer.css

js_composer.css

921 ms

jquery.js

jquery.js

729 ms

jquery-migrate.min.js

jquery-migrate.min.js

627 ms

hrf-script.js

hrf-script.js

667 ms

sandsjobprocessing.js

sandsjobprocessing.js

720 ms

wpfront-scroll-top.js

wpfront-scroll-top.js

739 ms

wbounce.min.js

wbounce.min.js

740 ms

masonry.js

masonry.js

652 ms

lightbox-2.6.min.js

lightbox-2.6.min.js

725 ms

jquery.mixitup.js

jquery.mixitup.js

725 ms

custom.js

custom.js

725 ms

ultimate.min.js

ultimate.min.js

823 ms

ajax-filter-posts.js

ajax-filter-posts.js

634 ms

functions.js

functions.js

720 ms

jquery-validate.bootstrap-tooltip.min.js

jquery-validate.bootstrap-tooltip.min.js

721 ms

jquery.validate.min.js

jquery.validate.min.js

722 ms

shCore.js

shCore.js

714 ms

shBrushAS3.js

shBrushAS3.js

807 ms

shBrushBash.js

shBrushBash.js

755 ms

shBrushColdFusion.js

shBrushColdFusion.js

754 ms

shBrushClojure.js

shBrushClojure.js

752 ms

shBrushCpp.js

shBrushCpp.js

753 ms

shBrushCSharp.js

shBrushCSharp.js

750 ms

shBrushCss.js

shBrushCss.js

745 ms

shBrushDelphi.js

shBrushDelphi.js

774 ms

shBrushDiff.js

shBrushDiff.js

772 ms

shBrushErlang.js

shBrushErlang.js

771 ms

shBrushFSharp.js

shBrushFSharp.js

775 ms

shBrushGroovy.js

shBrushGroovy.js

759 ms

shBrushJava.js

shBrushJava.js

674 ms

shBrushJavaFX.js

shBrushJavaFX.js

747 ms

shBrushJScript.js

shBrushJScript.js

745 ms

shBrushLatex.js

shBrushLatex.js

746 ms

shBrushMatlabKey.js

shBrushMatlabKey.js

739 ms

shBrushObjC.js

shBrushObjC.js

654 ms

shBrushPerl.js

shBrushPerl.js

647 ms

analytics.js

analytics.js

17 ms

shBrushPhp.js

shBrushPhp.js

689 ms

shBrushPlain.js

shBrushPlain.js

689 ms

collect

collect

12 ms

collect

collect

60 ms

shBrushPowerShell.js

shBrushPowerShell.js

634 ms

shBrushPython.js

shBrushPython.js

610 ms

shBrushR.js

shBrushR.js

609 ms

shBrushRuby.js

shBrushRuby.js

606 ms

shBrushScala.js

shBrushScala.js

704 ms

shBrushSql.js

shBrushSql.js

634 ms

shBrushVb.js

shBrushVb.js

633 ms

shBrushXml.js

shBrushXml.js

630 ms

jquery.form.min.js

jquery.form.min.js

653 ms

scripts.js

scripts.js

648 ms

scripts.min.js

scripts.min.js

641 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

639 ms

woocommerce.min.js

woocommerce.min.js

637 ms

jquery.cookie.min.js

jquery.cookie.min.js

636 ms

ads

ads

219 ms

cart-fragments.min.js

cart-fragments.min.js

544 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

99 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

153 ms

polls-js.js

polls-js.js

542 ms

retina.min.js

retina.min.js

600 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

703 ms

wp-mediaelement.js

wp-mediaelement.js

606 ms

plugins.js

plugins.js

706 ms

html5shiv.min.js

html5shiv.min.js

601 ms

main.js

main.js

606 ms

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

68 ms

PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf

PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf

70 ms

ZeroClipboard.min.js

ZeroClipboard.min.js

583 ms

ajax-post.js

ajax-post.js

585 ms

js_composer_front.js

js_composer_front.js

590 ms

gmw.js

gmw.js

589 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

783 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

986 ms

10298220688434874725

10298220688434874725

16 ms

osd.js

osd.js

24 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

852 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

722 ms

logo-mobile-ent.png

logo-mobile-ent.png

608 ms

75x75.png

75x75.png

607 ms

PHP900x133.jpg

PHP900x133.jpg

847 ms

entwickler-de-kiosk_v1.png

entwickler-de-kiosk_v1.png

717 ms

450x225.png

450x225.png

763 ms

300x150.png

300x150.png

764 ms

600x300.png

600x300.png

763 ms

PHP-Magazin-3-16_Cover_595x842-220x311.jpg

PHP-Magazin-3-16_Cover_595x842-220x311.jpg

920 ms

Abocover_Magazine_PM_29882-220x311.jpg

Abocover_Magazine_PM_29882-220x311.jpg

919 ms

Abocover_EK_29882-220x311.jpg

Abocover_EK_29882-220x311.jpg

835 ms

entwickler.jobs_Popup_Desktop_34633_v2_frei.jpg

entwickler.jobs_Popup_Desktop_34633_v2_frei.jpg

835 ms

entwickler.jobs_Popup_Mobile_34633_v2_frei.jpg

entwickler.jobs_Popup_Mobile_34633_v2_frei.jpg

995 ms

gmw-loader.gif

gmw-loader.gif

819 ms

shCore.css

shCore.css

801 ms

shThemeDefault.css

shThemeDefault.css

931 ms

1.png

1.png

967 ms

gtm.js

gtm.js

288 ms

admin-ajax.php

admin-ajax.php

3988 ms

embed.js

embed.js

217 ms

admin-ajax.php

admin-ajax.php

4172 ms

loading.gif

loading.gif

103 ms

close.png

close.png

111 ms

IPC-webinale-2016-90x45.jpg

IPC-webinale-2016-90x45.jpg

113 ms

puzzle-90x45.jpg

puzzle-90x45.jpg

103 ms

ff-windows-10-mobile-joomla-keep-alive-phpstorm-90x45.jpg

ff-windows-10-mobile-joomla-keep-alive-phpstorm-90x45.jpg

205 ms

h%C3%BCrden_business-90x45.jpg

h%C3%BCrden_business-90x45.jpg

4589 ms

iphone_enk-90x45.jpg

iphone_enk-90x45.jpg

213 ms

IPC-webinale-2016-300x150.jpg

IPC-webinale-2016-300x150.jpg

215 ms

webassembly-meilenstein-300x150.jpg

webassembly-meilenstein-300x150.jpg

410 ms

k%C3%BCnstliche-intelligenz_welt-300x150.jpg

k%C3%BCnstliche-intelligenz_welt-300x150.jpg

4593 ms

Container-300x150.jpg

Container-300x150.jpg

320 ms

flash-sicherheitsluecken-300x150.jpg

flash-sicherheitsluecken-300x150.jpg

559 ms

conversion_async.js

conversion_async.js

32 ms

33 ms

46 ms

65 ms

35 ms

20 ms

16 ms

common.js

common.js

4 ms

util.js

util.js

19 ms

stats.js

stats.js

29 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

114 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

103 ms

dark-bottom.css

dark-bottom.css

37 ms

Accessibility Review

phpmag.de accessibility score

54

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

phpmag.de 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

phpmag.de SEO score

79

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

phpmag.de

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